QA Engineer Salary Guide 2026: What Quality Assurance Actually Pays

A QA engineer in the United States earns a median base salary of $102,610 per year, according to the Bureau of Labor Statistics. That number is accurate and almost completely useless for anyone trying to budget a hire or negotiate an offer. The reason is that “QA engineer” covers at least three distinct jobs in 2026, and the salary gap between them is $40,000 or more. A manual tester running regression scripts in Jira is not the same hire as an SDET building Playwright frameworks in TypeScript, and the comp tables don’t care about your job title.

Robert Ardell here. I recruit for IT staffing at KORE1, and QA is one of the roles where I spend the most time re-educating hiring managers on what they’re actually paying for. About a third of the QA reqs that land on my desk have a budget mismatch baked in from the start. The JD says “QA engineer,” the budget says $90K, and the actual work described requires someone who can write CI-integrated test suites in Cypress or Playwright and spin up containerized test environments. That person costs $120K to $140K in most markets. The search stalls at week four, the hiring manager blames the candidate pool, and we end up having the conversation we should have had during intake.

Everything below pulls from BLS occupational data, aggregator salary reports from Glassdoor, ZipRecruiter, and PayScale, and the QA placements we’ve run through our desk over the past eighteen months. I’ll flag where the data sources disagree, because they do, and the variance itself tells you something useful about this market.

QA Engineer Salary in 2026, by the Numbers

The BLS classifies QA engineers under occupation code 15-1253, “Software Quality Assurance Analysts and Testers.” Their May 2024 data puts the national median at $102,610, with 10th percentile earners at $60,690 and 90th percentile at $166,960. The full spread looks like this.

Source: Bureau of Labor Statistics, Occupational Employment and Wage Statistics, May 2024.

That $102,610 median sits almost exactly where the aggregators land too. Glassdoor reports $101,387. ZipRecruiter comes in at $95,168. PayScale is the outlier at $82,694, likely because their sample skews toward earlier-career respondents who self-report. When three sources cluster around $95K to $103K and one outlier sits at $83K, the cluster is probably closer to reality.

None of those numbers are going to tell you what your next QA hire actually costs, because the spread between a manual tester and an SDET building Playwright suites inside a CI pipeline is wider than the spread between junior and senior in most other engineering roles. Not because they’re wrong. Because the job title hides too much.

The Three Jobs Hidden Inside “QA Engineer”

This is the part that costs hiring managers money. The title “QA engineer” gets applied to roles that share almost no daily workflow, and the salary bands barely overlap at the senior level.

Manual QA / QA Analyst. Runs test cases, files bugs, validates user stories against acceptance criteria. Tools are Jira, TestRail, maybe Postman for API spot checks. This is the role that the $60K to $85K range in the BLS data actually represents. It’s real work. Somebody has to do exploratory testing and edge-case thinking that automation doesn’t catch. But the market is compressing hard on comp for this profile. Two years ago I’d see manual QA reqs at $95K in Orange County. Now the same companies are posting $78K for the same scope. Part of that is AI-assisted test generation eating into the rote execution side of the job.

Last November, a SaaS company in Irvine brought us a req for a “QA engineer” at $88K. When I got on the intake call, the hiring manager described the work as writing and maintaining test cases in TestRail, running regression before each sprint release, and filing bugs with repro steps. No automation. No code. Solid, necessary work, and the $88K budget was about $8K above where that particular market segment was actually clearing at the time, which meant we had more candidates than usual responding to the posting and could afford to be selective about communication skills and bug-reporting rigor in a way that you normally can’t when the budget is tight. We filled it in eleven days. The candidate had four years of manual QA experience and a QA certification from ISTQB that nobody on the engineering team asked about during the interview. They asked about her bug triage process instead. Smart.

QA Automation Engineer. Writes and maintains automated test suites. Cypress, Playwright, Selenium, maybe Appium for mobile. Integrates tests into CI pipelines, usually GitHub Actions or Jenkins. This person codes daily. They might not build product features, but their test infrastructure is production-grade code with its own review process. The salary band here runs $100K to $140K for mid to senior, and the premium tracks directly to which frameworks they know, which is one of the few places in tech hiring where a specific tool on the resume moves the offer number by five figures rather than just getting the candidate past the recruiter screen. Playwright roles at modern tech companies and fintechs are paying 6 to 7 percent more than equivalent Selenium roles at enterprise shops, according to ZipRecruiter’s 2025-2026 data. The framework itself doesn’t make the engineer better. But the companies adopting Playwright tend to pay more across the board.

