QA engineer salary in 2026: tech hubs, nationwide and remote
Market benchmarks updated July 2026
In 2026, a mid-level QA engineer in the US earns $80k–$105k in base salary nationwide, $100k–$131k in major tech hubs and $76k–$100k for fully remote roles (tensionscore benchmarks updated July 2026, based on BLS OEWS, Robert Half, Stack Overflow Developer Survey 2025 (US), Glassdoor 2026 (PM, design, mobile), BLS ECEC Q4 2025 (employer cost), SHRM). Including recruiting and the cost of the search, the first year costs the employer $129k–$192k at the national level.
Base salary by seniority and location
Seniority
Major tech hubs
Nationwide
Remote
Junior
$75k–$100k
$60k–$80k
$57k–$76k
Mid-level
$100k–$131k
$80k–$105k
$76k–$100k
Senior
$131k–$166k
$105k–$133k
$100k–$126k
Lead
$166k–$209k
$133k–$167k
$126k–$159k
Annual base salary excluding bonus and equity, in thousands of dollars.
Time-to-hire and real first-year cost
Seniority
Median time-to-hire
Major tech hubs
Nationwide
Remote
Junior
1–3 months
$121k–$182k
$97k–$146k
$92k–$139k
Mid-level
1–3 months
$161k–$240k
$129k–$192k
$122k–$182k
Senior
2–4 months
$225k–$321k
$180k–$257k
$171k–$244k
Lead
2–4 months
$285k–$404k
$228k–$323k
$217k–$307k
First-year total = fully loaded salary + recruiting cost + cost of delay (months without the skill), in thousands of dollars.
How location changes the numbers
Major tech hubs: about 25% above the national figures.
Nationwide: in line with the national figures.
Remote: about 5% below the national figures.
Major tech hubs means high-cost metros such as the San Francisco Bay Area, New York or Seattle. These gaps are a coefficient applied to the national benchmark, not city-by-city surveys; time-to-hire does not change. Details in the methodology.
The real first-year cost, in detail
For a mid-level QA engineer nationwide, the advertised salary is only the visible part:
Fully loaded salary$104,000 – $136,500
Recruitment cost$16,000 – $21,000
Cost of delay (months without the skill) (over a median time-to-hire of 1–3 months)$8,667 – $34,125
First-year total$128,667 – $191,625
Assumptions
Fully loaded salary = base salary × 1.3 (benefits and employer taxes, BLS employer-cost data).
Recruiting cost = 20% of annual base salary, the typical agency fee; hiring directly costs less but takes internal time.
Cost of delay = monthly loaded salary × months without the skill: the value the role should have produced during the search.
A QA engineer makes sure your software works before customers find out it doesn’t. The role splits into two crafts: manual testing — methodically exercising the product like a demanding user — and test automation, which is genuine programming: writing code that checks the product on every release, automatically.
Good QA is a speed investment, not a brake. Teams without it ship slower over time, because developers burn hours re-checking old features by hand and firefighting bugs found by customers. A strong QA hire turns releases from a gamble into a routine — that’s the actual product you’re buying.
The miscasting mistake is treating QA as an entry-level clicking job. Manual and automation are different skill sets at different price points, and an ad that says “QA engineer” while meaning “someone cheap to click through screens” repels the automation profiles who could transform your release process.
What moves the range
Automation skill is the main price lever: an engineer who writes test code and wires it into your deployment pipeline is a developer in their own right and priced accordingly, well above manual-only testers. Seniority and product complexity move the number further — testing an app that handles payments or regulated data demands more rigor, and the market knows it.
Being the first QA hire carries a premium of its own: that person defines your whole quality approach from scratch, tools included, rather than slotting into an existing system. Expect to pay for that autonomy — it’s what you’re actually hiring.
Writing the job ad for this role
Say plainly whether the role is manual testing, automation, or building automation from zero — these attract different people and the ambiguity costs you the best ones. Describe the product, the release rhythm, and what exists today, even if the honest answer is “nothing, you’d be first.” That’s a selling point for the right profile. Name the tools if you have them; if you don’t, say the hire gets to choose. Precision here signals you take quality seriously — which is exactly what QA candidates screen for.
Paste your developer job ad: score, real time-to-hire, first-year cost and what’s driving candidates away — free, in 30 seconds.
Based on market benchmarks updated July 2026, a mid-level QA engineer earns $80k–$105k in base salary nationwide, $100k–$131k in major tech hubs and $76k–$100k for fully remote roles. Pay climbs with seniority: the per-level detail is in the table on this page.
Do QA engineers earn more in tech hubs?
Yes: in major tech hubs, QA engineer pay runs about 25% above the national figures, while fully remote roles pay about 5% less. Time-to-hire stays similar (1–3 months for a mid-level QA engineer): competition for strong candidates is tough everywhere.
Do I need a QA engineer, or can developers test their own code?
Developers should test their own code — and it’s never enough. They test what they built the way they meant it to work; a QA engineer tests the way real users actually behave, and catches what falls between features. The tipping point: bugs reaching customers regularly, or releases so nerve-wracking that shipping slows down. That’s when dedicated QA pays for itself.
Manual QA or test automation — which should I hire for?
Most growing products need both, in sequence. Manual testing catches usability problems and one-off issues no script foresees; automation keeps every past feature verified on every release without human hours. If you release frequently, automation is what stops testing from becoming the bottleneck. A pragmatic first hire is someone who tests manually and automates the repetitive parts as they go.
When should a small team hire its first QA engineer?
Watch for the symptoms rather than a headcount rule: customers report bugs you should have caught, releases keep slipping because retesting everything by hand takes days, or developers dread deploying. Once quality problems visibly cost you customers or speed, the hire is overdue — and a first QA who sets up automation compounds in value with every release after.