What does a SDET (Software Development Engineer in Test) do?
An SDET writes production-grade code whose product is confidence: automation frameworks, API and contract suites, and the CI pipelines that run them on every commit. Indian teams hire for this when manual regression stops scaling, and the job blends developer-level coding with test design, flaky-test forensics, and ownership of test data and environments.
A sdet (software development engineer in test) usually has around 2–9 yrs of experience and earns typically ₹6L–₹28L/yr in India. The day-to-day blends Selenium, Playwright, Appium and more — this page gives you a ready-to-use sdet (software development engineer in test) job description template you can copy, plus the exact skills and salary employers expect.
SDET (Software Development Engineer in Test) job description template
Copy the 9 responsibilities, 6 requirements and 10 skills below into your job post, then edit the parts that are specific to your company — pay band, location and reporting line.
Select the text above to copy it manually if the button is unavailable.
What are a SDET (Software Development Engineer in Test)'s key responsibilities?
A sdet (software development engineer in test) is typically responsible for the 9 duties below, which cover the day-to-day work most employers expect the role to own outright. Paste them into your job post as they are, or cut the ones another team already handles — a responsibility list that claims work the hire will not actually do is the fastest way to lose a candidate at offer stage:
- Build and maintain automation frameworks in Selenium, Playwright or Cypress for web flows
- Automate mobile regression with Appium across a device farm or emulator matrix
- Write API, contract and integration tests that run faster and more reliably than UI tests
- Wire suites into CI so every pull request gets a verdict within an agreed time budget
- Triage flaky tests to a root cause — timing, test data, or a genuine product race
- Design and refresh fixtures and seeded environments so runs stay repeatable
- Review feature code for testability and add missing hooks, element ids and instrumentation
- Report coverage, failure trends and escaped defects back to the engineering team
- Build performance and load checks for critical endpoints alongside functional suites
What qualifications does a SDET (Software Development Engineer in Test) need?
Employers hiring a sdet (software development engineer in test) in India usually ask for the 6 qualifications below, typically alongside 2–9 yrs of experience. Keep only the ones you will genuinely screen on: every extra must-have narrows the pool, and in the Indian market a long mandatory list filters out strong candidates whose background simply reads differently on paper:
- Coding ability comparable to a developer in Java, Python, TypeScript or C#
- Framework design experience rather than only recording or scripting inside a vendor tool
- Strong grasp of HTTP, REST payloads, authentication flows and API testing tools
- Experience with Git-based CI systems such as Jenkins, GitHub Actions or GitLab CI
- Understanding of the test pyramid, mocking, stubbing and deterministic test design
- Debugging skill to prove whether a red build is a product bug or a test defect
What skills should a SDET (Software Development Engineer in Test) have?
These are the 10 skills employers name most often on live sdet (software development engineer in test) listings in India. Treat the first few as the ones worth screening for directly and the rest as signals a candidate can pick up on the job — asking for all of them at once is what turns a reasonable role into an unfillable one:
Listing the three or four skills you genuinely screen on — rather than all 10 — is what keeps a sdet (software development engineer in test) posting from filtering out candidates who could do the job.
What does a SDET (Software Development Engineer in Test) earn in India?
Typical salary (India)
typically ₹6L–₹28L/yr
Experience range
2–9 yrs
These are typical ranges and vary by city, company and skills. For live, role-specific pay data, see the OnJob salary guide.
SDET (Software Development Engineer in Test) job description — FAQs
How does an SDET differ from a manual QA engineer?
Manual QA engineers explore the product, design test cases and judge quality by using the application. The engineer-in-test role instead writes software — frameworks, harnesses, fixtures and pipelines — that executes those checks automatically at scale. Both need product understanding, but only one is interviewed on data structures, code design and debugging depth.
What does the hiring loop look like in India?
Hiring loops open with a coding round on par with a developer interview — arrays, strings, complexity — followed by a framework-design discussion covering page objects, wait strategy, test-data isolation and how you would keep a suite under ten minutes. Many companies add a debugging exercise on a deliberately flaky suite plus a CI configuration question.
How should flaky tests be handled?
Flaky tests get quarantined, not retried into silence. The discipline is to reproduce the failure with fixed seeds and full logs, classify it as timing, shared state, test data or a real product race, then fix the underlying cause. Blanket retries hide genuine concurrency bugs and slowly train the team to ignore red builds.
Is automation testing a good long-term career in India?
Automation testing holds up well provided the skill set stays engineering-heavy. Roles that only record and replay scripts are being squeezed by low-code tools and AI-assisted generation, while people who design frameworks, own CI reliability and understand distributed systems keep moving into test architecture, platform or developer positions with matching pay.