The role in one line. You decide whether a build is good enough to ship, and you keep the work moving so it gets there.

What the job is

This is two disciplines that come from the same place: process rigour, systematic documentation and accountability. On the quality side you own testing across every live title. On the production side you own the project management that keeps four games shipping in parallel. It is not a standalone tester role and it is not a standalone project manager role.

Responsibilities

- Release sign-off. Test builds against specs and acceptance criteria, run regression and fix verification, and give the sign-off that approves a build for release.
- Bug discipline. Log bugs with explicit reproduction steps, device information and screenshots, and triage them with the Technical Director. Test coverage spans a device matrix from low-end to high-end Android and iOS.
- Live quality signals. Watch crash and ANR data from live games, and use our internal review-analysis tooling to surface what players are actually reporting.
- The production thread. Own the project management tool across all titles. Attend the cross-functional meetings, capture tasks, decisions and scope changes as they happen, and update sprints immediately rather than at end of day.
- Release structure.



Every release is a documented collection of tasks and issues, with commit-to-issue discipline held with engineering.
- Escalation. When a scope change or blocker will affect a milestone, tell the founders before being asked.

Who you are

- You are systematic. You document as you go, and your bug reports are reproducible by someone who was not in the room.
- You are comfortable saying no. A sign-off means something. You can hold a release when it is not ready and explain why in terms people accept.
- You think in process. You see where work stalls between people and you fix the seam rather than chasing individuals.
- You are close to the player. Crash dashboards and store reviews are the same signal to you as a failing test case.

Nice to have

- Experience running QA on live mobile titles.
- Hands-on with Jira or an equivalent at an ownership level, not just as a user.
- Any background where you built a process rather than inherited one.

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.

📌 QA Lead & Producer (Chennai)
🏢 Highbrow Interactive
📍 Chennai