SDET vs QA vs STE: What's the Difference?
SDET (Software Development Engineer in Test) builds test frameworks and tooling and needs strong coding skills. QA (Quality Assurance) owns overall product quality across manual and automated testing and process. STE (Software Test Engineer) focuses on executing test cases, finding bugs, and light automation. In short: SDET builds the test process, QA ensures quality, STE executes it.
Beginners — and plenty of experienced professionals — mix up SDET, QA, and STE. All three exist to protect software quality, but their day-to-day work, technical depth, and how much automation they own are quite different. This guide breaks down each role side by side so you can tell them apart and decide which one fits the career you want.
Key takeaways
- SDET = more coding + automation + framework development; the most engineering-heavy testing role.
- QA = overall product quality across manual and automated testing, with a strong process focus.
- STE = test execution + bug reporting + basic automation; a strong entry point into testing.
- Key takeaway: SDET builds the test process, QA ensures quality, and STE executes the test process.
- The roles overlap and careers move between them — the split is about center of gravity, not rank.
How the three roles connect
tap a role to focus →Thicker lines mean the role leans harder on that skill. Tap a role to isolate it and highlight its column below.
← swipe the diagram →
Which one to pick
You need automation frameworks, tooling, and CI-integrated test code built from scratch.
You need someone to own product quality end-to-end and shape the testing process.
You need test cases executed, bugs reported, and a dependable tester who can grow.
At a glance
| Aspect | SDET | QA | STE |
|---|---|---|---|
| Primary focus | Test automation, framework development, and tool creation | Overall product quality across manual and automated testing | Test case execution, bug reporting, and test running |
| Responsibilities | Write and maintain automated tests; build test frameworks and tools | Design and execute test cases; run manual and automated testing (functional, regression) | Write and execute test cases; identify and report bugs |
| Skills required | In-depth coding (Java, Python, C#, etc.) and strong programming fundamentals | Testing methodologies (black/white box), test-case design, defect prevention | Testing tools and methodologies plus working knowledge of automation tools |
| Test approach | Deep expertise in automation frameworks (Selenium, Playwright) and CI/CD integration | Issue tracking (Jira) and ensuring quality across the whole testing process | Defect tracking and executing test cases with some automation |
| Technical depth | High — centered on coding and test-framework development | Varies, typically lower coding depth than SDET | Moderate — focused on testing and automation execution |
| Automation focus | Strong — writing automated tests and frameworks is the core of the job | Optional but not always primary; blends manual and automated | Some automation, but not as heavy as SDET |
SDET (Software Development Engineer in Test)
An SDET sits closest to development. The role is defined by strong coding skills used to build automation frameworks and testing tools, develop and maintain automated tests, and work closely with CI/CD pipelines. An SDET is expected to reason about architecture, write maintainable test code, and treat the test suite as a real software product. If you enjoy programming as much as testing, this is the most engineering-heavy of the three roles.
QA (Quality Assurance)
QA is the broadest role. It's responsible for overall software quality: designing and executing test cases, performing both manual and automation testing, and focusing on process, quality, and defect prevention. A QA engineer thinks about the whole quality picture — requirements, risk, coverage, and process — rather than only writing code. Coding depth varies, and automation is one tool among many rather than the entire job.
STE (Software Test Engineer)
An STE is execution-focused. The role centers on executing test cases, identifying and reporting bugs, and using automation tools when needed, with more emphasis on test execution than framework development. It's an excellent entry point into testing: you build strong fundamentals in test design and defect reporting, and you can grow toward SDET by deepening coding skills or toward QA by broadening into process and strategy.
Which role should you pick?
Pick SDET if you want more coding, automation, and framework development. Pick QA if you want to own overall product quality across manual and automated testing and shape process. Pick STE if you want to focus on test execution, bug reporting, and basic automation while you build experience. None is strictly 'higher' than the others — they're different centers of gravity, and many careers move between them over time.
FAQ
An SDET builds test automation frameworks and tools and needs strong coding skills. QA owns overall product quality across both manual and automated testing and focuses on process and defect prevention. An STE focuses on executing test cases, reporting bugs, and using automation tools when needed. In short: SDET builds the test process, QA ensures quality, and STE executes the tests.
Sources
Related tools
Related guides
Selenium to Playwright: The SDET Roadmap (2026)
A 10-stage roadmap for Selenium engineers moving to Playwright — a Selenium→Playwright translation table, the habits to unlearn, real code, and progress tracking that remembers where you stopped.
Best MCP Servers for QA & Test Automation (2026)
The best Model Context Protocol (MCP) servers for QA engineers in 2026 — Playwright, GitHub, Atlassian/Jira, Filesystem, and database MCP servers for AI-assisted testing. Free and open-source.
Claude Cowork "Record a Skill": Teach AI by Showing It (2026 Guide)
Anthropic's Record a Skill turns a narrated screen recording into a reusable Claude Skill. How it works, step-by-step setup, 8 real cases (incl. QA workflows), what to keep off screen, and limits — updated July 2026.