Every game that ships has already been broken a hundred times behind the scenes — by testers who found the glitch before players ever could. That's the job we're filling: Remote Game Tester, playing unreleased builds and telling developers exactly what's wrong before launch day arrives.
The Actual Job
Playing games all day sounds like the dream, and honestly, parts of it are. But this role asks you to play differently — watching for anything that breaks, feels wrong, or doesn't align with the design's intent. You'll write it down, explain it clearly, and hand it off in a way a developer can actually use without chasing you for details.
It's remote, and the hours bend around you rather than the other way around. Part-time works. So does full-time.
What You'd Be Doing
- Play unreleased or in-progress game builds across different platforms.
- Track down bugs, glitches, and anything that behaves inconsistently.
- Compare gameplay mechanics against what they're supposed to do and flag anything that doesn't line up.
- Write bug reports detailed enough that someone else could reproduce the issue from your notes alone.
- Talk directly with developers when a report needs clarifying.
- Go back through patched builds to confirm a fix actually worked.
What Gets You In the Door
- Education: High school diploma or equivalent.
- Experience: None required — this is a true entry-level role at 0 years of professional experience.
- You've spent real time across console, PC, or mobile gaming — not just one platform.
- You can explain a problem in writing without leaving out the part that actually matters.
- Internet that won't drop mid-session, plus somewhere quiet enough to actually pay attention.
- You don't mind replaying the same five minutes of a level a dozen times to pin down what's causing an issue.
Things That'll Set You Apart
- Any past QA work, gaming-related or not.
- Some hands-on time with bug-tracking software like Jira.
- A decent read on how different game genres typically play and what "normal" looks like in each.
- Some sense of how a game moves from build to release, even if it's just casual knowledge.
What It Pays
$44,769 a year. On top of that:
- You pick part-time or full-time based on what actually fits your schedule.
- No commute, no fixed desk, no office hours to clock into.
- You'll be playing titles months before anyone outside the studio sees them.
- It's a real foot in the door if you want to move toward QA or development later on.
Who Tends to Be Good at This
Less about credentials, more about instinct — if something in a game feels slightly wrong and you can't quite explain why yet, that's the exact skill this job runs on. You'll see roles like this pop up on job boards including Naukri Mitra pretty regularly, but the testers who stick around long-term usually care about how a game works underneath, not just about playing it.
A lot of people use this as a first step into the industry — into QA, production, or development down the line.
The Difference Between a Useless Bug Report and a Good One
"Something felt off" doesn't help anybody. A report that says what happened, how to make it happen again, and what should've happened instead — that's what actually gets fixed before a game ships.
Apply
Send your resume and tell us about a bug or issue you noticed in something you played recently, even something minor. We care more about people who notice things than people who just log a lot of hours. This one's remote, and where you're located won't count against you.
