Published answers to this question vary widely, mostly because they rarely distinguish between three genuinely different kinds of pay: a salaried studio QA job, freelance or contract QA work, and per-session pay from a playtesting panel. A single headline number can't represent all three honestly, so we’ve split the range down by category.

Salary range by work type

Studio and in-house QA testing. The U.S. Bureau of Labor Statistics groups this under "Software Developers, Quality Assurance Analysts, and Testers," a broad category that includes QA roles well beyond games specifically. As of its most recent update, the median is $104,300 per year. That figure covers software QA broadly, not a game-tester-specific line item, so treat it as a ceiling-side reference for the profession QA testing sits inside, not a games-specific number.

Two sources that do report game-tester-specific figures: PayScale puts the average game tester hourly rate at $20.00, with a typical range of $13.25 to $35.10 per hour, based on a sample of 37 salary profiles. Indeed reports an average of $17.98 per hour for game testers in the US, with a range of $9.05 to $35.74, based on 67 recent salaries pulled from job postings. Both are narrower, entry-to-mid-level figures than the broad BLS number, which fits: "game tester" as a job title skews more junior than "software QA analyst" as a category.

Freelance and contract QA work. Rates here vary by platform and by the tester's own experience level far more than salaried roles do, and publicly available figures are thin and inconsistent enough that we're not going to repeat an unverified number here. If you're quoted a specific contract rate, treat it as specific to that listing, not a market standard.

Per-session playtesting panel pay. This is the category paid playtesting panels sit in, and it works differently from an hourly or salaried rate: you're paid per session, not per hour worked. A few platforms publish their own figures directly: PlaytestCloud pays $5 to $9 USD for a 15-minute playtest and survey. BetaTesting.com states a typical incentive of $15 to $30 for a 45-to-60-minute test. Userlytics states a range of $10 to $50 per study. These are general figures from the category, not a specific quote for any one platform's every session, since pay varies by session length and what's being asked of you.

What affects pay

Experience. Matters more for salaried and contract QA work than for panel sessions, where pay is typically set by the session itself rather than negotiated per tester.

Platform and specialization. Console QA work, particularly anything requiring certified test labs or specific devkits, tends to sit at the higher end of salaried QA pay. Panel work doesn't vary by platform in the same way, since pay is tied to the session, not the device.

Session length and depth. For panel-based work specifically, this is the single biggest factor: a 15-minute playtest and a 60-minute structured study are different amounts of work, and the pay figures above reflect that spread directly.

How panel-based pay compares

Panel work isn't a replacement for a salaried job's income, and it isn't meant to be. It's closer in structure to other paid research participation: you're compensated per session for your time and your feedback, on your own schedule, without the ongoing commitment a job implies. Comparing a single session's pay to an hourly wage misses the actual trade-off, since there's no expectation of a set number of hours per week the way there is with employment.

Realistic first-month expectations

Expect pay to scale with how many sessions you're actually matched to and complete, not with a fixed weekly or monthly figure. Being new to a panel typically means fewer sessions at first, since matching and a track record both take a little time to build. Consistency, showing up for sessions you accept and giving specific, useful feedback, is what tends to increase how often you're matched going forward, more than anything you can control on day one.

Emhance's playtester application is open now if you want to see how this works firsthand.