QA engineer career path
Around mid-level, QA careers split in two. One track is SDET and automation work, which is software engineering aimed at quality. The other is quality leadership, owning test strategy and release risk across teams. QA is also a common side door into other engineering jobs, since testers learn the whole product. How much real code you write decides which doors open.
Updated Pay and job counts from live US job listings
What comes after QA engineer?
A common next step for a QA engineer is test automation engineer, usually 1-3 years in. Other routes are a step up to QA manager, a sideways move to performance engineer or DevOps engineer, and a career change to software engineer.
QA engineer jobs in the US
We couldn't load live job numbers. The listing feed may be busy. Check back tomorrow.
Where QA engineers go next
5 moves people make from this role. The job counts and pay are for each destination role, so you can see what the market wants right now.
| Move to | Type | Usually when | Open US jobs | Advertised pay |
|---|---|---|---|---|
| Test automation engineer | Step up | 1-3 years in | 1,066 | $90K-$128K |
| QA manager | Step up | 5-7 years in | 461 | $105K-$136K |
| Performance engineer | Sideways move | 3-4 years in | 1,059 | $97K-$134K |
| Software engineerIts career path: software engineer | Career change | After 2-4 years writing automation in a general-purpose language like Java | 59,275 | $103K-$141K |
| DevOps engineerIts career path: DevOps engineer | Sideways move | 2-4 years in | 3,469 | $114K-$130K |
Job counts and pay from US listings, September 29, 2026. Pay shows only where at least five listings state it.
What each move takes
Why each move fits, the skills hiring managers look for, and the proof to have on your resume before you apply.
Test automation engineer
Step up1,066 open US jobs$90K-$128K advertised
You already know what to test and where the product breaks. Now the automation itself is your output, and you own the framework, the CI setup and a suite people actually trust.
- Usually when
- 1-3 years in, as soon as writing and fixing automated tests is part of your normal week
- Skills to add
- Playwright or Cypress with TypeScript
- API testing with REST Assured or Postman and Newman
- Running suites in CI with GitHub Actions or Jenkins
- Fixture and page object design
- Test data management
- Have this on your resume first
- Automation you built that runs in CI on every change, with the suite's runtime and flake rate.
QA manager
Step up461 open US jobs$105K-$136K advertised
Deciding whether a release is safe to ship is a manager's judgment call, and senior QA engineers make it every sprint. Management adds the team, the test strategy and the risk talk with engineering leaders.
- Usually when
- 5-7 years in, usually after leading release sign-off or coordinating other testers
- Skills to add
- Risk-based test strategy
- Quality metrics: escaped defects and change failure rate
- Hiring and coaching testers
- ISTQB Advanced Level Test Manager
- Have this on your resume first
- A quality process you introduced across a team, with defect or release numbers from before and after.
Performance engineer
Sideways move1,059 open US jobs$97K-$134K advertised
It's the same instinct as functional testing, aimed at a different failure. You still build a realistic scenario and push until something breaks, but what breaks is speed and capacity.
- Usually when
- 3-4 years in, often after running load tests ahead of a big launch
- Skills to add
- k6, JMeter or Gatling
- APM tools such as Datadog or New Relic
- Profiling and reading flame graphs
- Capacity planning
- Have this on your resume first
- A load test you designed that found a real bottleneck, with numbers from before and after the fix.
Software engineer
Career change59,275 open US jobs$103K-$141K advertised
Automation engineers already write code daily, read product code and join code reviews. What's missing is designing and owning features, plus getting through coding interviews.
- Usually when
- After 2-4 years writing automation in a general-purpose language like Java, Python or TypeScript
- Skills to add
- Data structures and algorithms for coding interviews
- One application framework such as Spring Boot, Django or React
- Unit testing and test-driven development in product code
- System design basics
- Have this on your resume first
- Code merged into the product itself, such as bug fixes or testability hooks, and not only into the test repo.
DevOps engineer
Sideways move3,469 open US jobs$114K-$130K advertised
Own the test environments and a pipeline stage or two, and you're already doing release engineering. DevOps widens that from the test stage to the whole path to production.
- Usually when
- 2-4 years in, if you already maintain the pipelines your tests run in
- Skills to add
- Docker
- Terraform
- Kubernetes fundamentals
- AWS Certified SysOps Administrator Associate
- Have this on your resume first
- Pipeline or environment work you owned, like throwaway test environments or a faster pipeline, with the numbers.
Now check your own resume
Your own resume will give you a sharper answer than this page. Your years, tools and wins change which move fits.
The suggested roles and fit scores come from AI. The job counts and pay come from live listings.
Questions QA engineers ask
Can a QA engineer become a software developer?
Yes, and it's one of the most common internal moves in engineering. What decides it is how much real code you write. Get into automation first, then start contributing fixes to the product codebase. Expect standard developer interviews, so practice the coding problems QA never asked of you.
Is QA a dead-end job?
Manual-only QA can be, because that work is easy to cut and rarely leads anywhere on its own. QA with automation, CI and performance skills leads to SDET, quality leadership, DevOps and development roles. If your job is all manual testing right now, automate part of it first.
Should I become an SDET or a QA manager?
Pick SDET if you want to stay close to code and keep a path open to development roles. Pick management if you care more about how teams decide what's safe to ship, and you like coaching. SDET is easier to back out of, because QA management jobs are scarcer.