Game Programmer

Game Programmer.
Level 7 assessment.

Game programmers lead the design and implementation of reliable, efficient software in real-time interactive environments. Version 1.2 has two options: game software programmer and game technology programmer.

ST0953Level 7Planned assessment
ST0953 · Level 7Game Programmer preparation focusSoftware & DevOps · Planned assessment
  1. 01
    Design performant and maintainable systems within real-time platform constraints.Use authentic work to explain decisions and individual contribution.
  2. 02
    Diagnose complex interactions using evidence, controlled experiments and engineering trade-offs.Use authentic work to explain decisions and individual contribution.
  3. 03
    Lead technical delivery and communicate decisions across creative and engineering disciplines.Use authentic work to explain decisions and individual contribution.

Illustrative preparation focus from this guide, not an assessment method sequence or official rubric. Confirm the applicable registered version.

Confirm the route before you plan.

Planned portfolio only. Confirm option, Level 7 funding position, secure artefact review, approval, assessor capability, capacity, fees and dates.

Checked 20 October 2026: version 1.2 is approved for delivery with two occupational options and no scheduled replacement shown. Level 7 funding restrictions apply to relevant new starts from 1 January 2026.

View the official standard and assessment plan ↗

What this occupation demonstrates

Game programmers lead the design and implementation of reliable, efficient software in real-time interactive environments. Version 1.2 has two options: game software programmer and game technology programmer. Both require strong engineering judgement, but their users and artefacts differ: one works directly on a game experience, while the other develops engines, libraries, tools or platform technology for developers. Providers must choose the registered option explicitly and secure a project that can demonstrate personal contribution without exposing unreleased games, source code, platform credentials or licensed assets.

Providers and games employers supporting experienced programmers in game-software or game-technology roles.

  • Design performant and maintainable systems within real-time platform constraints.
  • Diagnose complex interactions using evidence, controlled experiments and engineering trade-offs.
  • Lead technical delivery and communicate decisions across creative and engineering disciplines.

Prepare for a fair assessment

Use the applicable plan as your starting point. The following are preparation prompts, rather than additional gateway requirements or a substitute for the assessment specification.

  1. Record the selected option at enrolment and gateway. Map option-specific work rather than presenting generic software development as sufficient.
  2. Select a project where architecture, performance, testing and the apprentice's decisions are visible. Agree how source, builds and proprietary tools can be reviewed without external public upload.
  3. Use a synthetic artefact for public practice. Strip unreleased title names, repository URLs, platform material, credentials, player data and third-party assets.
Provider buying guide

Plan a useful handover.

Buy this route around the option, development environment and IP controls. Ask the employer to describe the apprentice's technical authority, target platforms, access to profiling and build systems, and a project that can produce a reviewable software artefact. The provider owns option and curriculum mapping; the employer owns repository, licence and disclosure decisions; the proposed assessment partner should explain secure source review, assessor currency across engines and platforms, conflict checks and how individual contribution is tested in a large studio team.

A realistic evidence conversation

Illustrative, not prescribed: a game-software apprentice builds a synthetic crowd system with a fixed frame-time budget. The record shows requirements, architecture, profiling baseline, implementation, automated and play testing, an abandoned approach, optimisation and remaining limitations. The code contains no employer IP or third-party assets. A game-technology cohort would need an option-relevant artefact instead. Use the case to test project scope, secure review, personal contribution and how performance claims are independently checked.

Handover checks

  1. Provider confirms the registered option, Level 7 depth and suitable software-artefact project.
  2. Employer IP owner approves source, build, platform and asset disclosure boundaries.
  3. Assessment contact confirms secure artefact access, environment needs and contribution checks.

Questions to ask before buying

  • How will you maintain option-specific assessment across game software and game technology roles?
  • What secure route supports proprietary code or builds that cannot leave the studio?
  • How will performance claims and personal contribution be tested in a team codebase?
Original preparation material

Think it through.
Explain your decisions.

These are original learning prompts. They are not live assessment questions, an official mock paper or a prediction of your result.

1. A feature meets its design goal but causes frame-time spikes. How would you decide what to change?

Explore a response structure

Profile before optimising, identify the relevant budget and reproduce the spike. Compare architectural and content trade-offs, protect the intended player experience and verify the result on representative hardware.

2. How would you demonstrate your contribution in a large codebase?

Explore a response structure

Use approved change history, design notes, tests and review evidence to identify decisions you owned. Explain dependencies and team contributions without sharing proprietary source outside the authorised route.

3. When should a game-specific solution become shared technology?

Explore a response structure

Consider repeated need, stable interfaces, performance, maintenance, documentation and effects on delivery teams. Explain the cost of abstraction and the evidence needed before standardising.

Open practice studio

Questions about this standard

Which options apply?

Game software programmer and game technology programmer. The provider and employer should select the option through the actual occupation and apply its option duties, not personal preference.

Which methods apply to version 1.2?

The official summary specifies a project producing a software artefact with presentation and questions, plus a professional discussion underpinned by a portfolio. Confirm option and gateway requirements from the full plan.

Does Level 7 guarantee public funding?

No. Skills England flags Level 7 funding restrictions for starts from 1 January 2026. Eligibility requires a current case-specific check; privately funded delivery and assessment suitability are separate questions.

Sources and review

Guide updated 20 October 2026; official source reviewed 20 October 2026. Standard titles, versions and requirements can change. Always check the linked official record for the apprentice’s start date.

Skills England: Game Programmer ↗