SDET (Software Development Engineer in Test). This is a developer who happens to work on test infrastructure. They build frameworks from scratch, own the test architecture across multiple services, write shared libraries, and sometimes contribute to production code. At major tech companies, SDET compensation packages are nearly identical to SWE roles at the same level. Senior SDETs clear $145K to $170K base, with total comp (equity, bonus) pushing past $200K at large public companies. A senior SDET earns $45,000 to $55,000 more per year than a senior manual QA at the same organization. Same department. Same standup. Different career ladder entirely.

When a req lands on my desk that says “QA engineer, $95K,” the first question I ask is which of these three roles the team actually needs. About 40 percent of the time, the answer reveals a mismatch that would have burned six to eight weeks of search time.

QA Engineer Salary by Experience Level

Experience premiums in QA are steeper than most people expect, because the gap isn’t just about years. It’s about the shift from executing test plans to designing test strategy.

The jump from junior to mid-level is mostly about automation literacy. Can you write tests, not just run them? The jump from mid to senior is about architecture. Can you design a test strategy for a system you didn’t build? The jump to staff or director is about influence. Can you make quality a priority for teams that don’t report to you?

A candidate I placed last year had seven years of experience but had spent all of it in manual QA at a single healthcare company. Good tester. Thorough. But her salary had plateaued at $94K because the company never invested in automation, and she’d never needed to learn it. She spent four months teaching herself Playwright on the side, built a portfolio project automating a public API’s test suite, and we placed her into a mid-level automation role at $118K. A $24K raise because she changed what she could do, not how long she’d been doing it.

QA Salary by Location: Where Geography Still Matters

Remote work has flattened salary bands for a lot of tech roles. QA is one of the places where geography still creates a real premium, partly because a lot of QA work happens inside regulated industries (healthcare, fintech, defense) where on-site or hybrid is still the default.

Sources: Built In, Glassdoor, PayScale, 2026 data.

San Diego stands out as the odd number in Southern California, and it confuses hiring managers who assume the whole region prices the same way. It reads lower because the defense contractors and biotech firms there run a lot of QA under “test engineer” or “verification engineer” titles that don’t show up in these aggregators, even though the work is functionally the same. If you’re hiring QA in San Diego and benchmarking against the $87K average, you’ll probably undershoot for automation talent by $15K to $20K. We’ve lost candidates in San Diego searches specifically because hiring managers anchored to that number instead of looking at what Playwright-capable engineers were actually accepting.

For a broader look at how QA comp fits into the Southern California tech market, our SoCal IT salary trends report breaks down the regional picture across roles.

QA Salary by Industry: Who Pays the Most

Industry matters more for QA salaries than it does for most engineering roles, because the consequences of quality failures vary wildly. A bug in a consumer social app is an annoying user experience. A bug in a medical device kills the product launch and maybe triggers an FDA recall. The stakes shape the comp.

Glassdoor’s 2026 industry breakdown for QA engineers shows the spread clearly.

• Aerospace and Defense: $115,453 median total pay. These teams test firmware, embedded systems, and flight control software under DO-178C or MIL-STD-882E compliance frameworks. The testing is slow, methodical, and heavily documented. Manual QA actually pays well here because the documentation rigor is the point.
• Manufacturing: $114,680. A lot of this is automotive and industrial IoT. The QA engineer is testing the software that runs on a factory floor, not a web app.
• Financial Services: $112,039. Regulatory compliance drives the premium. SOX, PCI-DSS, and internal audit requirements mean QA artifacts are legal documents, not just engineering artifacts.
• Insurance: $107,462. Similar compliance dynamics as financial services, but the systems tend to be older. A lot of the QA work involves testing against mainframe interfaces, which is a surprisingly well-compensated niche because nobody under 35 wants to do it.
• Energy and Utilities: $105,915. SCADA systems, grid management software, safety-critical testing. Clearances sometimes required.

