QA Lead

Role

Plans and coordinates the testing process across builds, devices, risks, and release criteria.

Description

A QA Lead runs testing as a production discipline. They decide what gets tested, when, on which devices, by whom, and against what release criteria, then keep that plan honest as builds, scope, and deadlines shift.

In immersive work the testing surface is wide: one project may need technical passes, comfort checks, accessibility verification, device coverage, and rehearsal under venue conditions. The QA Lead's real product is coverage, making sure nothing important is being tested only by accident, or not at all.

Discipline-Specific Description

Inside the testing discipline, the QA Lead is the connective role: they schedule the specialist testers' work, weigh their findings against each other, and translate the overall state of testing into a straight answer to the question of whether the work can ship.

Scope Note

Usually covers test planning and coverage decisions, release criteria, tester coordination, device and context prioritization, risk tracking, schedule negotiation with production, and reporting testing status to the wider team.

Boundary Note

The QA Lead owns the testing process as a whole; the Technical QA Lead goes deeper on test strategy for technically complex systems, and on smaller teams the two are one job. Deciding which defects get fixed is shared ground with the Bug Triage Lead, and running individual sessions belongs to the testers themselves.

Collaboration Note

Works with QA and specialist testers, bug triage roles, producers, technical directors, and the leads whose release dates depend on what testing finds.

Related entries