Roles · Game QA Engineer · Junior
4 core skills, 65 in total. Expectations per skill, and what changes at the next level.
This page lists what a Junior } 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: Game Development.
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Runs basic performance tests: measures FPS in key scenes, captures framerate drops. Reports performance bugs specifying hardware configuration and reproduction conditions.
Tests basic physical interactions: collisions, gravity, ragdoll. Finds clipping bugs, falling through geometry, characters getting stuck in objects.
Performs basic functional game testing using prepared test cases. Reproduces bugs step by step, files defects in Jira specifying platform, build and screenshots.
Evaluates basic user experience: tutorial clarity, hint readability, menu navigation convenience. Reports UX issues as a separate bug category in the tracker.
Not assessed by the team, but part of the self-assessment and the development plan.
65 skills get a higher expectation or become core when moving from Junior to Mid-level. The biggest jumps first.
} in the open competency matrix: 65 skills across 5 levels. The matrix is free for individuals and stays free.