This apprenticeship has options. This document is currently showing the following option:
Program reliable and efficient software.
This occupation is found in the games and interactive entertainment industries where programmers create software designed for entertainment. This includes organisations which develop games for games consoles, desktop computers, mobile devices, websites and TVs. This is a core and options apprenticeship standard, which means that apprentices must complete the core, and one option out of Game software programmer or Game technology programmer. Companies which employ Game software programmers range from large, international studios employing hundreds of staff, to small indie studios made up of a few developers. Game technology programmers are often employed by hardware developers (e.g. console manufacturers), middleware providers (e.g. game engine developers) as well as large game studios, and would include specialists like server programmers in mobile game development companies.
The broad purpose of the occupation is to program reliable and efficient software within the constraints of real-time graphical environments running on contemporary gaming platforms. Such programmers lead the development of technical systems which feed directly or indirectly into the player experience of a game. These technical systems could range from gameplay mechanics (e.g. programming a system of different attack moves and their effect on enemies) to asset pipelines (e.g. engineering tools which process geometry data in order to support a character customisation system) and custom technologies (e.g. a new graphics rendering system for displaying realistic-looking dragon scales). They collaboratively plan and coordinate the delivery of their work within a larger team and provide technical insight to a broad spectrum of creative disciplines. They create and maintain appropriate technical standards and stay informed of the latest technical requirements for gaming platforms, exploring new technologies and their potential application within the business. They diagnose and fix problems in complex systems that involve many interacting factors, initiating changes to software architectures to support an evolving design. Game software programmers work on a specific gaming title and their audience are the consumers of that product (gamers). Game programmers select and apply game engines and tools to realise a game design. They are responsible for the development of bespoke asset pipelines and work collaboratively with other developers to maximise the collaborative value of the team’s effort to the player experience. Game technology programmers work on the technologies that underpin videogames and their audience are other game developers. Game technology programmers design and create libraries, engines and tools which target specific hardware architectures or gaming platforms. They initiate and lead the development of standardised technologies and work collaboratively with a wide user-base to inform and improve their design and documentation.
In their daily work, an employee in this occupation interacts with a diverse creative community of developers, providing technical authority and insight to Game programmers, Designers, Producers, Artists, Animators, Audio engineers, Quality Assurance (QA) staff and Project managers. They may also interact with external stakeholders, such as publishers, platform holders and external QA. They work independently and collaboratively as required, reporting to Development directors, Technical directors, Producers, and senior staff. This applies to both options.
An employee in this occupation will be responsible for leading the design and development of bespoke technical systems which affect the allocation of significant project resources. They are responsible for planning and coordinating the delivery of work for themselves and junior programmers and provide technical insight and leadership to a range of creative disciplines within a larger team. They create and maintain technical standards across the organisation and its clients. This includes technical requirements needed to submit titles to console platforms. They lead research into new technologies, identifying potential opportunities for their application. They work under limited direct supervision, responsible for the quality and accuracy of their own work and sometimes the work of others. They ensure work is completed within agreed timescales and within budgets. As their work includes communicating with external stakeholders, they must present a professional image of their employer and themselves. This applies to both options.
This is a summary of the key things that you – the apprentice and your employer need to know about your end-point assessment (EPA). You and your employer should read the EPA plan for the full details. It has information on assessment method requirements, roles and responsibilities, and re-sits and re-takes.
An EPA is an assessment at the end of your apprenticeship. It will assess you against the knowledge, skills, and behaviours (KSBs) in the occupational standard. Your training will cover the KSBs. The EPA is your opportunity to show an independent assessor how well you can carry out the occupation you have been trained for.
Your employer will choose an end-point assessment organisation (EPAO) to deliver the EPA. Your employer and training provider should tell you what to expect and how to prepare for your EPA.
The length of the training for this apprenticeship is typically 24 months. The EPA period is typically 6 months.
The overall grades available for this apprenticeship are:
When you pass the EPA, you will be awarded your apprenticeship certificate.
The EPA gateway is when the EPAO checks and confirms that you have met any requirements required before you start the EPA. You will only enter the gateway when your employer says you are ready.
The gateway requirements for your EPA are:
For the game programmer, the qualification required is:
A project with a software artefact
You will be asked to complete a software artefact. The title and scope will be agreed with the EPAO at the gateway. As part of the project, you need to write a software artefact and submit this to the EPAO. The software artefact should be a maximum of 5000 (with a 10% tolerance).
You will have 12 weeks to complete the project and submit the software artefact to the EPAO.
You need to prepare and give a presentation to an independent assessor. Your presentation slides and any supporting materials should be submitted at the same time as the project output. The presentation with questions will last at least 90 minutes. The independent assessor will ask at least 5 questions about the project and presentation.
Professional discussion underpinned by a portfolio of evidence
You will have a professional professional discussion with an independent assessor. It will last 105 minutes. They will ask you at least 10 questions. The questions will be about certain aspects of your occupation. You need to compile a portfolio of evidence before the EPA gateway. You can use it to help answer the questions.
The EPAO will confirm where and when each assessment method will take place.
You should speak to your employer if you have a query that relates to your job.
You should speak to your training provider if you have any questions about your training or EPA before it starts.
You should receive detailed information and support from the EPAO before the EPA starts. You should speak to them if you have any questions about your EPA once it has started.
If you have a disability, a physical or mental health condition or other special considerations, you may be able to have a reasonable adjustment that takes this into account. You should speak to your employer, training provider and EPAO and ask them what support you can get. The EPAO will decide if an adjustment is appropriate.
Version | Change detail | Earliest start date | Latest start date |
---|---|---|---|
1.2 | End-point assessment plan revised. | 13/02/2023 | Not set |
1.1 | End-point assessment plan revised | 26/01/2023 | 12/02/2023 |
1.0 | Approved for delivery | 03/08/2021 | 25/01/2023 |
Crown copyright © 2025. You may re-use this information (not including logos) free of charge in any format or medium, under the terms of the Open Government Licence. Visit www.nationalarchives.gov.uk/doc/open-government-licence