Building and testing simple, high-quality code for software.
Apprentices learn to build, test, and deploy software solutions across the full development life cycle. The programme covers writing clean, maintainable code; designing and developing user interfaces; working with relational and non-relational databases; and applying testing methods including unit, integration, system, and user acceptance testing. Apprentices also learn to interpret design specifications, apply development methodologies such as agile and waterfall, and handle data responsibly in line with GDPR and organisational security policies.
On a typical week, an apprentice might pick up a ticket from the backlog, write and test code against a functional specification, and raise a pull request for review by a senior developer. They will debug issues, create or update test scenarios, and contribute to sprint ceremonies such as stand-ups or retrospectives. Interaction with designers, analysts, and project managers is common, and apprentices may occasionally work in a client environment to support user testing or requirements gathering.
Completing this standard opens routes to roles including application developer, web developer, mobile application developer, and junior software engineer. With experience, developers typically progress to mid-level and senior developer positions, or move into technical architecture, DevOps, or engineering management. Employers span almost every sector, from financial services, retail, and transport through to public sector bodies, defence contractors, and software consultancies of all sizes. Smaller firms may offer broader exposure earlier, while larger organisations tend to offer more structured progression paths.
Sorted by achievement rate.
Corndel is a UK-based strategic skills partner that helps employers use the Apprenticeship Levy to f...
Activate Learning is a UK education group that delivers apprenticeships and vocational training thro...
Abingdon & Witney College is a further and higher education college in Oxfordshire offering a wide r...
Completers typically move into roles such as Junior Software Developer, Application Developer, Web Developer, or Mobile Application Developer. Day-to-day responsibilities at this stage include writing and testing code against agreed specifications, fixing bugs identified through unit and integration testing, and contributing to sprint cycles within an agile team. Some move directly into mid-level developer positions, particularly in smaller organisations where they have carried broader project responsibility during the apprenticeship.
Within three to five years, developers commonly progress to Mid-level or Senior Software Developer, taking ownership of more complex features and beginning to mentor junior colleagues. From there, two tracks tend to open up. The leadership track leads toward Technical Lead, Engineering Manager, or Head of Software Development. The specialist track leads toward roles such as Solutions Architect, DevOps Engineer, or Security Engineer, with deep expertise in a particular technology stack, platform, or domain.
Employers hiring into these roles span almost every sector. Financial services firms, government departments, NHS trusts, defence contractors, transport operators, retailers, and games studios all employ software developers directly. Consultancies and digital agencies hire developers to build bespoke solutions for clients across industries. Roles exist at every scale, from small software houses with single-developer projects to large public sector programmes and multinational technology organisations.
Throughout the programme, the apprentice builds competence in real software development work, covering the full development life cycle, testing, debugging, and working within a development team. Assessment is tied to demonstrating genuine capability in the role, not just theoretical knowledge. Before the final assessment stage, the apprentice passes through a readiness point, often called the gateway, where the employer and training provider confirm the apprentice has met the required knowledge, skills, and behaviours. Final assessment then verifies that competence independently. Assessment models across many standards are currently being updated, so check the standard's gov.uk page for the current specification before committing.
Building a strong body of workplace evidence from the start makes a significant difference. Apprentices should keep records of the projects they work on, the code they write and test, and the decisions they make along the way, rather than trying to reconstruct this at the end. Regular check-ins with the employer and training provider help ensure progress is on track and that any gaps in the required knowledge, skills, or behaviours are identified and addressed well before the gateway.
Look for providers whose achievement rate sits above 65% on their FATP profile, with a strong employer satisfaction score indicating they stay in close contact with the hiring business, not just the apprentice. For this standard specifically, ask whether the curriculum covers the full software development life cycle in practice, not just theory, and whether apprentices are writing, testing and deploying real code from early in the programme. Providers who teach version control, testing frameworks and at least one current development methodology such as agile are covering the baseline. Learner reviews mentioning genuine project work are a good sign.
Be cautious of providers running large cohorts with a declining or unverified achievement rate. For this standard, the most telling warning sign is a curriculum heavy on theory and light on hands-on coding practice. If a provider cannot name the languages, testing frameworks or deployment tools apprentices will work with, or if their off-the-job training is mainly slide-based instruction, that is a problem. Vague answers about end-point assessment preparation, or providers who cannot point to alumni now working as developers or in related roles, suggest weak delivery.
There are no nationally mandated entry qualifications, but most employers expect candidates to have some grounding in programming or a relevant technical subject, whether through prior study, a bootcamp, or work experience. English and maths at Level 2 (GCSE grade 4 or equivalent) are typically required before the apprenticeship ends if not already held. Employers set their own additional requirements, so criteria vary between organisations and sectors.
The typical duration is 24 months, though this depends on the individual's starting point and employer context. Apprentices are employed throughout and spend the majority of their time doing real development work. A portion of working hours is dedicated to off-the-job training, covering theory, skills and knowledge. The exact off-the-job requirement is subject to current government policy; check the latest specification on the Institute for Apprenticeships and Technical Education pages on gov.uk for current figures.
Before reaching end-point assessment, the apprentice must pass through a gateway, at which point the employer, training provider and apprentice confirm that the required knowledge, skills and behaviours have been developed. Assessment models for many standards are currently being updated under Skills England reforms. Check the current assessment plan on gov.uk for the precise methods, but expect the apprentice to demonstrate competence in writing and testing code, problem solving, and working across the software development life cycle.
The funding band for this standard is £18,000, which is the maximum that can be drawn from government funding. Levy-paying employers (those with a payroll above £3 million) pay through their digital apprenticeship service account. Non-levy employers co-invest with the government, currently contributing 5% of the funding band cost. Employers taking on an apprentice aged 16 to 18, or a care leaver under 25, may pay nothing depending on their size. Check current co-investment rates on gov.uk as these can change.
Day-to-day work involves writing and testing code against design specifications, debugging issues, building user interfaces, and linking code to databases. Apprentices contribute to sprints or project tasks alongside analysts, architects and senior developers. They attend team meetings, interpret technical documentation, and may take part in user testing sessions. In smaller teams they may work more independently under supervision. The work spans web development, application building, internal tools, or sector-specific systems depending on the employer.
Completers typically move into mid-level or senior developer roles, or specialise in areas such as back-end development, mobile applications, or security. Progression routes include the Level 6 Software Engineer degree apprenticeship or other higher technical qualifications. Some move into related roles such as DevOps engineer, technical lead, or solutions architect over time. Employers across every sector hire at this level, so progression is not limited to one industry.
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: 2.
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.