
QA Project Lead at Electronic Arts
I design the systems that make a QA organization's quality measurable and its people accountable.
I run QA for the EA SPORTS F1 titles with 28 direct reports in India, aligned with EA Romania and EA Birmingham.
Pick an object on the desk to jump there, or keep scrolling.
About me
I’m Nilesh Kasimahanti, a QA Project Lead at Electronic Arts in Hyderabad. I plan, run, and report the QA cycle for the EA SPORTS F1 titles across PS5, Xbox, PC, and Mobile. I lead 28 direct reports in India, run alignment with EA Romania, and manage stakeholders across EA Romania and EA Birmingham.
I started at PTW in 2021 as a Trainee Test Engineer and went straight to Senior in fourteen months, a double promotion that skipped the Test Engineer grade. I moved to EA in 2023, became QA Lead in 2025, and QA Project Lead in October 2026. Most of what I do now is building the systems underneath quality: rating models, patch verification checks, and reporting that hold up without me in the room.
Outside of work I follow Formula 1 closely and spend time on independent product research, mostly applying product management frameworks to mobile games I play. Some of that research is in the writing section below. I also maintain an open source developer tool, Claude Context Optimizer, that cuts the token cost of AI coding sessions. I hold certifications in project management from Google and ISB, and a postgraduate program in product management (INSAID / Accredian).
How I lead
I lead 28 people directly in India, and I’m the alignment point with EA Romania and the stakeholder contact for cross-studio work with EA Romania and EA Birmingham. The 28 is today’s headcount: the team runs on a project ramp and de-ramp cycle, climbing to about 40 and returning to about 20, so the structure has to absorb people joining and leaving without the standard slipping. That is three operating contexts with different time zones, priorities, and expectations. I don’t hold it together through proximity or heroics. I hold it together with three commitments.
The standard is written down before anyone is measured against it. Performance runs on a weighted 9-box model with role-adjusted bands, because a QA Tester and a Quality Analyst do different jobs and shouldn’t be held to one bar and then called objective. Every person can trace their rating to evidence, and development conversations start from the same rubric, so they are about a specific gap rather than an impression.
Ownership is never ambiguous, especially across sites. At PTW I was the escalation point between clients and internal delivery on two concurrent titles, long before I had the authority to fix the structure. That taught me what unclear ownership costs. Today it shows up as an onboarding workflow that clears every required step before test work starts, weekly alignment and execution tracking, and one accountable name for each deliverable at each studio.
Risk goes up early, and status is reported as outcomes. I manage capacity, schedules, and change requests for each cycle, and I raise risks to senior managers while there is still room to act. Partners get coverage, defect status, and results rather than a list of activity. Growing the team from 20 to 46 people across two sites taught me that scale only works when the structure carries the people, not the other way around.
Experience
How I define and measure quality
Both systems below started the same way: an existing process was subjective, inconsistent, or nonexistent, and I built something auditable in its place.
Independent Product Analysis: Game Economy & Monetization
Everything in this section is personal research, done in my own time with public industry data. It isn’t EA or PTW work product. I keep it separate from my QA work on purpose: it’s evidence of how I think about a product, not evidence of what I was assigned to do.
None of this was assigned. It’s the clearest evidence I have that I read a product’s numbers and ask what’s driving them: the same instinct a QA Lead needs to prioritize risk, and a TPM needs to prioritize scope.
Certifications & recognition
Skills
Let's talk
I’m open to QA Project Lead, QA Manager and project management roles at game studios, and to conversations about technical program management as a next step. The fastest way to reach me is email.
Hyderabad, India