We're hiring a Game QA Tester for our team in MIHAN, Nagpur, full-time and on-site. If you've ever finished a level, hit a weird collision bug, and immediately wanted to know why it happened instead of just shrugging it off, this is probably a good fit. We work across a mix of mobile and PC titles at any given time, so the bugs you'll chase aren't always the same shape from one sprint to the next.
Qualifications
We're asking for a bachelor's degree here, and it doesn't have to be in game design specifically. Computer science or information technology backgrounds are common among people who apply, but honestly, what matters more day-to-day is whether you've actually done test case design and defect tracking before, even in a non-gaming context. That hands-on piece is the part we look at closely. A degree tells us you can commit to something structured over several years; it doesn't tell us whether you'd notice a frame drop that only happens on the third loop of an animation, so the practical experience carries more weight in how we evaluate an application.
Experience
You'll need 24 months in a QA or testing role. That's roughly two build cycles at most studios, enough time to have sat through a launch, dealt with the bug spike that follows, and learned which issues actually need to block a release versus which ones can wait for a patch. Someone earlier in their career often hasn't seen that full arc yet, from feature freeze through post-launch cleanup, and that's really what the two-year mark is meant to capture.
What you'll actually be doing
- Write and run test cases against new builds, covering everything from core mechanics to UI edge cases
- Log defects with clear repro steps, since a bug report that says "it's broken" costs the whole team time later
- Re-test fixes before they go out to confirm the patch actually solved the problem and didn't quietly break something else
- Sit in on regular check-ins with the dev team to flag patterns, like a specific system that keeps generating the same class of bug
- Run compatibility passes across the target platforms and device configurations we're shipping to
Some weeks are quieter than others. Right before a milestone build, testing tends to run long, and the bug backlog piles up fast; that's just part of the rhythm of the role, not something unusual. Crunch here isn't permanent; it shows up in bursts tied to specific milestones and then eases off once the build stabilizes, and we try to keep it that way rather than letting it become the default pace.
Skills
Manual game testing experience is the starting point, paired with real attention to detail. We also want someone comfortable using a bug-tracking tool day-to-day, and genuine gaming knowledge matters too. Not because we need someone who's beaten every title in a genre, but because knowing what "feels off" in combat pacing or camera movement is hard to fake and even harder to teach on the job. Someone who plays a lot, across different genres rather than just one, tends to catch these things faster than someone testing their first game.
On the bonus side, exposure to test automation tooling is useful, even at a basic level, since more of our regression suite is moving in that direction. Some familiarity with scripting, Python in particular, would let you contribute to that shift rather than just working around it. Prior console or mobile testing experience is a plus if you've got it, and an ISTQB certification is welcome but nowhere near a dealbreaker. What we'd rather see than any single certification is someone who can clearly explain why a bug matters and how they'd prioritize it against everything else in the tracker that week.
Life on the team
Naukri Mitra has listed a handful of QA roles this cycle, and this one's a bit more hands-on than most. You won't just be running through a checklist someone else wrote. Testers here regularly weigh in on whether a mechanic actually plays well, not just whether it functions, and that feedback gets taken seriously by the design side. It's not a passive role, and if you're the kind of person who stays quiet when something feels wrong in a build, this probably isn't the right seat. Design meetings include QA input as a matter of course here, not as an occasional courtesy, so the feedback loop between spotting an issue and someone actually looking at it is usually short.
Compensation and benefits
The role pays ₹73,500 a month. Beyond that:
- Health insurance
- Paid time off
- Provident fund contributions
- Relocation assistance for anyone moving to Nagpur for the job
- Accommodation support while you get settled
The last two are worth calling out given this is an on-site role in MIHAN. It's a stretch of Nagpur that's grown quickly with tech and industrial parks, so employers here typically build relocation support into the offer rather than treating it as an afterthought, and we've done the same. Health coverage kicks in from day one rather than after a waiting period, which isn't always standard for QA-level roles in this market.
Where this sits
The job is based on-site in MIHAN, Nagpur, Maharashtra, with no remote or hybrid option. If you've been scanning game QA tester openings around Nagpur and wanted something closer to MIHAN specifically, this one's local to that area rather than downtown. Pay is in line with, or slightly above, what similar QA roles in Nagpur are currently offering per month. The area itself has decent connectivity for anyone commuting from other parts of the city, which matters more than it sounds once you're doing it daily.
Applying
Send your application whenever you're ready; we're reviewing them as they arrive rather than waiting for a fixed cutoff date. If your background lines up, expect a call to walk through your past testing work and, more specifically, any games or interactive projects you've tested before. There's a short practical test as part of the second round: a small build with a handful of planted bugs, and you'll get a couple of days' notice before it's sent over rather than being asked to do it live. We'd rather see your normal process than watch you scramble under a timer.
