Careers

Move From QA Testing Into Game Production Roles

Ryan Cole June 22, 2026 (Updated Jul 8, 2026) 2 min read · Fact-checked & reviewed

Move From QA Testing Into Game Production Roles

In this article

QA is the best job in the games industry for getting into production, and almost no one talks about why. They’re too busy warning you about the grind, the low pay, the repetitive test cases. All of that is true. It’s also beside the point.

Here’s what actually matters: QA is the only entry-level role where you see the entire development pipeline, every day, without anyone filtering it for you. You watch features break. You watch them get fixed wrong and break again. You see what happens when a milestone slips, when a build is untestable, when a lead makes a call that the team clearly disagrees with. That’s a graduate-level education in how games are actually made, and you’re getting paid for it (badly, but still).

The transition from QA to production isn’t a long shot. It’s a logical step. The problem is that most QA testers don’t build the case for it, and then they’re surprised when the AP role goes to someone from outside the studio.

What Production Actually Wants From You

Let’s be specific about what an associate producer or production coordinator does, because the job description on the posting and the reality on the floor are different things.

AP roles at mid-size studios in 2026 are mostly about information flow and friction reduction. You’re tracking tasks, running standups, chasing down blockers, updating schedules, writing clear summaries of messy conversations, and generally being the person who makes sure nothing falls through the cracks between disciplines. That’s it. The creative vision stuff comes later, if it comes at all.

Now look at what a sharp QA tester does all day: they document bugs with precision, they track issues across multiple builds, they communicate between disciplines when a bug’s cause is ambiguous, and they develop an instinct for which problems are actually urgent vs. which ones look scary but aren’t. That’s the same job, slightly rotated.

The gap isn’t skill. It’s positioning. Most QA testers don’t frame their existing work in production language, and they don’t put themselves in front of the right people.

Building the Case While You’re Still in QA

4096-level pressure-sensitive pen tablet with 4 ExpressKeys for concept art, UI mockups, and digital sketching.

Check Price →

Don’t wait for a production opening to start acting like a producer. That’s backwards. By the time the role posts, you want to already be known as the person who thinks in terms of schedule, scope, and team dependencies.

Start with your current work. Write better bug reports. Not just repro steps and screenshots, which is table stakes. Write a one-line summary at the top that explains the business impact: “This crash affects 100% of players who complete Chapter 3 before installing the Day 1 patch. Expected ship-blocker.” That kind of framing is what production people write. Do it consistently and leads will notice.

Volunteer for anything that touches coordination. Test lead coverage shifts, triaging incoming bugs for severity, running the morning sync when your lead is out. These aren’t glamorous tasks, but they’re visible and they’re exactly the work you’ll be doing as an AP. I’ve seen testers land AP roles almost entirely because they’d been unofficially running triage for six months and everyone already thought of them as a coordinator.

Pick up Jira or whatever your studio uses and actually learn it past the basics. Custom filters, bulk edits, dashboard setup, board configuration. Then offer to help production with board maintenance. You’ll learn how they think about tracking, and you’ll get face time with the people who’ll eventually hire you.

Read. Seriously. Heather Maxwell Chandler’s “The Game Production Handbook” is the clearest breakdown of what a game producer actually manages. Pair it with Mike Acton’s talks on data-driven design not because you need to become technical, but because understanding how engineers think will make you a better communicator between disciplines. If you want structured learning, the Renegade Game Studios production course and the Game Academy’s production track are both reasonable, though neither replaces actual floor time.

The Conversation You Need to Have

The Portfolio Problem (And How to Solve It)

Sources

Atahan Demir

Here’s the contrarian take: you don’t need personal projects to get your first AP role. Most of the advice you’ll read says otherwise. It’s oversold.

What you actually need is documented evidence of production thinking. A written postmortem of a release you worked on, even a personal one you keep private until an interview, shows you understand scope, risk, and process. A sample sprint plan you built for a hypothetical feature shows you know how to break work down. A one-page production plan for a jam game you made with two friends over a weekend shows initiative.

None of that requires shipping a full indie title. Shipping a full indie title is genuinely hard and takes years and will almost certainly delay your career transition, not accelerate it. Use that time to build the paper trail that proves you think like a producer.

For task tracking and planning practice, Notion and Linear are both worth knowing. Most studios use Jira and ShotGrid (especially on larger projects), but the logic transfers. Spending a weekend building out a fake project in Jira’s free tier teaches you more than reading about it.

Photo: Atahan Demir via Pexels

Note: This content reflects the author's personal experience and research. Game development outcomes vary widely; always do your own research before making production decisions.

Frequently Asked Questions

How long does it typically take to move from QA to production?

Anywhere from one year to four, honestly. The spread is wide because it depends almost entirely on how deliberately you pursue it. Testers who actively do the things above, document it, have the conversation, and apply externally if needed, tend to move in 18 to 24 months. Testers who wait for it to happen to them wait much longer.

Do I need a degree in game design or production management to make this switch?

No. I've hired AP candidates from QA backgrounds with no relevant degree and passed on candidates with production management degrees who couldn't demonstrate they understood how a real development team functions. Direct experience reads louder than credentials in this industry, especially at the associate level.

Should I apply for AP roles at studios I don't currently work at before trying internally?

Yes, and sooner than feels comfortable. Interviewing externally does two things: it tells you what the market actually values, and it gives you leverage (not the buzzword kind, the real kind) if you want to have a more direct conversation with your current employer. You don't have to take a competing offer to benefit from having one.

What's the hardest part of the QA-to-production transition that no one warns you about?

The shift from a reactive role to a proactive one. In QA, your job is to respond to what's in front of you. In production, your job is to anticipate what's coming and prevent problems before they arrive. That mental model switch is harder than it sounds, and it catches a lot of new APs off guard in their first three months. The testers who do best in production are the ones who've already been thinking that way in QA.

Is it worth taking a pay cut to get an AP title at a smaller studio?

Usually yes, if the alternative is staying in QA for another 18 months waiting for an internal slot. Title and role history compound. An AP at a 20-person studio for two years sets you up for a full producer role much faster than another two years of QA at a larger one. Run the two-year math, not the one-year math.

Ryan Cole Production Lead

Ryan Cole has spent a decade working in game production across mobile, PC, and console projects. He started as a junior producer at a mid-size studio and worked his way up by learning to ship on schedule without burning out his team. At GameDevProducer, he covers production frameworks, milestone planning, and the practical side of getting a game from concept to launch.

🎧

Listen to industry books on Audible — free trial for new members

From Masters of Doom to The Art of Game Design — Audible has the game dev reading list, all in audio. Perfect for long playtests, commutes, and crunch.

Try Audible Free →

🎮

Half-Price Amazon Prime for Ages 18–24

Get Amazon Prime at the student rate — plus Prime Gaming unlocks free PC games and in-game loot every month.

Claim Half-Price Prime →