Consumer tech and SaaS companies often pay less base but more in equity, which makes direct comparisons misleading. A QA engineer at a pre-IPO fintech making $105K base with $40K in RSUs is not earning less than the aerospace QA making $115K base. The risk profiles are different, but the total comp might not be.

The Automation Premium: Why Tooling Knowledge Moves the Needle

Seventy-seven percent of QA job postings in 2026 require coding skills. In 2023, that number was 53 percent. The shift is not subtle.

What that means for salary is straightforward. A QA engineer who can write and maintain automation in a modern framework earns $20K to $40K more than one who cannot, at the same experience level, in the same market. That is the single largest salary lever in this role outside of switching to management.

The framework-specific premiums are real but smaller than the automation-vs-manual gap. ZipRecruiter’s data through early 2026 shows Cypress medians up roughly 6 to 7 percent year over year, while Selenium medians have dropped 9 to 10 percent. Playwright sits at the top of the framework pay scale, with average US salaries around $116,607 for engineers with Playwright as a primary skill. But the framework premium is mostly a proxy for company type. Playwright roles cluster at modern tech companies and fintechs that pay more across every role. Selenium roles dominate at enterprise shops (banks, insurers, government contractors) with more structured, and often lower, pay scales.

Should you learn Playwright because it pays more? Probably, yes, if you’re optimizing for comp and you’re early enough in your career to absorb the ramp-up time without losing current income. But not because the framework itself commands a premium. Because the companies that adopt it are the ones with the budget to pay market rate.

A QA engineer who invests twelve months learning SDET-level skills can expect a $20,000 to $40,000 salary increase in their first SDET role, with compounding growth from there. That number comes from placement data and aligns with what we see in our own queue. The career math is hard to argue with.

QA Engineer vs. SDET vs. QA Lead: Salary Comparison

The career paths diverge early, and the comp diverges with them.

The SDET path is the one that reaches developer-level compensation, because the work is developer-level work. At major tech companies, SDET comp packages are nearly identical to SWE packages at the same level. The manual QA path plateaus earlier, not because the work is less important, but because the market has decided it’s more replaceable. Whether that pricing is fair depends on who you ask, and most QA managers I talk to have strong opinions about it that don’t match what the market is willing to pay. The salary data doesn’t care about fair.

Something I keep running into on intake calls this year: the QA Lead and QA Manager roles are getting harder to fill, not easier, and the reason is a compensation problem that most companies haven’t figured out how to solve yet. Companies that laid off middle management in 2023 and 2024 are realizing they still need someone to own the test strategy across teams, and the engineers who would be natural fits for those roles would rather stay on the IC track where the comp is higher. If you’re a senior QA engineer debating the management move, the money doesn’t favor it unless you’re aiming for director or VP.

The AI Factor in QA Salaries

It’s impossible to write about QA engineering in 2026 without talking about AI’s effect on the role. The short version: AI is changing what QA engineers do, not eliminating the need for them. The salary data supports this.

The BLS projects 15 percent growth for software developers, QA analysts, and testers from 2024 through 2034, with roughly 129,200 openings per year. That growth rate is “much faster than the average for all occupations,” their words. The AI doom narrative and the BLS data are looking at different realities.

What is actually happening, from what I see in the reqs that come through our desk: AI tools are handling test case generation, reducing the time QA engineers spend writing boilerplate assertions. Copilot and similar tools auto-suggest test code. AI-powered test maintenance tools flag flaky tests and suggest fixes. The rote execution part of QA is compressing. The judgment part, knowing what to test, when the edge case matters, and how to communicate a quality risk to a product team, is not.

Fifty-eight percent of enterprises are actively upskilling their QA teams in AI tools, according to the ThinKSys QA Trends Report 2026. That is not what you do to a role you’re about to eliminate. That’s what you do to a role you’re investing in differently.

For salary, the implication is that manual-only QA comp will continue to compress, while QA engineers who can work with AI tools, write automation, and reason about test strategy will see their premium grow. The split is already visible in the data. It’s going to get wider.

What Hiring Managers Get Wrong About QA Budgets

I’ll keep this section blunt because the mistakes repeat.

