QA strategy
QA engineer salary: the full cost of a QA hire in 2026, and the alternatives
What a QA engineer costs a US company in 2026: BLS salary figures, benefits on top, hiring time, hidden costs, and what drives the price of the alternatives.
The U.S. Bureau of Labor Statistics (BLS) has no occupation called QA engineer. The closest one, software quality assurance analysts and testers, had a median annual wage of $104,300 in May 2025, the figure in the BLS handbook as of October 2026. That median QA engineer salary is not what the hire costs you. Add benefits and payroll costs at the shares US private employers paid in June 2026, and by our arithmetic a QA engineer at the median costs a company about $136,000 a year, or about $11,300 a month, before recruiting, tools and the time your team spends managing the role.
Below: the salary range, the arithmetic with every input labeled by source and period, what hiring takes, the costs that are hard to put a number on, and what drives the price of the alternatives. Every figure is a US figure from a primary source listed at the end; where we found none, we give no number.
QA engineer salary: what BLS reports
BLS defines the occupation (SOC code 15-1253) as workers who “develop and execute software tests to identify software problems and their causes,” document defects in a bug tracking system and report them to developers. Its Occupational Employment and Wage Statistics (OEWS) survey counted 186,740 of them in May 2025, not counting people who work for themselves. If you searched for a QA tester salary, the figures are the same: BLS counts analysts and testers as one occupation.
The OEWS wage distribution for May 2025:
| Percentile | Annual wage | Hourly wage |
|---|---|---|
| 10 | $61,440 | $29.54 |
| 25 | $80,310 | $38.61 |
| 50 (median) | $104,300 | $50.14 |
| 75 | $133,180 | $64.03 |
| 90 | $167,010 | $80.29 |
BLS turns hourly wages into annual ones by multiplying by 2,080 hours, which is 52 weeks of 40 hours. Pay also depends on the industry: among the industries the Occupational Outlook Handbook lists for this occupation, the median ran from $99,960 in computer systems design and related services to $129,930 in manufacturing. For comparison, the same handbook puts the median for software developers at $135,980 (May 2025).
From QA engineer salary to the full cost of a hire
An employer spends more than the salary. The BLS Employer Costs for Employee Compensation (ECEC) release for June 2026, published September 9, 2026 and the latest as of October 2026, splits that spending into wages and benefits per hour worked:
- Private industry, all workers: $46.89 per hour worked. Wages and salaries were 70.0 percent of it, benefits 30.0 percent.
- Private industry, workers employed full time (the closer match for a QA hire): $54.00 per hour worked. Wages and salaries were 68.5 percent, benefits 31.5 percent.
ECEC sorts benefits into five groups. For private industry workers employed full time, each group’s share of the employer’s total cost was:
- Paid leave (vacation, holiday, sick and personal leave): 8.1 percent
- Supplemental pay (overtime, shift differentials and nonproduction bonuses): 4.3 percent
- Insurance (life, health and disability): 8.5 percent
- Retirement and savings: 3.6 percent
- Legally required benefits (Social Security, Medicare, unemployment insurance and workers’ compensation): 7.0 percent
Why paid leave changes the math
ECEC counts paid leave as a benefit, but a salary already pays for vacation days and holidays. So a salary stands for wages plus paid leave: 68.5 + 8.1 = 76.6 percent of what the employer spends. Divide the salary by that share:
| Step | Figure | Source or arithmetic |
|---|---|---|
| Median annual wage, QA analysts and testers | $104,300 | BLS OEWS, May 2025 |
| Wages and salaries, share of employer cost | 68.5% | BLS ECEC, private industry, full time, June 2026 |
| Paid leave, share of employer cost | 8.1% | BLS ECEC, same group, June 2026 |
| Share of the cost a salary covers | 76.6% | 68.5% plus 8.1% |
| Estimated yearly cost to the employer | $136,162 | $104,300 / 0.766 |
| Cost on top of the salary | $31,862 | $136,162 minus $104,300 |
| Estimated monthly cost | $11,347 | $136,162 / 12 |
Dividing by the wage share alone (68.5 percent) gives $152,263, which counts the vacation pay twice. Across the wage range, the same 76.6 percent turns $61,440 a year (the lowest 10 percent earned less) into about $80,200, and $167,010 (the highest 10 percent earned more) into about $218,000.
Treat the result as an estimate, not a statistic. The shares are averages for all private industry workers employed full time, not for QA engineers, and your real costs depend on your health plan, your retirement match and your state’s payroll taxes. When you know your own shares, swap them in:
// Yearly cost of a salaried hire. Default shares: BLS ECEC, June 2026,
// private industry workers employed full time.
function yearlyCost(
salary: number,
wagesShare = 0.685, // wages and salaries, 68.5% of employer cost
paidLeaveShare = 0.081, // paid leave, 8.1%: the salary already pays for it
): number {
return Math.round(salary / (wagesShare + paidLeaveShare));
}
console.log(yearlyCost(104_300)); // 136162The cost of hiring a QA engineer: time and effort
SHRM’s 2025 benchmarking survey (2,371 responding members, from US organizations across industries) gives two medians. Both cover all kinds of roles, not QA in particular:
- Time to fill: about a month and a half, for executive and nonexecutive positions alike. SHRM counts calendar days from the day the job requisition opens to the day the candidate accepts the offer.
- Cost per hire: $1,200 for nonexecutive roles. SHRM’s definition adds up costs such as third-party agency fees, advertising, job boards, employee referral costs, travel, relocation, recruiter pay and recruiting software, divided by the number of hires. It does not list the hours your own engineers spend interviewing.
Neither number covers what comes after the accepted offer: the notice period at the candidate’s current job, and the time a new QA engineer needs to learn your product. The steps, and who on your side spends time on each:
- Define the role (founder or engineering lead). Exploratory and manual testing, test automation, or both, and for which platforms: web, API, iOS, Android.
- Write and post the job (hiring manager, or a recruiter you pay). Name the stack, for example Playwright and TypeScript, so candidates can judge the fit.
- Screen applications and hold short calls (hiring manager).
- Test the actual skill (an engineer). Give candidates a feature and ask what they would test first and why. Ask for a bug report on a bug you planted. For automation roles, ask for one small test in your stack.
- Interview with the team (an engineer and whoever owns the product).
- Offer, references and the notice period (founder).
- Onboard (an engineer). Accounts, environments, test data and the product itself, then the first tests in CI and the first release call.
Write down the hours each person spent on your last engineering hire. That is the part of the hiring cost no survey can give you.
Software testing costs that are real but hard to put a number on
These depend on your product and your stack more than on the salary, so we describe them instead of guessing.
Tools and devices
Seats in a bug tracker and a test management tool, test inboxes and phone numbers for sign-up and sign-in flows, and sandbox accounts with third-party services such as your payment provider. For mobile apps, a shelf of real devices or a device cloud subscription. When you compare device clouds, ask how they bill (per user, per parallel session or per minute), because the number of parallel sessions also caps how fast your suite runs.
CI minutes
Tests use compute every time they run. As of October 2026, GitHub includes a monthly quota of Actions minutes for private repositories that depends on the plan: 2,000 on GitHub Free, 3,000 on GitHub Team and 50,000 on GitHub Enterprise Cloud. Beyond the quota, a standard Linux runner with 2 cores costs $0.006 a minute and a macOS runner with 3 or 4 cores costs $0.062 a minute, about ten times as much, which matters if your mobile tests run on hosted macOS runners. Actions usage is free on runners you host yourself (you pay for the machines instead) and for public repositories on standard runners. This cost is yours whoever writes the tests, with us included: the tests run in your CI.
Management time
A QA engineer needs priorities, reviews and regular time with a manager, like any engineer. A first QA hire also has no QA peer: nobody reviews their test design, and you have to define what growth in the role looks like.
Coverage gaps: vacations, sick days and departures
Paid leave is inside the estimate above. The gap it leaves is not. When your only QA engineer is on vacation or sick, releases wait or ship without them. If they leave, the hiring clock starts again, and whatever lived only in their head or in a tool only they used leaves too. Keep tests and test plans in your repository from the first day, whoever writes them.
QA outsourcing cost: what drives the price of each alternative
How much does QA cost if you do not hire? It depends on what you buy: hours, a fixed scope, test cycles or a managed service. We found no primary source for market rates, so we quote none here. Ask each provider for a written quote against the same written scope.
| Option | You pay for | What moves the price |
|---|---|---|
| QA engineer on staff | Salary, benefits, hiring | Wage level, benefits plan, hiring time |
| Hourly agency | Hours worked | Rate, hours, monthly minimum |
| Fixed retainer | A defined scope each month | Scope, platforms, release pace |
| Crowdtesting | Test cycles or results | Cycles, devices, testers per cycle |
| Managed QA with AI agents | Varies by provider | Scope, platforms |
Hourly agencies
You buy hours from a firm or a contractor, so the bill is a rate times the hours the work takes. Ask for the minimum hours a month, whether time spent learning your product is billed, how many hours overlap with your working day, and whether the tests they write live in your repository.
Fixed retainers
You pay a fixed monthly fee for a defined scope: a number of hours, test cycles or releases. Ask what happens when you release more often than the scope assumes, how a change of scope is priced, and what the minimum term and the notice period are.
Crowdtesting
A crowdtesting platform hands your build to many testers who test on their own devices, which fits wide device coverage and an exploratory pass before a launch. Ask how the quote changes with test cycles, devices, countries, testers per cycle and turnaround; whether you pay per cycle, per tester or per accepted bug; who checks each bug before it reaches you; and whether anything persists between cycles, such as automated tests in your repository.
Managed QA with AI agents
A provider runs the QA function for you: the test plan, the automated tests, their maintenance and the release reports, with AI agents doing much of the test work. Ask how the price is set (by hours, tests, flows or runs), who reviews what the agents write before it is merged, where the tests live and who owns them, and what is billed separately, such as AI usage, test runs and devices. Ours is one flat monthly price for up to a set number of user flows, and runs are never billed: see the pricing page.
How to compare a quote with a hire
Copy this template and fill in one block per option, so every price covers the same scope:
## <option>: QA for <product>, per month
Scope: <n> user flows on <web, API, iOS, Android>, <n> releases a month
- Monthly price: <amount> (for a hire: estimated yearly cost / 12)
- Billed separately: <tools, device cloud, CI minutes, AI usage>
- Hours from our team: <onboarding, questions, reviews, management>
- Who looks at a failure before it becomes a bug report: <name or role>
- Who covers a vacation or a sick day: <answer>
- Who owns the tests if we stop, and where they live: <answer>
- Minimum term and notice period: <answer>Three rules keep the comparison honest:
- Use the same scope for every option: the same flows, platforms and release pace. Rank the flows first; our risk-based testing guide shows how.
- Count your own team’s hours in every option, the hire included.
- Compare what you keep if you stop. Tests in your repository survive a cancelled contract or a resignation.
If you are still deciding whether you need dedicated QA at all, our QA checklist for startups lists the signs, stage by stage.
How we do it
We run the managed option. Claude agents, built with the Claude Agent SDK, plan, write, run and maintain your tests as plain Playwright and TypeScript code (web and API) or Appium, Maestro or Mobilewright code (mobile) in your repository, and the tests run in your CI on every pull request. A human QA engineer reviews every change before it is merged, looks at every failure before it becomes a bug report or a test fix, and signs a Go or No-Go call before each release; shipping stays your decision. We work in your team’s chat, in your time zone, with a weekly digest. Billing is month-to-month, and you keep every test if you stop. How it works shows what a normal week looks like.
Sources
- Software Developers, Quality Assurance Analysts, and Testers, Occupational Outlook Handbook, U.S. Bureau of Labor Statistics
- OEWS profile: Software Quality Assurance Analysts and Testers, May 2025, U.S. Bureau of Labor Statistics
- Employer Costs for Employee Compensation, June 2026, U.S. Bureau of Labor Statistics
- ECEC Table 5: private industry workers by bargaining and work status, U.S. Bureau of Labor Statistics
- ECEC Technical Note, U.S. Bureau of Labor Statistics
- 2025 Recruiting Executives Benchmarking: Insights to Maximize Recruitment, SHRM
- Actions runner pricing, GitHub Docs
- GitHub Actions billing, GitHub Docs
Researched and drafted with Claude, Anthropic's AI model, and checked against the sources it links. Spotted an error? Tell us and we will correct it.