Last updated: October 25, 2026
By Devin Hornick, Co-Founder and Partner, KORE1
As of October 16, 2026, a mid-level contract QA tester or test engineer bills $73 to $94 an hour nationally, median $83, about $43,000 for a three-month release cycle. Junior testers bill $57 to $72 and senior test engineers $94 to $114 (KORE1 Contract Rate Index 2026-Q4, modeled from BLS OEWS May 2025). Every cell on this page is modeled. We have too few recent QA placements to print an observed rate, and I’d rather say that up front than dress it up.
Picture the quarter. A billing platform goes live on a date the CEO already gave the board. The regression suite has grown from 400 cases to 1,100, and the one engineer who understood the Selenium framework took another job in August, leaving a TestRail plan that three people claim to understand and none can fully explain. Nobody planned for any of it. Sound familiar?
The budget line for the replacement came off a salary site. That’s a pay number. Your invoice carries a different one, and the distance between the two is what this page is for.
I’m Devin Hornick, a partner at KORE1, and the question I hear most on contract staffing calls is some version of “what does a tester cost per hour?” Our QA engineer staffing team fills these seats, so yes, we’d like the call. Read the tables first anyway. When you’re ready to price an actual seat, ask for a QA bill rate quote.
How Much Does a Contract QA Tester or Test Engineer Cost per Hour in 2026?
Between $57 and $114 an hour at the national level, depending on level, with the mid-level median sitting at $83. A bill rate is the hourly price on a staffing firm’s invoice for a W2 contractor. Wages, payroll taxes, insurance, paid sick leave, benefits the firm pays for, weekly payroll and the recruiting behind the placement all live inside that one number, which is why a bill rate always looks high next to the hourly wage you’d be tempted to compare it with. Costs below assume 40 hours a week. Thirteen weeks is a quarter, 26 is half a year. Simple math.
| Level (United States) | Bill rate range | Median | 3-month cost | 6-month cost |
|---|---|---|---|---|
| Junior | $57 to $72 | $62 | $32,500 | $65,000 |
| Mid-level | $73 to $94 | $83 | $43,000 | $86,000 |
| Senior | $94 to $114 | $106 | $54,900 | $109,900 |
Pricing a specific seat? Get a bill rate quote for a contract QA tester or test engineer. Tell us the role, the level, the metro, the start date and how long you need them. You get a range back before you see a single resume.
What Do QA Contractors Bill at Junior, Mid and Senior Level?
$62, $83 and $106 at the national median. Each step up adds $21 to $23 an hour, which sounds modest until you multiply it by a 13-week schedule and then by the three or four people a release crunch usually needs. Junior to mid is $10,500 over three months. Mid to senior is another $11,900. Put a senior where a junior would have done the job and six months costs you $44,900 more. That’s real money.
Levels aren’t titles. They describe what a person can finish without somebody senior looking over their shoulder. This sorting is my judgment, not something the index measures.
- A junior runs the cases somebody else wrote. Clean repro steps in Jira, retests after the fix, a TestRail plan worked top to bottom. Quick to onboard, and happiest with a lead nearby.
- Mid-level means writing the cases. Owning a feature area from spec to sign-off, fixing flaky checks inside a framework that already exists, and telling you by Thursday whether Friday’s release candidate is safe.
- Senior? Strategy. Choosing the framework, or rescuing a bad one, wiring Playwright, Cypress or Selenium suites into a Jenkins or GitHub Actions pipeline, and coaching the juniors. Sometimes the whole test function is one person.
Most requisitions that say senior don’t need one. A mid-level tester inside a team that already has a test lead and a working framework is the right buy. The same tester dropped into a team with no lead and no framework is not, and I’d rather tell you that before the purchase order than after the second missed release.
Where do the numbers come from? Each cell starts with the federal wage for Software Quality Assurance Analysts and Testers, SOC 15-1253, at the 25th percentile for junior, the median for mid and the 75th percentile for senior. Those wages are in the May 2025 wage estimates from the Bureau of Labor Statistics, released May 15, 2026. Add 24% employer burden. Then apply the bill-to-cost band our own placements show at that cost level. Three steps.
Here’s the part I won’t blur. No KORE1 QA cell reaches five placements with 2023 to 2026 starts, which is our floor for printing an observed rate. Fewer than five. So the national table above, and every table below it, is modeled.
How Much Do QA Tester Bill Rates Change by Metro?
A mid-level seat runs from an $82 median in Dallas-Fort Worth and Austin to $107 in the San Francisco Bay Area, which is $12,900 apart over one quarter.
| Metro (mid-level) | Bill rate range | Median | 3-month cost | 6-month cost |
|---|---|---|---|---|
| United States (national) | $73 to $94 | $83 | $43,000 | $86,000 |
| Dallas-Fort Worth, TX (incl. Plano, Irving, Frisco) | $73 to $92 | $82 | $42,600 | $85,100 |
| Austin, TX | $74 to $93 | $82 | $42,500 | $85,000 |
| Orange County, CA | $82 to $108 | $97 | $50,400 | $100,800 |
| Los Angeles, CA | $82 to $108 | $97 | $50,400 | $100,800 |
| Seattle, WA | $90 to $118 | $103 | $53,500 | $107,000 |
| New York, NY | $91 to $115 | $104 | $53,800 | $107,700 |
| San Francisco Bay Area, CA | $92 to $120 | $107 | $55,500 | $111,100 |
| San Francisco Bay Area, CA (senior) | $116 to $139 | $128 | $66,700 | $133,400 |
Texas buyers sometimes expect a bargain, and they get a small one. Dallas-Fort Worth, including Plano, Irving and Frisco, and Austin both land at $82, a dollar under national. Houston? $78. That’s about it for cheap. Houston’s other IT seats are priced in Houston contractor rates for IT roles.
California is a different animal. Federal wage data folds Orange County and Los Angeles into a single metro, Los Angeles-Long Beach-Anaheim, so a mid-level tester in Irvine and one in Burbank price the same at $97. The Bay Area runs $107. A senior there is $128, or $66,700 for a quarter. Seattle is $103. New York is $104. If your company is headquartered in San Jose but the test team sits in Frisco, price the seat where the person actually works, because the metro wage data follows the desk and not the corporate address on your letterhead. We break out the other roles on our Orange County IT contractor rates, Bay Area IT contractor rates and Seattle IT contractor rates pages, and all 22 index metros sit side by side on IT contractor rates by city.
Want every role and every metro in one file? The 2026 Contract Rate Card is a free download built from the same index cells as these tables.
What Does a 3-Month or 6-Month QA Tester Contract Cost?
One mid-level tester is $43,000 for three months and $86,000 for six at the national median. Those two numbers answer the question managers ask first. The second question is what the team costs. Different math.
Take a release-hardening crew. Two mid-level testers run regression and exploratory passes while one senior test engineer repairs the flaky Cypress suite and gates the pipeline so that nothing red reaches the release branch on a Friday afternoon. At national medians that’s $140,900 for 13 weeks and $281,900 for 26. In Dallas-Fort Worth the same three people cost $137,800 a quarter. Move them to the Bay Area and it’s $177,700, $36,800 more for an identical release.
Shorter work? Hours times rate. A two-week regression push, one mid-level tester at 80 hours, is about $6,600 nationally. A four-week hardening sprint at 160 hours is about $13,300. Not every QA need is a quarter long.
What Is Inside a Contract QA Bill Rate?
I use a round number on calls, on purpose, and it has nothing to do with QA wages. Round numbers show the layers better than realistic ones do. $100 an hour pay plus a 24% burden is $124 loaded; the bill rate on that pay would likely be around $150 to $160.
That 24% isn’t a fee. It’s what it costs an employer to have a W2 person on payroll at all. In 2026 the employer pays 6.2% Social Security on wages up to $184,500 and 1.45% Medicare on every dollar, per IRS Publication 15. Add federal and state unemployment taxes, workers’ compensation, liability coverage and, in California, mandatory paid sick leave of at least 40 hours or five days a year, which a contractor accrues even on a short assignment. Then payroll runs every Friday whether or not your accounts payable team has paid last month’s invoice. Somebody finances that float. It lives in the rate.
Burden rides along at every level. A $62 junior tester carries the same 24% as a $106 senior.
So when a firm hands you a percentage instead of an hourly number, ask what it is a percentage of. Pay alone? Or pay plus burden? In my example the burden is $24 an hour before anyone has earned a dollar of margin, and a quote that leaves those dollars out of the markup makes the proposal look smaller than the invoice turns out to be. Compare all-in hourly bill rates instead, line by line, which is how every figure on this page is built. The full line items are in how a KORE1 bill rate breaks down, and if you’re holding several quotes, how to compare staffing agency quotes walks through it. A 1099 or corp-to-corp tester priced well under these bands? Read W2 vs C2C vs 1099 first, because the payroll tax doesn’t vanish. It moves to whoever gets audited.
Why Is the Range Between Manual Testers and Automation Engineers So Wide?
Because QA is two jobs sharing one title, and the index can’t separate them. BLS files manual testers and automation engineers under a single occupation, SOC 15-1253 (see the BLS profile for software developers, QA analysts and testers), so the wage data under every cell blends the two. I won’t invent a manual median or an automation median to fill the gap. What the index does show is the spread across levels, from $57 at the junior 25th percentile to $114 at the senior 75th. Double.
Level and framework depth drive that width. This is my read after a lot of requisitions, and it is not a measurement. A tester who executes scripted regression in TestRail and logs defects in Jira sits at the low end of a band. An engineer who builds and owns the Playwright or Selenium framework, writes API checks in Postman, and keeps the Jenkins job green sits at the high end. Mobile automation in Appium is a narrower pool, and in my experience quotes land toward the top of its band.
So when two quotes for “a QA contractor” differ by $30 an hour, check first whether they’re pricing the same job. One may be a manual regression seat. The other may be an SDET wearing a tester’s title. Ask which framework. Ask what the person will own at the end of week four. If you are weighing a permanent hire for the same work, our QA engineer salary guide and hiring a QA engineer pages cover the pay side.
When Does Contract QA Around a Release Make Sense, and How Long Does It Run?
When the work has an end date and the skill isn’t already in the building. That is the whole test. Three shapes keep showing up.
- A release with a date nobody can move, and a regression pass that won’t fit inside the team’s capacity.
- A migration, an ERP cutover or a move to a new cloud platform, where every integration needs retesting and the people who know the old system are busy running it.
- A backlog. Eight months of untested hotfixes, say.
Contracts run longer than the purchase order says. Across every role KORE1 places, the median assignment is 116 days over 1,887 ended assignments, about 17 weeks. For a mid-level tester at the national median, 17 weeks is roughly $55,000, not $43,000, and that $12,000 gap is the surprise to plan for. Write the extension into the budget as its own line. Unused? Give it back.
And when the answer is no? If the same testers will be needed in 18 months doing the same job, you don’t have a project. You have headcount. Hire. A middle path is contract-to-hire staffing, since after 1,040 hours on assignment a KORE1 contractor can join your payroll and we charge nothing for the conversion.
Starting is fast. The median is three days from a yes to a first shift, measured over 1,997 contract starts, and the slow part is access. Request the Jira and TestRail licenses, the test-environment credentials, the VPN and the device-lab login before the contractor’s first morning. More on timing in how fast a contractor can start. Teams that want testers embedded for a release instead of a standing vendor can read about QA staff augmentation.
How Does KORE1’s Own Placement Data Compare With the Modeled QA Rates?
| Cell | Source | Placements (n) | Bill rate range | Median | 3-month / 6-month |
|---|---|---|---|---|---|
| QA tester, all levels, KORE1 placements (primarily Southern California) | KORE1 observed | Fewer than 5 | Not published | Not published | Not published |
| Mid-level, Orange County, CA | Modeled | Not applicable | $82 to $108 | $97 | $50,400 / $100,800 |
| Mid-level, Dallas-Fort Worth, TX | Modeled | Not applicable | $73 to $92 | $82 | $42,600 / $85,100 |
| Mid-level, United States (national) | Modeled | Not applicable | $73 to $94 | $83 | $43,000 / $86,000 |
Not yet. The observed row is empty. That’s the honest answer. The index prints a KORE1-observed cell only at five or more placements with 2023 to 2026 starts, with anomalies and payroll-only deals filtered out, and QA hasn’t cleared the bar. Most of the placements we do have are in Southern California, so even a future observed cell would lean toward Orange County and Los Angeles pricing, not the national figure.
Robert Ardell at KORE1 put the design in one sentence on our October 16 call. “Scrape the web for generic stuff too… and then we use our own personal data from our contractors to complement that.” Public wage data comes first. Our placements are the check. For QA the check is thin. Very thin. That is why I’m calling these figures the middle of the market and not a promise. When a QA cell reaches five placements it will print beside the modeled one, and the next chance is the January 2027 refresh. The method, exclusions included, is in how the KORE1 Contract Rate Index is built.
What Engineering Managers Ask Before Adding Testers
Mid-level QA test engineer, what’s the national hourly number?
$73 to $94 an hour, median $83, so about $43,000 for a three-month, 40-hour-a-week contract and $86,000 for six (KORE1 Contract Rate Index 2026-Q4, modeled).
The cell starts from BLS OEWS May 2025 wages for SOC 15-1253, adds a 24% employer burden, then applies KORE1’s observed bill bands.
What would a junior tester run me?
Short answer: $57 to $72 an hour, median $62, which comes to about $32,500 for three months and $65,000 for six at 40 hours a week (KORE1 Contract Rate Index 2026-Q4).
Junior fits scripted regression with a lead close by. If nobody senior is in the building, budget for mid-level.
Senior test engineer, is $106 an hour real?
Senior test engineers bill $94 to $114 an hour nationally, median $106, about $54,900 for a three-month contract and $109,900 for six (KORE1 Contract Rate Index 2026-Q4, modeled).
That price buys framework ownership and pipeline work, not extra test execution. If the job is mostly running cases, a mid-level tester is the better buy.
Why does a Bay Area tester cost $24 an hour more than the national number?
A mid-level QA tester in the San Francisco Bay Area bills $92 to $120 an hour, median $107, about $55,500 for three months and $111,100 for six, because metro wages in the BLS data run higher.
A senior test engineer there bills $116 to $139, median $128, or about $66,700 a quarter.
Before You Open the Requisition
Pick the level by what the person has to finish alone. Take the bill rate for that level in the metro where they will sit, $83 for a national mid-level tester, and multiply by the hours. Then budget 17 weeks, not 13, because that is how long our contracts actually run. A mid-level tester on that plan costs about $55,000. If the release ships on time and the contract ends at three months, you’re $12,000 under budget, which nobody has ever been fired for, and the finance team remembers you as the manager who gave money back instead of asking for more. Easy call.
KORE1 has been doing contract staffing for IT teams since 2005, and the Contract Rate Index refreshes quarterly, next in January 2027. To run your own seat counts and weeks, open the contract staffing cost calculator and pick QA. For rates across every technical role, there’s tech contractor hourly rates for 2026. And when you want a real number for your city and start date, talk to a KORE1 recruiter. If a part-time freelancer on your own team can cover the gap, we’ll tell you that too.