The most common one: budgeting at the median. The BLS median of $102,610 is a national number that includes manual QA analysts in low-cost-of-living markets. If you’re hiring an automation engineer in Los Angeles or Orange County, the median is not your benchmark. The 75th percentile ($131,870) is closer to your reality for a senior hire. Start at the median and you’ll interview for eight weeks before adjusting upward anyway.

Second mistake: treating QA comp as “developer comp minus 20 percent.” This mental model worked ten years ago when QA was a downstream function that received code and tested it. In 2026, SDETs are writing production-quality test infrastructure that lives in the same CI pipeline as the application code, gets reviewed in the same pull request workflow, and breaks the build just as hard when it fails, which makes the argument for paying them less than the developers whose code they’re validating harder and harder to defend in an offer negotiation. The discount assumption costs you the candidates who have options.

Third mistake, and this one is specific to our market: confusing software engineer staffing budgets with QA budgets. They’re different labor markets with different supply dynamics. The software engineer market is oversaturated at the junior level and tight at the senior level. QA automation is tight at every level because fewer CS graduates self-select into QA as a first career choice. The pipeline is thinner, and the pricing reflects it.

If you want to benchmark a specific role against current market data, our salary benchmark tool can give you a starting range. It won’t replace an intake conversation, but it’ll get you closer than Googling “QA engineer salary” and using the first number you see.

How to Maximize QA Engineer Compensation

If you’re a QA engineer reading this for career guidance rather than hiring intel, here’s what the data says about where the money moves.

Learn automation if you haven’t. That is the single highest-ROI investment in this career path. The $20K to $40K salary jump from manual to automation is documented across every source I’ve cited, and it compounds. A manual QA engineer at year ten might earn $100K. An automation engineer at year ten might earn $155K. Same starting point, different trajectory, and the divergence started with whether they learned to write test code.

Pick a modern framework. Playwright adoption is accelerating. Cypress is mature and widely used. Selenium still has the largest installed base, but the salary trend is downward for Selenium-only engineers. If you already know Selenium, adding Playwright takes a few months of evenings, not a career reset.

Consider the SDET path seriously. The comp approaches SWE parity at senior levels, and the competition for senior SDET roles is lower than for senior SWE roles because fewer people target it deliberately. Most SDETs I’ve placed fell into the role sideways, from QA or from development. The intentional path is less crowded.

Don’t ignore domain expertise. A QA engineer who knows HIPAA validation testing inside a healthcare SaaS platform, who understands what PHI exposure looks like in a test log and which edge cases trigger OCR audit flags, is worth substantially more than a generalist with identical automation skills, because that domain knowledge took years of regulated-environment experience to accumulate and cannot be replicated by running through a Udemy course over a weekend. Defense, fintech, and healthcare all pay premiums for QA engineers who understand the regulatory testing requirements, and that premium stacks on top of the automation premium.

Negotiate with data. Bring the BLS percentile table. Bring the Glassdoor industry breakdown. Show the hiring manager the gap between their offer and the 75th percentile for the specific type of QA work you’ll be doing. “QA engineer” is vague enough that you can almost always make a case for a higher benchmark if you specify the actual scope. Our salary negotiation guide for tech professionals walks through the mechanics.

QA Market Outlook Through 2034

The global software testing market is projected to roughly double over the next decade, from $55.8 billion in 2024 to $112.5 billion by 2034, and the automation segment inside that number is growing even faster at 14.5 percent annually, which tells you where the hiring pressure is going to land. Automation testing alone is projected to go from $28.1 billion in 2023 to $55.2 billion by 2028. The money is following the automation side of the market, and it’s not close.

QA engineering positions grew 17 percent over the past year while traditional development roles grew at 9 percent. That surprised me too. QA is outpacing dev hiring. The explanation, once you sit with it for a minute, is actually straightforward: release velocity keeps increasing across nearly every engineering org, AI-generated code is creating more testing surface area rather than less, and the shift-left movement is pulling QA involvement earlier into the development cycle, which means companies need more QA capacity even as they automate the execution layer. More code shipping faster means more testing surface area. The demand is structural.

