Every game ships with bugs somebody missed. The question is how many, and how bad. We need a Remote Game Tester to catch the ones that would've slipped through — the frame drop nobody flagged, the tutorial that quietly loses half its players by step three. What the Job Actually Is Not a checklist you run and forget. You'll play unfinished builds — strategy this week, VR the next, maybe a puzzle game after that — and try to break things on purpose. When something's off, write it up well enough that a developer who's never touched that part of the code can fix it without three follow-up questions. That's the real skill. More than hours played. What Fills the Day Playthroughs, mostly. Not only that, though. Group playtests where testers compare what they're each finding on the same build. Bug reports need specifics: steps to reproduce, what you expected, what actually happened instead. Beyond bugs — controls that feel wrong, an economy that's clearly out of balance, progression that stalls for no obvious reason. Cross-platform and multiplayer sync testing comes up a lot too. Those bugs hide until real players collide with each other. What Gets You Considered A high school diploma or its equivalent covers the educational side. Experience-wise — at least six months of hands-on testing, or gameplay experience serious enough that you've caught yourself noticing bugs other players scroll right past. High school diploma or equivalent 6+ months testing experience, or a genuinely critical gameplay background Notices small things others miss — frame drops, timing, a tutorial that drags Bug reports that make sense to someone who's never seen the build Picks up unfamiliar genres and control schemes fast Handles multiple playtests without needing reminders Not required, but it helps: prior QA work anywhere, comfort with Jira or similar tools, a habit of writing detailed reviews even when nobody asked. How the Work Runs Play from wherever your setup lives — PC, console, mobile, whatever the build needs. Most of it's async. Nobody's locked into someone else's clock, though there's a weekly sync to compare notes. Posted in a few places right now, Naukri Mitra among them. Same screening either way. Tools You'll Use Jira for bugs. Discord for voice and group sessions. Trello keeps testing cycles organized. Cloud-based version management keeps builds up to date across the team. Reports live in shared docs — nothing elaborate, just organized enough that patterns across testers are easy to spot. Pay and What's Included This role pays $59,500 a year. Fully remote — work from wherever your setup already is Mostly async, one weekly team sync Real input into how shipped games turn out Structured onboarding, then ongoing feedback from senior testers Exposure across genres instead of getting stuck on one type of game Where It Can Lead Testers who keep catching what others miss tend to move into lead QA work or specialize in multiplayer sync, performance, or localization. Decent entry point into game development more broadly, if that's where you're headed. Apply Open to applicants in the U.S., Canada, the UK, the EU, Australia, India, and several other regions. Send a resume. If you've got bug reports or reviews you've written before, include a couple — they say more than a list of games you've played.