Carrying out tests to make sure computer software works as intended and is fit for purpose.
Apprentices learn how to plan, design, and execute tests across software systems to confirm they behave as intended. This includes understanding different testing types such as functional, regression, and integration testing, writing test cases and scripts, logging defects clearly, and working within quality assurance processes. Apprentices also develop skills in test documentation, risk-based testing approaches, and using industry-standard tools to manage test cycles. The role sits within software development teams, so an understanding of the software development lifecycle is central to the programme.
A typical week involves reviewing requirements or user stories to identify what needs testing, writing and executing test cases, and raising defect reports when software does not behave as expected. Apprentices use test management tools and may work with automated testing frameworks depending on the employer. They attend sprint ceremonies in agile teams, liaise with developers to investigate failures, and help track defects through to resolution. Producing clear test evidence and maintaining traceability records are regular outputs.
After completing this apprenticeship, typical job titles include Software Tester, QA Analyst, or Test Analyst. Progression paths often lead to Senior Tester, Test Lead, or Test Manager roles, with some testers moving into performance testing, security testing, or test automation engineering as a specialism. Employers span almost every sector including financial services, retail, public sector, healthcare, and software companies. Organisations that build or procure bespoke software are consistent hirers, making this a transferable qualification across industries.
Sorted by achievement rate.
Apprentify is a specialist digital and tech apprenticeship and training provider that focuses on hel...
Completing this standard typically leads into roles such as Junior Software Tester, QA Analyst, Test Analyst, or Junior Automation Tester. Some completers move directly into a defined Software Tester position within the team where they trained, while others step into slightly broader roles covering quality assurance across a development cycle. The specific title varies by employer, but the function is consistent: designing and executing tests, logging defects, and supporting release decisions.
Within three to five years, testers commonly move into Mid-level Test Analyst, Senior QA Engineer, or Test Lead positions. From there, two tracks tend to diverge. One runs toward technical specialism, including roles such as Automation Engineer, Performance Test Engineer, or Security Test Analyst. The other moves toward team leadership and process ownership, with titles like QA Manager or Head of Quality Assurance. Some practitioners also transition into adjacent roles such as DevOps Engineer or Business Analyst, drawing on their understanding of software behaviour and requirements.
Demand for software testers sits across a wide range of sectors in the UK. Software houses, digital agencies, and technology consultancies hire regularly at this level, as do in-house digital teams within financial services, retail, healthcare, and the public sector. Both large enterprises running complex systems and smaller product companies building consumer or B2B applications employ testers. Central government departments and NHS trusts are also consistent employers, particularly for those with experience testing regulated or high-stakes systems.
Learning takes place in the workplace, with the apprentice applying software testing knowledge and skills to real projects throughout the programme. Before final assessment can begin, the apprentice must pass a gateway check, which confirms that they and their employer are satisfied the required knowledge, skills and behaviours have been developed to the necessary level. Final assessment then confirms the apprentice can carry out testing work competently, covering areas such as test planning, defect identification and quality assurance processes. Assessment models for many standards are currently being updated, so check the standard's gov.uk page for the current specification.
The strongest preparation is building a record of workplace evidence from early in the programme rather than scrambling to gather it near the end. Apprentices should document the testing activities they carry out, the tools and techniques they use, and how they respond when defects are found or test results are unexpected. Regular review meetings with both the employer and training provider help identify any gaps in the knowledge or skills needed before the gateway, so these can be addressed in good time.
Look for providers with an achievement rate above 65% on their FATP profile, and check whether employer and apprentice satisfaction scores are both above 70. For this standard specifically, ask whether the curriculum covers both manual and automated testing, and whether apprentices work with tools that employers actually use: Selenium, JIRA, Postman, or similar. Providers with active employer partnerships are better placed to offer apprentices exposure to real test environments rather than artificial exercises. Learner reviews mentioning genuine project work, defect reporting on live systems, and involvement in agile sprint cycles are a stronger signal than general praise.
Be cautious if a provider has high enrolment numbers but a falling achievement rate over successive years, which can indicate over-recruitment relative to actual support capacity. Providers who speak vaguely about "industry tools" without naming them are often behind the curve on what testing teams currently use. If off-the-job training is delivered entirely through classroom slides with no access to realistic test environments or version control systems, apprentices will arrive at EPA underprepared. Opaque cohort sizes and no visible learner reviews should prompt further questions before you commit.
Employers set their own entry criteria, but most look for a good level of IT literacy and an interest in problem-solving. Some employers require GCSEs in English and maths, while others accept functional skills qualifications. Prior experience with software or coding is useful but not always essential. Apprentices who do not already hold level 2 English and maths must achieve them before completing the apprenticeship.
The typical duration is around 24 months, though the actual length depends on the apprentice's pace of progress and prior experience. Apprentices remain employed throughout, applying their learning directly in the workplace. A portion of working hours is dedicated to off-the-job training. The current specification, including time commitment details, is published on the Institute for Apprenticeships and Technical Education page on gov.uk.
Before taking their end-point assessment, apprentices must pass through a gateway, at which point the employer and training provider confirm the apprentice has the knowledge, skills, and behaviours set out in the standard. Assessment methods typically include practical work-based projects and a professional discussion. Many assessment models are currently being updated under Skills England reforms, so check gov.uk for the latest specification before selecting a provider.
The funding band for this standard is £18,000, meaning the government contributes up to that amount toward training costs. Levy-paying employers draw from their digital apprenticeship service account. Non-levy-paying employers contribute 5% of training costs, with the government covering the remaining 95%. Very small employers taking on an apprentice aged 16 to 18 pay nothing. Funding covers training and assessment only, not the apprentice's wage.
Day-to-day work involves planning and executing tests on software applications to identify defects and confirm the software meets its requirements. Apprentices write test cases, log and track bugs, and work closely with developers to retest fixes. They may carry out functional, regression, or exploratory testing, often using test management tools. The role is heavily collaborative, sitting within development teams and contributing to quality assurance at each stage of the software lifecycle.
Completing this level 4 apprenticeship gives a strong foundation for a career in software quality assurance. Many completers move into senior tester or QA lead roles. Others specialise in areas such as automation testing, performance testing, or security testing. Further study options include a level 6 degree apprenticeship in software engineering or a related digital discipline, as well as industry certifications such as ISTQB, which many employers support.
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: 91.
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.