For hiring managers weighing whether to staff QA now or later: the market is tighter than the title suggests. QA automation engineers with 3+ years of experience are fielding multiple offers in most major metros. If you’re running a search through an IT staffing partner, expect somewhere between 3 and 5 weeks for a strong mid-level automation hire, and 6 to 10 weeks for a senior SDET, although those timelines compress significantly when the hiring manager is willing to move fast on interviews and the comp band is set at or above the 75th percentile from the start. Manual QA fills faster, usually under 3 weeks, because the candidate pool is larger and the comp negotiations are simpler.

Things People Ask About QA Engineer Pay

So what does a QA engineer actually earn right out of school?

$60,000 to $84,000 for the first couple of years, depending heavily on whether you land somewhere that starts you on automation or manual work. PayScale’s data shows entry-level total comp averaging around $68K, while ZipRecruiter’s numbers run closer to $84K. The gap is partly geographic and partly about whether the role has “automation” in the title. Entry-level positions with Selenium or Cypress in the requirements pay $8K to $12K more than the ones that just say “QA” or “tester.” Worth paying attention to when you’re comparing offers.

Is QA engineering a dead-end career in 2026?

No, but the version of it that involves only running manual test scripts is shrinking. The BLS growth projection of 15 percent through 2034 applies to the category as a whole. Inside that number, the demand is shifting toward automation, AI-augmented testing, and test architecture. A QA engineer who keeps learning has a wider career aperture now than five years ago, not a narrower one. The people calling QA a dead end are usually comparing it to software engineering comp, which is a valid observation about relative pay but not evidence that the role is disappearing. It isn’t.

Do QA engineers earn less than software developers?

At the manual QA level, yes, typically 15 to 25 percent less. At the SDET level, the gap mostly closes. Major tech companies pay SDETs on the same bands as SWEs of equivalent seniority. The BLS median for software developers is around $132,270 versus $102,610 for QA. But that comparison mixes manual QA into the QA number and pulls it down. When you compare a senior SDET pulling $145K to $170K against a senior software engineer in the $150K to $175K range, the gap shrinks to maybe $5K or $10K, which is a rounding error in a negotiation, not the $30K chasm that the headline medians make it look like.

Realistically, how much can I increase my salary by learning automation?

$20,000 to $40,000 in your first automation role, based on both aggregator data and our placement history. That range is wide because it depends on what you automate and which framework you learn. A manual QA engineer making $85K who learns Playwright well enough to own a test suite can reasonably target $110K to $120K within twelve to eighteen months. I’ve seen it happen faster for engineers who already had some scripting background. The ROI per hour of study time is higher than almost any certification you could pursue instead.

ISTQB certification, does it actually move the salary needle?

Barely. In our experience, hiring managers in the US rarely ask for ISTQB during interviews, and I can think of maybe two placements in the past year where the certification was mentioned in the offer negotiation. It matters more in European and Asian markets. In the US, a GitHub portfolio of automation projects will do more for your salary than ISTQB Foundation Level. Certifications that do move the needle: AWS Certified (for QA in cloud environments), security certifications like CompTIA Security+ (for QA in regulated industries), and framework-specific credentials when they exist. ISTQB won’t hurt you. It just won’t be the thing that gets you the raise.

Contract QA rates versus full-time, what’s the gap?

$55 to $85 per hour for contract QA automation engineers through a staffing firm, which annualizes to $114K to $177K before you account for the benefits gap. Full-time QA automation at the same level runs $100K to $140K with benefits. The contract rate looks higher on paper and it is higher in gross dollars, but once you subtract health insurance out of pocket at $6K to $12K per year, zero PTO, no 401k match, and no equity component, the real premium that the contractor actually takes home versus a salaried employee doing identical work drops to roughly 10 to 15 percent, which is a lot less dramatic than the 30 to 40 percent gap the raw hourly math would have you believe. Some engineers prefer contract because they want flexibility or because they’re testing a new industry. Others prefer it because they can make more money in fewer months and take time off between engagements. The math works differently for everyone. If you want to explore contract staffing options for QA, that page breaks down how the engagement model works.

If you’re building or scaling a QA team and want to talk comp strategy before you post the req, reach out to our recruiting team. We’ll tell you what the role is actually clearing in your market before you commit to a budget that stalls the search.