Rockstar Games India
Hands-on quality, growing leadership responsibility and continuity across global teams.
defects personally reported
GTA III DE testers led
people in India Nights, including me
testers onboarded across two teams
The journey
I began across GTA III, Vice City and San Andreas. After roughly three months, I was entrusted with functional leadership of GTA III DE, managing 10 testers for around eight months while remaining officially a tester.
I moved into a 24/7 Online Services QA model spanning India and Lincoln shifts. For the first six weeks, I was the sole India Night member, reporting to both Lincoln Day and Lincoln Night leads as coverage developed.
I represented QA in weekly Social Club Web sprints and later GTA VI Online Connectivity & Functionality sprints, alongside regular hands-on testing.
I led the 15-person team, covering allocation, work review, onboarding, formal performance reviews, leave approvals and testing coordination while staying hands-on.
Quality in practice
A useful defect report helps the next person understand the problem and reproduce it.
I reviewed reports for clear summaries, reproduction steps, probability, frequency, location, attachments and supporting context before escalating complete reports.
When a report needed work, I requested the correction and coached the tester privately. Repeated mistakes became additions to onboarding documentation so the learning reached the wider team.
I also worked on completionist validation: taking GTA III DE to 100% through natural gameplay and later supporting GTA V and Red Dead Redemption 2 events, checking progression, achievements and playability under production-like conditions.
Online services
My testing covered game functionality and the services around it, across development, certification and production environments.
GTA Online, Red Dead Online and GTA VI online work, including gameplay, connectivity, functionality and achievements.
Social Club Web, Rockstar Games Launcher and their integrations with game and achievement functionality.
Proprietary QA systems, P4V connectivity, test-case creation and context-sharing between global shifts.
In cross-functional sprints, I communicated testing status, expectations, blockers and risks. When a GTA VI timeline could not accommodate the remaining QA effort, I explained the gap and helped secure approved overtime and additional support.
Cross-shift continuity
I created a daily handover format when no standard template existed and used it throughout my India Nights leadership period.
It supported continuity with India Day, while I reported to Lincoln leads. Some colleagues adopted the format, although it did not become a mandatory standard.
What each handover covered
Leading while staying hands-on
hands-on testing
people leadership
meetings and stakeholder communication
Approximate time allocation during Online Services QA India Nights leadership.
I trained approximately seven testers on GTA III and another seven in India Nights. Training covered tools, build access, reporting, test practices and environment lifecycles.
I watched how each person understood information and adjusted the approach. For a tester who learned well through analogies, I deliberately used them in later explanations.
Formal reviews considered proactiveness, defect count and quality, reliability and initiative. I provided feedback and assessments for review by the appropriate leads.
I also supported development requests, clarified approval boundaries and helped team members understand the path toward future opportunities.
My official title remained in testing. The leadership described here reflects my functional responsibilities, including team allocation, reviews, onboarding and day-to-day coordination.
More about how I lead