SDET vs QA engineer
Updated 2026-11-13 · 2 min read
Compare role expectations without salary claims or rigid title rules; use responsibilities to assess a testing job. Includes a comparison table, concrete examples and an interview answer.
The difference in one table
| Aspect | SDET | QA engineer |
|---|---|---|
| Common emphasis | Software engineering applied to testability and feedback | Product risk, test coverage and quality evidence |
| Example work | Build test tooling, fixtures and CI integrations | Analyse requirements, explore risks and assess releases |
| Coding | Often a central responsibility | Ranges from occasional scripting to substantial engineering |
| Shared work | Test design, debugging and collaboration | Test design, debugging and collaboration |
| Title limitation | May be used for an automation-heavy tester | May include the same automation and tooling work |
Examples
SDET-shaped responsibility: a checkout suite has slow, unreliable setup. An engineer builds isolated test-data fixtures, improves diagnostics and integrates focused checks into CI. The value is dependable feedback, not the number of scripts written.
QA-engineer-shaped responsibility: another engineer identifies ambiguous coupon rules, explores refund journeys and explains uncovered risks before release. They may also implement automated API checks and help repair the fixtures.
These are illustrative allocations of work, not a universal job ladder. One person or one role can own both sets of responsibilities. Ask about the team's actual work before using a title to infer seniority.
How to answer in an interview
SDET usually means a software development engineer in test, with a strong emphasis on coding, tooling and testability. A QA engineer often has a broader product-testing focus, but may do just as much automation. For example, building reliable test fixtures and exploring risky checkout journeys are complementary responsibilities. I compare job descriptions by expected outcomes, coding ownership and release responsibilities rather than treating the titles as a fixed hierarchy.
Common confusion
Do not equate QA with manual-only execution or SDET with someone who never explores the product. Titles vary across employers. There is no title-based guarantee of salary, seniority or interview difficulty, and technical competence does not remove the need for domain understanding.
Likely follow-up: How would you assess a role? Ask who owns framework maintenance, exploratory testing, CI failures, environment setup and the final release-risk assessment.
Quick answers
Can a QA engineer build automation frameworks?
Yes. The title does not prevent that responsibility. Look at the actual engineering work and ownership expected.
Should a fresher choose by title alone?
No. Compare mentoring, product exposure, coding opportunities and day-to-day responsibilities. Ask for examples of recent work the role delivered.
Sources
Want a project you can show in interviews?
The portfolio project kit walks you through testing a deliberately buggy app with Selenium or Playwright and API tests, then explaining it. The app itself is free.