QA Engineer, QA Automation Engineer, and SDET are not interchangeable titles
QA Engineer tests software manually and writes simple test cases. QA Automation Engineer writes test automation scripts (usually in Python, JavaScript, or Java). SDET (Software Development Engineer in Test) builds test frameworks, CI/CD pipelines, and owns testing infrastructure like a backend engineer owns production code.
The gap matters. A QA Engineer writing test cases by hand won't qualify for an SDET role. An SDET won't take a QA Automation Engineer job—the ceiling is too low. If you apply to the wrong category, your resume gets filtered out before the phone screen, even if you can technically do parts of the job.
QA Engineer: Manual testing, test case design, no code required
A QA Engineer's job is to find bugs by running applications and documenting what breaks. They write test cases (step-by-step instructions for how to test a feature), track bugs in Jira, and prioritize what the dev team should fix next. The work is exploratory and methodical—black-box testing.
Requirements: Basic testing frameworks (maybe Selenium), Excel, communication skills, attention to detail. No software engineering background required. Many QA Engineers come from non-technical backgrounds and learn on the job.
Career arc: Entry-level, 3-5 years median tenure, then you either specialize into automation/SDET or pivot to product management or BA roles. Limited upward mobility if you stay pure-play manual QA.
QA Automation Engineer: Writing test scripts, maintaining test suites
A QA Automation Engineer writes code (not production code, but test code) that automatically runs the same test cases repeatedly. Instead of clicking through a login flow 50 times yourself, you write a script that does it and tells you if it fails.
The work: Build test suites in Selenium, Cypress, Playwright, or similar frameworks. Debug flaky tests (tests that pass sometimes and fail sometimes for no clear reason). Maintain automation libraries as the application changes. Partner with developers and QA Engineers to determine what to automate.
Requirements: Fluent in at least one programming language (Python, Java, JavaScript). Understanding of software testing concepts (unit vs. integration vs. end-to-end). Git, CI/CD basics. A computer science degree or bootcamp training helps but isn't required if you can prove the skills.
Career arc: Mid-level role, 4-7 years typical, higher pay than QA Engineer, more stability. You can stay here for a decade if the role is senior enough. Or pivot to SDET by learning backend systems design.
SDET: Building the testing infrastructure, engineering the test platform
An SDET is a backend engineer who specializes in testing infrastructure. They don't write test cases—they write the systems that make testing possible at scale. Think: distributed test runners, custom test frameworks, test data generation pipelines, failure analysis dashboards, integrations with CI/CD systems.
The work: Design and build testing platforms. Debug infrastructure failures, not flaky tests. Collaborate with developers on testability (how to make the code easier to test). Write internal tools and libraries that QA Automation Engineers use. Optimize test execution time and cost. Own the testing tech stack the same way a backend engineer owns the production stack.
Requirements: Strong systems design knowledge. Proficiency in multiple languages (usually Go, Python, or Java for infrastructure). Deep understanding of CI/CD, containerization (Docker), and distributed systems. A degree in CS or equivalent experience as a backend engineer. SDETs come from production engineering and dev backgrounds, not testing backgrounds.
Career arc: Senior-level role, 6+ years of software engineering experience required. High pay, significant leverage, long tenure. Potential to move to staff engineer or principal engineer roles.
Side-by-side comparison
| Dimension | QA Engineer | QA Automation Engineer | SDET |
|---|---|---|---|
| Primary activity | Manual testing, exploratory testing | Writing test automation code | Building testing infrastructure |
| Coding required? | No | Yes (daily) | Yes (complex systems) |
| Entry point | Zero technical background okay | Some CS fundamentals required | Requires 5+ years backend engineering |
| Tools/frameworks | Jira, TestRail, basic web automation | Selenium, Cypress, Pytest, unittest | Go, Kubernetes, distributed testing frameworks |
| Typical level | Junior to Mid | Mid to Senior | Senior to Staff |
| Career longevity | Medium (risk of stagnation) | High (can advance to SDET) | Very high (senior IC track) |
Why this matters for your job search
If you're applying to jobs, the title on the requisition signals what the hiring team expects. If the job says "QA Engineer" and you list "5 years of test automation" as your top skill, they think you've overqualified or confused about the role. If they post "SDET" and your resume shows only Selenium experience with no infrastructure background, you get screened out.
The same rule applies in reverse: don't apply to an SDET role if your background is QA Automation. You'll lose the interview to someone who has worked on microservices, load testing, or CI/CD. You can learn it, but the phone screen assumes you already know it.
When negotiating or planning your next move, the title determines the ceiling. A senior QA Automation Engineer at a big company might make what a junior SDET makes at the same company. The SDET track is steeper but longer.
How to find the right QA role for you
Read the job description's "Required Skills" section first, not the title. If it lists only Jira and exploratory testing, it's a QA Engineer role. If it emphasizes Selenium or Cypress, it's QA Automation. If it mentions CI/CD design, microservices, or distributed systems, it's SDET.
Match your experience accordingly. Don't hedge your background. If you've spent three years building test frameworks and CI/CD pipelines, call yourself an SDET candidate. If you've spent three years running manual test cases, you're a QA Engineer—and that's a legitimate path into automation.
The speed of your application matters. Recruiters sorting through dozens of QA applications go fast. Being first with a matching resume beats being a perfect fit three hours later. GiraffyReach detects fresh job postings within seconds and auto-applies before the crowd, which cuts through the timing problem entirely—but you still need the right title match on your profile.