Manual QA vs SDET
Manual QA verifies software by designing and executing tests, exploring the product and reporting defects; the craft is finding what is wrong. An SDET is an engineer who writes code to test software: frameworks, automated suites, CI pipelines and tooling, interviewed with coding rounds. Both are QA; SDET pays more and requires programming. Many testers move across.
- Manual QA
- A tester who verifies software by designing and executing test cases, exploring the product and reporting defects, without automation as the core of the job.
- SDET
- A software development engineer in test: an engineer who writes code to test software, builds frameworks and tooling, and is interviewed like a developer.
How do Manual QA and SDET compare?
| Dimension | Manual QA | SDET |
|---|---|---|
| Core of the job | Manual QATest design, exploratory testing, execution, defect reporting | SDETWriting and maintaining test code, frameworks, pipelines and tooling |
| Daily tools | Manual QATest management tools, Jira, browser dev tools, Postman, spreadsheets | SDETAn IDE, git, a test runner, Playwright or Selenium, CI, Docker |
| Programming | Manual QAHelpful, not required; SQL and basic scripting are common asks | SDETRequired: one language well, data structures, clean code, code review |
| Interview format | Manual QAScenario questions, test case design, bug reports, process, sometimes SQL | SDETCoding exercises, framework design, automation debugging, system questions |
| Pay | Manual QAThe lowest of the QA tracks in the site's salary model | SDETThe highest of the general QA tracks in the site's salary model |
| Career ceiling | Manual QAQA lead, QA manager, product or business analysis | SDETStaff or principal engineer, architect, developer roles |
| What the market is doing | Manual QAFewer pure manual roles; most postings now ask for some automation | SDETGrowing share of QA postings; often the only QA title at product companies |
| Where each is strongest | Manual QAJudgement about risk, user behaviour and what to test | SDETMaking that judgement repeatable, fast and part of every build |
When should you choose Manual QA, and when SDET?
Choose Manual QA when
- You are strongest at understanding products, users and risk, and want to keep that as the centre of the job.
- You are entering QA without a programming background and want to start working now.
- The domain is complex or regulated and human exploratory testing is the main line of defence.
- You are moving towards product, business analysis or QA management rather than engineering.
Choose SDET when
- You enjoy programming and want the pay and ceiling of an engineering role.
- The companies you want to join hire SDETs as the only QA title.
- You want to build the tools and pipelines rather than run the tests by hand.
- You are willing to prepare for coding interviews, not only testing interviews.
How does Manual QA vs SDET come up in QA interviews?
This is the question behind a third of QA career conversations. Interviewers for either role want to hear that you understand the other: a manual tester who can explain what automation should and should not cover, and an SDET who can design a test case without a keyboard. The move across is common and interviewers know it.
- 01What is the difference between a QA engineer and an SDET in your view, and where do you sit?
- 02Describe a bug only a human would have found, and a bug only automation would have caught.
- 03You are a manual tester moving into automation. What have you built, and what would you build next?
- 04What should stay manual on a team with a strong automation suite?
No account needed · Scored in under a minute against a senior rubric
Common questions about Manual QA vs SDET
Is SDET higher than QA?
SDET is usually paid more and interviewed like a developer, and it is often the only QA title at product companies. It is not a promotion from manual QA in a fixed ladder; it is a different skill mix. Senior manual testers with deep domain judgement are valuable, but the pay ceiling is lower.
Can a manual tester become an SDET?
Yes, and many do. The usual path is one language learned properly, an automation framework built for a real product, a public repository showing it, and preparation for coding interviews. Testers bring test design judgement that engineers often lack, which is an advantage once the coding bar is met.
Is manual testing going away?
Pure manual roles are shrinking and most QA postings now ask for some automation. Exploratory testing, test design and risk judgement are not going away; they are being combined with automation skills in the same person. The safer career is the tester who can also code.
How different are the interviews?
Manual QA interviews focus on scenario questions, test case design, bug reports and process, sometimes with SQL. SDET interviews add coding exercises, framework design and debugging of automation, and expect developer-level answers about code quality and CI.
Where was this checked?
What should you read next?
Ready to be asked about Manual QA or SDET?
Practice explaining the trade-off to an interviewer who knows both.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account