QA & Game Tester Jobs: The Honest Career Guide

QA has been the traditional way into game development for decades. That is changing, and anyone giving career advice about it now has an obligation to say so. Here’s what the role involves, what the market actually looks like, what the AI question really amounts to, and where the jobs that survive are going.

What QA Actually Is in the Games Industry

QA stands for Quality Assurance. Games are complex software running across an enormous range of hardware configurations, played by people who will try things nobody anticipated. The result is an inexhaustible supply of ways for things to go wrong.

QA testers are the people who find those problems first. They work methodically rather than casually, replaying segments, attempting deliberately unreasonable actions, and documenting what breaks in enough detail that someone else can reproduce and fix it. The work covers technical function, performance, usability, progression, and sometimes security. They are the last line of defence before a game reaches players.

It’s a role with significant responsibility and a long history of being undervalued, which is worth naming plainly rather than dressing up.

The Market Reality

The original version of this guide (published back in 2021), like most QA career advice, described the role as a welcoming entry point into the industry. That was true for a long time. It requires serious qualification now.

QA accounts for roughly 5% of game development professionals, according to our own Gamedev Salary Pulse, making it one of the smaller disciplines. It also carries the lowest salaries of any department we survey, with senior QA medians running around €19,000 in Central and Eastern Europe and €30,500 in Western Europe, well below comparable seniority in engineering, art, or design.

The wider layoff cycle has hit entry-level roles disproportionately. Documentation of the industry’s recent layoffs notes that they affected junior staff in greater numbers than other skill levels, and that in some cases juniors were specifically targeted. QA is the classic junior entry point, which means it sits directly in that firing line.

None of this makes QA a bad career. It makes it a career that now requires a deliberate strategy rather than being the obvious default route in.

What Automation Can’t Do Yet

Worth being specific, because this is where the surviving roles are.

Automated tests are good at repetition, consistency, and scale. They will run the same regression suite across twenty hardware configurations overnight without fatigue, catch a crash on launch, and verify that yesterday’s fix didn’t break something else. That work is genuinely well suited to automation and it was always the least rewarding part of the job.

What automation handles poorly is everything requiring judgment about experience. Whether a control scheme feels responsive. Whether a difficulty spike is frustrating or satisfying. Whether a tutorial is confusing in a way players won’t articulate. Whether a bug is technically minor but ruinous to immersion. Testing as a player rather than as a script is not a solved problem, and describing a problem well enough that a developer can act on it remains a human skill.

The criticism levelled at the Square Enix announcement by others in the industry focused precisely here: that QA workers provide insight machines don’t, and that the role serves as a crucial entry point into the industry that automating it away would close. Both points are worth taking seriously, and both are arguments about what gets lost rather than claims that automation won’t happen.

The QA Role Family

QA is more differentiated than outsiders assume, and the distinction between the manual and technical branches has become the most consequential thing about the discipline.

Read that table as a gradient rather than a list. The further a role sits from executing predefined test cases and the closer it sits to designing what should be tested or building the systems that do the testing, the more durable it is.

What the Work Actually Involves

For anyone considering the role, the daily reality is worth stating without romance.

You’ll study the game’s design and requirements so you know what correct behaviour looks like. You’ll replay specific segments repeatedly, systematically rather than for enjoyment. You’ll try to break things deliberately, including in ways no reasonable player would attempt. You’ll test across every platform the game targets. You’ll check text for typos and errors, including in supporting documents. You’ll file bug reports through tracking software in enough detail that someone can reproduce the issue without asking you. You’ll retest after fixes to confirm they worked and didn’t break something adjacent.

And you’ll tell people their work has problems, repeatedly, which requires more diplomacy than the job description suggests. Nobody enjoys hearing that what they built is broken. How you deliver that determines whether people engage with your reports or dread them.

Is QA Still a Good Way Into the Industry?

It can be, with conditions attached that didn’t previously apply.

What still holds. QA gives you a detailed understanding of how a game actually works, how a studio actually operates, and who does what. That knowledge is genuinely valuable and it’s why QA has historically produced so many designers, producers, and technical artists. Moving internally from QA remains considerably easier than being hired externally into those roles.

What has changed. The number of manual QA positions is contracting, competition for them is high, pay is the lowest in the industry, and the routine end of the work is the part being automated first. Entering QA with no plan beyond “get in and see what happens” is a weaker strategy than it was.

The conditional version of the advice. QA is a good route in if you treat it as a two-to-three year transition rather than a destination, and if you build technical skills from the start. Testers who learn Python, pick up a test automation framework, and can script their own tools are hired from a much smaller candidate pool, are paid better, and are moving toward the part of the discipline that’s growing rather than shrinking.

