Defines Docker infrastructure strategy for game testing: container test farm standards, automated game testing environment governance, container orchestration for QA pipelines. Conducts architecture reviews for containerized test infrastructure and optimizes FinOps for test compute resources.
Roles · Game QA Engineer · Lead
What a Lead } should know
21 core skills, 65 in total. Expectations per skill, and what changes at the next level.
This page lists what a Lead } is expected to know and do, skill by skill. Core skills are the ones a manager and peers assess in a review cycle; the rest count only in self-assessment. Main areas: Cloud & Infrastructure, DevOps & CI/CD, Testing & QA.
Core skills for a Lead
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Cloud & Infrastructure · 1
DevOps & CI/CD · 1
Defines DevOps strategy for game QA: establishes CI/CD standards for game quality gates, implements platform engineering approaches for test automation infrastructure, drives adoption of continuous testing practices in game development pipelines.
Testing & QA · 9
Defines game accessibility testing standards and certification requirements across the organization's game portfolio. Establishes accessibility QA pipelines, disabled gamer testing programs, and platform compliance verification workflows for all game releases. Conducts architecture reviews ensuring game engines and frameworks support extensible accessibility features and mentors QA teams on inclusive game testing methodologies.
Defines testing strategy at product level. Establishes quality assurance standards. Implements shift-left testing culture.
Defines testing strategy at product level. Establishes quality assurance standards. Implements shift-left testing culture.
Defines testing strategy at product level. Establishes quality assurance standards. Implements shift-left testing culture.
Defines testing strategy at product level. Establishes quality assurance standards. Implements shift-left testing culture.
Defines testing strategy at product level. Establishes quality assurance standards. Implements shift-left testing culture.
Defines testing strategy at product level. Establishes quality assurance standards. Implements shift-left testing culture.
Defines testing strategy at product level. Establishes quality assurance standards. Implements shift-left testing culture.
Defines testing strategy at product level for game projects: automated gameplay test standards, performance regression testing governance, multiplayer testing frameworks. Establishes shift-left testing culture with automated quality gates for game builds and content updates.
Observability & Monitoring · 1
Defines observability strategy for game QA operations: establishes SLO-based approach for game stability and performance monitoring, coordinates game incident management across QA and development teams, optimizes MTTD/MTTR for game-breaking issues through improved detection workflows.
Version Control & Collaboration · 1
Defines organizational LFS policies for QA asset versioning across multiple game projects and test environments. Coordinates storage budgets and retention rules for test recordings, automated capture artifacts, and performance baselines. Mentors QA engineers on effective LFS workflows and drives adoption of asset management best practices across QA teams.
Game Development · 7
Defines QA strategy for game mechanics across the project. Establishes testing standards for gameplay systems, balancing validation processes, and automated mechanics regression suites. Coordinates QA efforts with game designers on feature acceptance criteria.
Defines performance QA strategy for the studio. Implements continuous performance monitoring, establishes performance gates in CI/CD pipeline for each build.
Defines QA approach to physics testing at studio level. Builds library of typical physics bugs, implements fuzzing approaches for stress-testing physics systems.
Defines QA processes for the studio: implements risk-based testing, establishes quality metrics (defect leakage, escape rate). Manages QA team across multiple projects simultaneously.
Defines UX QA strategy for the studio. Implements A/B testing for UX decisions, establishes process for collecting and analyzing player feedback. Coordinates UX QA with game designers.
Defines technical strategy for Unity Engine. Establishes development standards. Coordinates technical direction.
Defines technical strategy for Unreal Engine C++/Blueprints. Establishes development standards. Coordinates technical direction.
Documentation · 1
Defines Runbook and Playbook Writing strategy at team/product level. Establishes standards and best practices. Conducts reviews.
Additional skills
Not assessed by the team, but part of the self-assessment and the development plan.
What changes at Principal
0 skills get a higher expectation or become core when moving from Lead to Principal. The biggest jumps first.
} in the open competency matrix: 65 skills across 5 levels. The matrix is free for individuals and stays free.