Sdet-3

Role Overview

As an Embedded SDET at Exotel you will be the Quality Lead within a high-impact product pod (e.g. Voicebot Billing or Voice Infra). You will partner directly with developers to eliminate silos between coding and oftestingthe code for them you will build the automation frameworks and CI/CD gates that empower developers to own their quality with confidence.

Key Responsibilities

• Engineering Quality Tooling:Design and develop automatedtestingframeworks (API UI and Contract) specifically tailored to your pods domain.

• The Shift-Left Advocate:Work with developers to improve unit and in design reviews to ensure new features are architected for testability.

• ContractTesting:Implement and maintain contracttests(e.g. Pact) to ensure your pods services interact flawlessly with shared services like IAM or Telemetry.

• CI/CD Pipeline Integration:Own the Quality Gate in the deployment that automated suites are fast reliable and provide immediate feedback to developers.

• Chaos & Resilience:Partner with the Reliability Architect to design and run Game Days and chaos engineering experiments totestservice failure modes.

• Observability for Quality:Build dashboards to track quality metrics likeChange Failure RateandEscaped Defectsfor your specific product area.

Required Skills & Experience

• Coding Proficiency:Strong experience in at least one of Exotels core languages (e.g. Java Python Go or ).

• TestArchitecture:Proven track record of building scalable automation frameworks from scratch (not just writing scripts).

• Infrastructure Mindset:Familiarity with Docker Kubernetes and CI/CD tools (e.g. Jenkins GitLab CI or GitHub Actions).

• API Mastery:Deep understanding of RESTful services gRPC and tools like Postman or RestAssured.

• Problem Solving:The ability to debug complex distributed systems and identify root causes in a microservices environment.

Key Performance Indicators (Success Metrics)

1. Production Defect Rate:Reduction in bugs found by customers after release.

2. TestExecution Speed:Maintaining a high-speed CI pipeline where time-to-feedback is minimized.

3. Developer Self-Sufficiency:% of automatedtestssuccessfully written and maintained by the developers using your frameworks.

4. MTTR (Mean Time to Recovery):Improving the speed at which a pod can identify and roll back a faulty release using your automated gates.