How to find game QA testing work
Game QA work comes from IndieGuild, Work With Indies, game QA outsourcing companies and publishers (on their careers pages and LinkedIn), testing communities like uTest, r/gameDevClassifieds and r/INAT, and indie devs who need a careful pair of eyes before a demo or launch. The good news: you can build a real portfolio of bug reports before anyone hires you.
I founded IndieGuild, so keep that in mind when I talk about it. I've tried to be fair to everyone here, because each of these is the right pick for somebody.
- Your bug reports are your portfolio. Clear steps, expected vs actual, the build and platform, and a video.
- Want a job? Game QA companies and publishers hire testers, and Work With Indies lists QA roles at indie studios.
- Want freelance clients? Help indie devs before a demo or launch, starting with a small paid test pass.
- Just starting? Test free demos and jam games, send your reports to the devs, and ask if you can show them.
- Want devs to find you? Put your reports, platforms and rates on a free IndieGuild profile.
| Where | Better pick when | Watch out for |
|---|---|---|
| IndieGuild | You want indie devs to find you by the platforms you test on and the reports you write. | It's new, so there are fewer roles than on the big boards. |
| QA companies and publishers | You want steady hours, a team and a clear process to learn from. | Entry roles can be strict about schedules and confidentiality. |
| Work With Indies | You want a QA role at an indie studio. | QA roles come up less often than art or code roles. |
| uTest | You want a testing community with paid projects and room to learn. | It covers all kinds of software, not just games. |
| You want a free [FOR HIRE] post on r/gameDevClassifieds, or a team on r/INAT. | Read each sub's rules, and check rev share teams carefully. | |
| Indie demos and playtests | You need real bug reports to show. | It's unpaid, so treat it as practice and portfolio. |
Where game QA work actually comes from
IndieGuild
This one's mine. You make a free profile with sample bug reports, test plans, test cases, compatibility reports and video repros right on it. You pick the platforms you test on, like PC, Steam Deck, Switch, Android or VR, add your rates and tags like "Rev share OK", and devs find you on Discover or with Find my match. When a dev posts a role that fits you, it lands in your inbox. Every role on the Job board shows the pay type up front, and some show a budget. It's free, and I don't take a cut.
Better pick when you want indie devs to come to you. Not the best pick if you want the biggest pool of jobs today, since it's newer than the big sites.
QA companies and publishers
A lot of game QA happens at outsourcing companies that test games for studios and publishers, and at publishers with their own QA teams. Their careers pages and LinkedIn are where tester roles go up, often called QA tester, game tester or functional tester. It's a classic first job in games, and you learn a real process: test plans, bug databases, regression passes and sometimes console certification.
Work With Indies
Work With Indies is a job board for indie studios. When I checked in October 2026, it had QA tester and QA specialist roles next to art and code. Studios pay to list, so these are real roles.
uTest
uTest is a big community for software testers, where you can learn, find paid projects and talk shop. It covers all kinds of software, not just games, but it's a good way to practice writing reports for people who read a lot of them.
r/gameDevClassifieds and r/INAT
r/gameDevClassifieds is for paid game work, so make a [FOR HIRE] post with the platforms you own, a link to a sample report and your rate. r/INAT is for rev share and hobby teams, and small teams there rarely have a tester. Read each sub's rules first.
Indie demos and playtests
This is the best practice there is. Steam festivals like Next Fest (February, June and October) put lots of free demos out at once, and devs run open playtests through Steam Playtest, itch.io and Discord. Play them properly, write clean reports, and send them where the dev asks for bug reports. Devs remember the person who sent a perfect repro. Ask before you post someone's bugs in your portfolio, and never share builds that aren't public.
What your portfolio should show
Devs and QA leads want to see that you find real bugs and explain them well. I'd show:
- Sample bug reports. A clear title, the build and platform, numbered steps, expected vs actual, how often it happens, severity, and a video.
- A test plan. What you'd test on a small game and in what order.
- Test cases or a regression checklist. Short, specific checks someone else could follow.
- Device coverage. The hardware you actually own: PCs, Steam Deck, consoles, phones, controllers.
- A compatibility or performance report. Like a demo on three different machines, with settings and frame rates.
- An accessibility review, using something like the Game Accessibility Guidelines as your checklist.
Learn the tools: Jira, Trello and GitHub Issues all come up, and a clean spreadsheet works for small teams. If you want more structure, ISTQB runs official software testing certifications. They cover software testing in general, not games, so think of them as a bonus.
From first report to steady work
Here's how I'd climb:
- Practice on public demos and jam games. Send your reports to the devs, and ask if you can show them.
- Learn one platform deeply. Steam Deck is a good one. Valve's compatibility rules are public, so you can test against them.
- Take small paid passes. A couple of hours on one build, with every bug in the dev's tracker. Each one is a credit and a client who might come back.
- Apply for QA roles at companies and publishers once you have a few reports to show.
- Stay in touch. Every patch needs a regression pass, and devs would rather call the tester who already knows the game.
Rates
I won't make up numbers. Freelance game testers usually charge per hour or per test pass, and QA companies pay their testers a wage. What moves the price is how many platforms and devices you cover, how big the game is, how much retesting is involved, and special skills like console certification, performance or network testing. When you quote, ask for the build size, the platforms and what "done" means.
Red flags
- "Test the whole game for free before launch." A short practice pass on a public demo is your call. A full QA pass is work.
- No build numbers, no tracker, no known issues list. You'll waste hours on duplicates.
- Pressure to stream or post an unreleased build. Don't, unless the dev says so in writing.
- Pay that depends on finding a set number of bugs. A clean build is a good result, not a failed test.
Frequently asked questions
Where can I find game QA testing work?
Game QA testers find work at QA outsourcing companies and publishers (on their careers pages and LinkedIn), on Work With Indies, in testing communities like uTest, on r/gameDevClassifieds and r/INAT, and by helping indie devs before a demo or launch. A free IndieGuild profile with your bug reports and platforms lets indie devs find you too.
How do I become a game tester with no experience?
Play public demos and jam games, write clean bug reports with steps, expected vs actual, the build and platform, and a video, and send them to the devs. Ask if you can show them, build a small portfolio, then apply for QA roles and offer small paid test passes.
What should a game QA portfolio include?
Sample bug reports, a test plan, test cases or a regression checklist, the devices you own, a compatibility or performance report, and an accessibility review.
How do game QA testers charge?
Freelance testers usually charge per hour or per test pass, and QA companies pay testers a wage. The price depends on how many platforms you cover, the size of the game, how much retesting there is, and special skills like console certification.
Is IndieGuild free for game QA testers?
Yes. Making a profile is free, and I don't take a cut of your gigs. You and the dev agree on pay and terms directly.
Let devs find you
Make a free QA tester profile with your bug reports and test plans, the platforms you test on, your rates and what you're open to (paid, rev share or hobby). When a dev posts a role that fits you, it lands in your inbox. It's free, and I don't take a cut of your gigs.
Make my profileMore guides
- How to find work as an indie game developer
- How to pitch a game dev (for creators)
- How to find game programming and game design work
- How to find game UI/UX design work
- How to find a QA tester for your indie game
- Game QA testers on IndieGuild