Program reliable and efficient software.
Apprentices learn to design and develop complex technical systems for games or gaming technologies, working within the performance constraints of real-time graphical environments. The programme splits into two options: Game software programmer, focused on building gameplay systems and asset pipelines for a specific title, and Game technology programmer, focused on creating engines, libraries, and tools used by other developers. Both options involve leading technical planning, setting and maintaining code standards, researching emerging technologies, and providing technical authority across creative teams.
Work varies by option but typically includes writing and optimising code in languages such as C++ or C#, using game engines such as Unreal or Unity, and collaborating with designers, artists, animators, and audio engineers to integrate systems. Apprentices attend planning sessions, review and diagnose bugs in complex codebases, and contribute to technical documentation. Game technology pathway apprentices may also manage support portals, track user issues, and communicate tool updates to a broad internal or external user base.
Completion typically leads to senior or lead programmer roles, with titles such as gameplay engineer, rendering engineer, game server programmer, or developer relations engineer. Game software programmers tend to progress within studios of any size, from indie teams to large international studios. Game technology programmers are more commonly found at console manufacturers, middleware companies, and large platform-holding studios. Both pathways offer routes into technical director or engineering lead positions with further experience.
Sorted by achievement rate.
No training providers currently listed for this standard.
Graduates typically move into mid to senior-level positions rather than entry-level roles, reflecting the Level 7 standard. Depending on the chosen option, that means titles such as Gameplay Programmer, Rendering Engineer, Graphics Engineer, Game Server Programmer, Mobile Game Developer, or Software Development Engineer on the software track, and Engine Developer, Tools Programmer, or Developer Relations Engineer on the technology track. Both routes carry responsibility for technical decision-making from the outset.
Within three to five years, most move into Senior Gameplay Programmer, Senior Graphics Engineer, or Senior Tools Programmer positions. Beyond that, two tracks tend to diverge. Those drawn to people and project leadership progress toward Lead Programmer, Technical Director, or Development Director. Deep specialists stay closer to the code, moving into Principal Engineer or Staff Engineer roles focusing on a particular domain such as rendering, physics, or platform architecture. Both tracks involve mentoring junior programmers and shaping technical standards.
The UK games industry spans a wide range of employers. Large international studios with hundreds of developers, mid-size independent studios, and small indie teams all hire Gameplay and Graphics Programmers. The technology track opens additional doors: console and hardware manufacturers, game engine developers, and middleware providers employ Game Technology Programmers specifically. Mobile game development companies, particularly those with significant online infrastructure, also hire Game Server Programmers. Roles exist across England, Scotland, and Wales, with notable clusters in London, Guildford, Leamington Spa, and Edinburgh.
The apprentice learns while working in a games development role, building knowledge and practical skills across the core and their chosen option, either game software programmer or game technology programmer. Before moving to final assessment, the apprentice and employer must confirm readiness at a gateway point, demonstrating that the apprentice can perform at the level expected of the occupation. Final assessment then confirms whether the apprentice has genuinely mastered the knowledge, skills and behaviours required. Assessment models for many Level 7 standards are currently being updated under ongoing reforms, so check the standard's gov.uk page for the current specification before committing to a programme.
Gathering evidence of real work throughout the programme is far more manageable than trying to reconstruct it at the end. That means keeping records of technical decisions made, systems built or maintained, and examples of leading or coordinating work within a team. Working closely with both the employer and training provider from early on, rather than only near the gateway, helps identify gaps while there is still time to address them. Treat each project or sprint as an opportunity to document competence, not just deliver code.
Look for providers with achievement rates above 65% and strong employer satisfaction scores on their FATP profile, particularly from studios or technology companies rather than generic digital employers. Because this is a Level 7 standard with a core plus options structure, ask whether the provider actively delivers both the Game software programmer and Game technology programmer pathways, or only one. Providers worth shortlisting will show evidence of tutors with industry backgrounds in games development, links to professional bodies such as UKIE or TIGA, and teaching that covers contemporary engines (Unreal, Unity, proprietary in-house engines) and real platform submission requirements.
Be cautious of providers who deliver a wide range of digital apprenticeships but cannot point to specific games industry experience among their teaching staff or their employer partners. A high learner volume paired with a declining or unknown achievement rate is a warning sign at this level. If a provider cannot explain how they handle the core and options split, or gives vague answers about how apprentices gain exposure to actual platform SDKs, toolchain work, or live project codebases, that suggests the curriculum may be general software development with a thin games overlay.
Employers set their own entry criteria, but this is a Level 7 standard, so most expect applicants to hold a relevant degree or equivalent experience in software engineering, computer science, or a related discipline. Strong programming skills, ideally in C++ or another systems language, are typically expected. Applicants must be employed in a role where they can apply advanced programming work on real game systems or game technologies throughout the programme.
The typical duration is 24 months, though the exact minimum may be affected by ongoing reforms to apprenticeship rules. Check the current specification on the Institute for Apprenticeships and Technical Education page on gov.uk for up-to-date requirements. The apprentice is employed throughout and applies learning directly to their day-to-day work. A portion of their time must be spent on off-the-job learning, with the current required percentage confirmed in the same specification.
Before end-point assessment, the apprentice must pass through a gateway, where the employer and training provider confirm the apprentice has met the knowledge, skills, and behaviours set out in the standard. Assessment models for many Level 7 standards are currently being reviewed as part of Skills England reforms, so check the current end-point assessment plan on gov.uk for the most accurate picture. The apprentice must demonstrate genuine competence, not just course completion, before being entered for final assessment.
The funding band for this standard is £19,000, which caps what can be spent from apprenticeship funding. Large employers with a levy account use those funds directly. Smaller employers without a levy account co-invest with the government, currently contributing a small percentage of training costs. Employers with fewer than 50 staff who take on an apprentice aged 16 to 18 pay nothing, with the government covering the full cost. Speak to a training provider to confirm current co-investment rates.
Day-to-day work depends on which option is chosen. A game software programmer builds and maintains systems that feed into a specific game title, such as gameplay mechanics, character physics, or asset pipelines, working closely with designers, artists, and QA staff. A game technology programmer develops engines, libraries, and tools used by other developers, often targeting specific hardware architectures. Both options involve planning and coordinating technical work, setting standards, diagnosing complex bugs, and communicating with a wide range of creative disciplines.
Typical next roles include senior or lead programmer, rendering engineer, gameplay engineer, game server programmer, or developer relations engineer. Some move into technical director or principal engineer positions, particularly in larger studios. Game technology programmers may progress into specialist roles at hardware manufacturers, middleware companies, or engine developers. Because this is already a Level 7 qualification, further academic progression would be at postgraduate level, though many in this sector advance through professional experience and studio seniority rather than further formal study.
Tell us a bit about your team and we'll send a shortlist.
Tell us your requirements and we'll match you with the right training providers.
Curated by Alex Lockey, FATP founder and editor. Last reviewed: .
Sources include the apprenticeship's official specification on apprenticeships.gov.uk, Skills England guidance, IfATE archive records, DWP funding bands, and provider data sourced directly from the public Apprenticeship Provider and Assessment Register (APAR). Standard reference: 650.
Some sections on this page were drafted with AI assistance from published source data and reviewed by a human editor before publication. See our editorial methodology for how we maintain this content. Spotted something out of date? Tell us.