How to Future-Proof a QA Career

Concrete and in rough order of return.

Learn to script. Python first, because it’s the most common automation language and the most transferable. This single step separates you from most of the candidate pool.

Learn an engine’s testing framework. Unity Test Framework or Unreal’s automation and Gauntlet systems. Studios hire for engine-specific familiarity, and it demonstrates you understand testing inside a game rather than testing in the abstract.

Understand CI/CD pipelines. Automated tests are only valuable when they run automatically on every build. Knowing how that plumbing works moves you from writing tests to owning the testing system.

Get good at exploratory testing. The part machines handle worst. Structured exploration, intuition about where bugs hide, and the ability to articulate a subtle experiential problem are durable skills and worth developing deliberately rather than treating as innate.

Write excellent bug reports. Underrated as a differentiator. A report that a developer can act on without a follow-up conversation saves real time, and leads notice who produces them.

Learn to work alongside automation rather than against it. Studios increasingly want testers who can triage automated results, identify false positives, and decide what needs human attention. That’s a genuine skill and it’s currently in short supply.

---

QA & Game Tester Jobs – Common Questions

Is AI replacing game QA testers?

Partly, and the intent is documented rather than speculative. Square Enix stated in its progress report on its medium-term business plan a goal of automating 70% of QA and debugging tasks by the end of 2027, working with the Matsuo-Iwasawa Laboratory at the University of Tokyo. That said, documentation of the recent layoff wave notes there’s no clear indication layoffs have been driven directly by AI adoption; most trace to overexpansion, costs, and consolidation. The realistic picture is that automation is displacing routine regression and compatibility testing faster than exploratory testing, changing what QA means rather than ending it.

Is QA still a good way to get into the games industry?

It can be, with conditions that didn’t previously apply. QA still gives you unmatched understanding of how a game and a studio actually work, and moving internally from QA into design, production, or technical art remains far easier than being hired externally. But manual QA positions are contracting, competition is high, and pay is the lowest of any discipline. Treat it as a two-to-three year transition rather than a destination, and build scripting skills from the start.

Which QA roles are safest from automation?

Think of it as a gradient. The further a role sits from executing predefined test cases, the more durable it is. QA automation engineers and test engineers are currently in strongest demand, since they build the systems doing the automating. QA leads and directors are insulated by the people and planning components. Senior testers are safer than juniors because the work involves deciding what to test rather than working through a list. Manual regression and compatibility testing is the most exposed.

What can automated testing not do?

Anything requiring judgment about experience. Whether a control scheme feels responsive, whether a difficulty spike is frustrating or satisfying, whether a tutorial confuses people in ways they can’t articulate, whether a technically minor bug ruins immersion. Automation excels at repetition, consistency, and scale: running regression suites across many hardware configurations overnight without fatigue. Testing as a player rather than as a script is not a solved problem.

What skills should a QA tester learn to stay employable?

Python first, as the most common and transferable automation language. Then an engine’s testing framework, such as Unity Test Framework or Unreal’s automation and Gauntlet systems. Then CI/CD pipeline understanding, since automated tests only matter if they run on every build. Alongside that, get deliberately good at exploratory testing and at writing bug reports a developer can act on without a follow-up conversation. And learn to triage automated results, which is a genuine skill currently in short supply.

How much do game QA testers earn?

Less than any other discipline in games. According to our Gamedev Salary Pulse, senior QA medians run around €19,000 in Central and Eastern Europe and €30,500 in Western Europe, well below comparable seniority in engineering, art, or design. Automation and test engineering roles pay considerably better than manual testing, which is another reason the technical branch is worth moving toward.

What does a QA tester actually do day to day?

Study the game’s design so you know what correct behaviour looks like. Replay segments systematically rather than for enjoyment. Deliberately try to break things, including in ways no reasonable player would. Test across every target platform. Check text for errors. File bug reports detailed enough to reproduce without a conversation. Retest after fixes. And tell people their work has problems, repeatedly and diplomatically, which is harder than the job description suggests.

Are layoffs in games caused by AI?

Not primarily, on the available evidence. Documentation of the layoff wave states that while AI is a concern for many developers, there’s no indication layoffs have been driven directly by its adoption. The main causes are post-pandemic overexpansion, rising development costs, consolidation after major acquisitions, and cancelled projects. AI is arriving into an already-contracting market, which makes it genuinely difficult to separate cause from coincidence. Junior roles have been affected disproportionately, and QA is the classic junior entry point.