Level 5 Data Engineer Apprenticeship (ST1386) UK

By James Cotton, Founder, iO-Sphere

Most guides to this apprenticeship hand you a level description, an entry-requirements list, and no way to actually decide. That's the wrong shape for the real question. Levels aren't school years you climb from the bottom. They're entry points matched to the complexity of the work a role already holds. An experienced BI developer or software engineer often enters straight at Level 5 because their job already demands it. Someone whose role touches spreadsheets and dashboards is usually better served at Level 3 or 4.

So before the standard, the funding or the assessment, ask the practical question: what data-engineering work will this person actually do, week to week, at Level 5? If you can't fill the off-the-job hours with real pipeline work at that level, the learning detaches from the day job and becomes classroom theory with extra admin. In our experience, that's the main way a funded programme quietly fails.

Key figures at a glance

Standard

Data Engineer, Level 5 (ST1386), approved for delivery by Skills England. A revised assessment plan replaces the current version for new starts on 18 December 2026 (Skills England, accessed 2026-07-02)

Typical duration (the standard)

Typically 24 months

iO-Sphere delivery

15 months of training plus a 3-month end-point assessment

Entry requirement

Set by the provider, not by the standard: Skills England publishes no entry requirements for ST1386. Typically a Level 3 qualification in a relevant area (any grade), or equivalent programming experience, or 2 to 3 years in a related role

Funding band

Up to £19,000, the maximum government funding for ST1386 (Skills England). Bands are revised periodically, so confirm the live figure before committing budget.

Assessment

Two end-point assessment methods: a project evaluation report with presentation and questions, and a professional discussion. Overall grades are fail, pass, merit or distinction, and there is no written exam (ST1386 assessment plan, Skills England). Delivered by an independent assessment organisation from the register of end-point assessment organisations

What is the Level 5 Data Engineer apprenticeship?

The Level 5 Data Engineer apprenticeship is a work-based route that develops someone into a data engineer: the person who builds and maintains the pipelines and platforms that collect, move, clean and store data so analysts, dashboards and AI systems can use it. It runs on the Skills England-approved Data Engineer standard (ST1386), which sets out the knowledge, skills and behaviours the role requires.

Skills England maintains apprenticeship standards in England; it replaced the Institute for Apprenticeships and Technical Education (IfATE) on 2 June 2025. Funding policy now sits with the Department for Work and Pensions (DWP), following the machinery-of-government move confirmed on 16 September 2025. ST1386 is approved for delivery now, and a revised assessment plan replaces the current version for new starts on 18 December 2026 (Skills England, accessed 2026-07-02). Check the live standard page if you're planning a start around that changeover.

Level 5 sits above A-level and below a full bachelor's degree. On the domain ladder, it's the step beyond the Level 4 Data Analyst role: an analyst answers business questions with data; a data engineer builds the plumbing underneath so the data is there to answer them. If you're weighing those two, our data engineer vs data analyst comparison draws the line in detail.

Who it's for: entry requirements and eligibility

Entry requirements are set by the training provider, not by the standard: Skills England publishes none for ST1386, so they vary. Typically you need a Level 3 qualification in a relevant area (any grade): two A levels in a similar subject, a Level 3 apprenticeship, a BTEC Extended Diploma, or genuine programming experience such as working knowledge of Python, or 2 to 3 years in a related role. Ask any provider for theirs. "No degree needed" is true. "No prior knowledge needed" is not. Level 5 is engineering work, and it assumes a real technical starting point.

Apprentices also need English and maths to Level 2 (roughly a GCSE grade 9 to 4 standard pass, or an Ofqual-regulated Functional Skills Level 2). For anyone aged 19 or over at the start, that exit requirement has been optional since 11 February 2025, though it can still be funded if they lack it and the employer agrees. For 16 to 18-year-olds it remains a completion condition. Existing employees are eligible, and this is often the most powerful use of the route: upskilling someone who already knows your systems.

When Level 5 fits, and when it doesn't

Here is the committed test. Level 5 fits if the role involves at least two of: owning a production pipeline end-to-end; choosing and operating a data storage or processing platform; writing and maintaining transformation logic in Python or SQL at a scale that breaks naive approaches; or mentoring others on data infrastructure decisions.

It does not fit if the role's outputs are reports, dashboards or ad-hoc queries, however sophisticated, because those outputs are downstream of the engineering work, not the engineering work itself.

The error we see most is employers confusing a technically fluent analyst (someone who writes Python to interrogate data) with a data engineer, who builds the system that makes the data available to interrogate. They are different jobs, and the apprenticeship can only certify the second. The tell-tale signal of a role that can't hold Level 5 work: when you ask the line manager to list the pipeline-building tasks they'll assign, the list turns into a list of questions they want answered from data. That is analysis, not engineering.

Who this apprenticeship is not for

Be honest here, because it saves a wasted year. If the role genuinely doesn't contain data-engineering work (no pipelines to build, no platform to maintain, no data to move at scale), Level 5 is the wrong choice however keen the person is. You'd be funding a syllabus the job can't feed.

If the day job is closer to reporting and analysis, the Level 4 Data Analyst standard (ST0118) is the right fit. It develops people who work with existing data to answer business questions: querying, visualising, and communicating insight. If the role's outputs are reports, dashboards or analytical findings rather than the infrastructure that makes data available, ST0118 is the standard to look at, via the Level 4 Data Analyst route. If the work is foundational data-handling, a Level 3 route fits better.

And if the ambition is statistical modelling and machine learning rather than building the pipelines that feed it, that's the data scientist path: a different discipline, one iO-Sphere doesn't deliver at this level, so weigh it on its own merits elsewhere. The test is always the work, not the ambition. Talk to whoever manages the role about what tasks they'll actually assign at Level 5 before anyone enrols. The syllabus can't supply what the role doesn't contain.

What's covered: standard, curriculum and end-point assessment

ST1386 covers production-grade data engineering: designing and building data pipelines, working with languages such as Python and SQL, managing data storage and processing, applying data governance and security, and doing it all to the reliability standard real systems demand. iO-Sphere teaches these on real data rather than toy examples. Apprentices work in Prism, a simulated e-commerce company built on 500M+ rows, so they practise pipeline-building in a safe sandbox before it counts on live systems.

Assessment is where this route parts company with an academic course. There is no written exam. The end-point assessment (EPA) has two methods, both built on the apprentice's real work: a project evaluation report with a presentation and questions, and a professional discussion. Each method is graded fail, pass or distinction, and the two combine into an overall grade of fail, pass, merit or distinction (ST1386 assessment plan, Skills England). It is delivered by an independent assessment organisation, which the employer selects from the register of end-point assessment organisations. For anyone who dreads exams, that's a genuine relief: you're judged on what you can build, not what you can recall under a clock. Our end-point assessment glossary entry explains the mechanics.

Duration, structure and levy funding rules

iO-Sphere delivers the Level 5 Data Engineer apprenticeship in 15 months of training plus a 3-month end-point assessment. The standard's typical duration is 24 months, and providers deliver it in different lengths (cambridgespark.com advertises 14 months, 2026-07-13), which tells you duration varies with how a provider structures delivery, not with the standard itself. Learning happens off-the-job during paid working hours: protected time, never "catch up at home."

Any start you plan now lands in the 2026-27 funding year (starts from 1 August 2026). How the levy pays for it:

• Levy-paying employer (pay bill over £3m). You draw on your apprenticeship service account, which covers training and EPA up to the funding band. The maximum government funding for ST1386 is £19,000 (Skills England). Confirm the live figure in the DWP apprenticeship funding rules before committing budget, as bands are revised periodically. If your account is exhausted, from 1 August 2026 you co-invest 25% and government pays 75%.
• Non-levy employer (pay bill under £3m). You don't pay the levy but the apprenticeship is still funded, through government co-investment (£0 for an apprentice under 25; 5% at 25+, with government paying 95%) or a levy transfer from a larger employer covering up to 100% of the cost. "We don't pay in" is not "we can't benefit."

Level 5 is unaffected by the Level 7 funding withdrawal, which only hits master's-level starts aged 22 and over. A note on the newer apprenticeship units (short, standalone training the levy can fund from 28 April 2026): apprenticeship units are a narrow stopgap, not a route to real engineering capability. The funding per unit is small and the format constrains depth. For genuine capability-building, a full apprenticeship is what does it. The employer funding page works through the routes for your situation.

Career outcomes and salary progression after completion

A Level 5 Data Engineer apprenticeship qualifies someone for data engineer roles and is a strong platform for progression toward senior engineering and, later, machine-learning engineering (a Level 6 standard, ST1398, exists). Data engineering is consistently among the better-paid data roles because the skills are scarce and the work is production-critical.

We won't quote a single salary figure, because pay varies widely by sector, region and stack, and a stale number does you no favours. Check a current, dated source such as the ONS ASHE tables or a live recruitment salary guide for the range that fits your market. As a shape: apprentices earn a real salary throughout (the apprentice National Minimum Wage is £8.00/hour from 1 April 2026, the legal floor rather than the going rate, and most data-engineering employers pay well above it); qualified data engineers command materially more, and experienced engineers more again. The durable signal isn't any one quarter's figure. It's the structural, growing demand for people who can make data usable.

How to compare providers before you shortlist

Sort by four things, in this order:

1. What will the learner actually be doing? If the answer is "watching lectures", stop. If it's "building pipelines on real data", continue.
2. Who coaches? People who've done the job, or people who teach the subject? Ask directly.
3. Does the role hold Level 5 work? Confirm with the line manager what tasks they'll assign, the check most shortlists skip.
4. What does it run on? It should be ST1386, at Level 5. Then, and only then, fit the funding to it.

Notice funding comes last. "Is it free?" is the wrong first question. Decide the outcome first (what you want this person to be able to do, and how you'll measure it), then judge every route as if you were paying cash, and only then work out the funding. A funded course that doesn't change what someone can do is the most expensive training there is, because it spends the one resource you can't get back: working time.

Why the delivery model decides the outcome

Here's the position we'll stake plainly: capability, not technology, is the bottleneck, and delivery model is where capability is won or lost. The evidence is stark. MIT's NANDA initiative found 95% of GenAI pilots delivered no measurable P&L return despite $30 to 40bn of enterprise investment, naming learning, not infrastructure, as the core barrier ("The GenAI Divide", fieldwork Jan to Jun 2025). RAND found more than 80% of AI projects fail, twice the rate of non-AI IT projects, the top root cause being a misunderstanding of the problem to be solved (RAND RRA2680-1, August 2024). Neither is a tooling story. Both are capability stories.

That capability gap explains why the format matters, not just the provider. A bootcamp or short course can transfer knowledge; it can't transfer the habit of applying it under real operational pressure, on real systems, over months. The apprenticeship model forces that repetition: off-the-job time is protected working time, not a side project. The EPA then certifies the output, not the attendance. That is why the delivery model isn't a differentiator between providers alone. It's the structural reason the apprenticeship format outperforms shorter interventions for production-grade capability.

So when you apply the four comparison criteria above, delivery model is the thing they're all testing for. Lectures and theory-first modules produce people who can describe a data pipeline. Building real pipelines, coached by people who've done the job, produces people who can build one. We build the second kind, coached by practitioners rather than academics, because the "doing" is the method, not a preference.

FAQ

What level is the Data Engineer apprenticeship?

The Data Engineer apprenticeship is Level 5, run on the Skills England-approved standard ST1386. Level 5 sits above A-level and below a full bachelor's degree: technical engineering work, a step beyond the Level 4 Data Analyst role.

How long does the Level 5 Data Engineer apprenticeship take?

The standard's typical duration is 24 months. iO-Sphere delivers it in 15 months of training plus a 3-month end-point assessment. Other providers advertise shorter timelines (cambridgespark.com lists 14 months, 2026-07-13), so duration depends on how a provider structures delivery.

What are the entry requirements?

Entry requirements are set by the provider rather than the standard, since Skills England publishes none for ST1386. Typically you need a Level 3 qualification in a relevant area in any grade: two A levels in a similar subject, a Level 3 apprenticeship, or a BTEC Extended Diploma, or equivalent such as working programming experience (for example Python) or 2 to 3 years in a related role. A degree isn't required, but genuine technical grounding is. Apprentices also need English and maths to Level 2, though for those aged 19+ that exit requirement has been optional since 11 February 2025.

How is the Level 5 Data Engineer apprenticeship funded?

The maximum government funding for ST1386 is £19,000 (Skills England); confirm the live figure before budgeting, as bands are revised. Funding runs through the apprenticeship levy. A levy-paying employer (pay bill over £3m) draws on their apprenticeship service account; from 1 August 2026, if the account is exhausted, they co-invest 25% and government pays 75%. A non-levy employer (pay bill under £3m) pays 5% under co-investment, or £0 if a larger employer transfers levy funds covering the cost.

Is there an exam?

No written exam. The end-point assessment has two methods, both built on the apprentice's real work: a project evaluation report with a presentation and questions, and a professional discussion. Each is graded fail, pass or distinction, and together they give an overall grade of fail, pass, merit or distinction (ST1386 assessment plan, Skills England). It is delivered by an independent assessment organisation. You're assessed on what you can build, not on recall under a clock.

Should I pick Level 5, or a lower level?

Pick the level whose work genuinely exists in the role now. Level 5 fits if the role involves at least two of: owning a production pipeline end-to-end, operating a data storage or processing platform, maintaining transformation logic in Python or SQL at a scale that breaks naive approaches, or mentoring others on data infrastructure. It does not fit if the outputs are reports, dashboards or ad-hoc queries, however sophisticated: those are downstream of the engineering, not the engineering itself. The error employers make most is treating a technically fluent analyst as a data engineer. They are different jobs, and the apprenticeship certifies the second. If the role's outputs are analytical, the Level 4 Data Analyst standard (ST0118) is the right fit; if it's foundational data-handling, look at Level 3.

Can an existing employee do the Level 5 Data Engineer apprenticeship?

Yes. Existing employees are among the most effective uses of this route. If someone is already doing parts of data-engineering work but lacks the formal grounding, the apprenticeship formalises and deepens what they can do on real systems they already know. The eligibility rules are the same: Level 3 prior qualification or equivalent experience, English and maths to Level 2 (optional exit for those aged 19+ since February 2025), and a role that genuinely contains Level 5 engineering work.

If the Level 5 work genuinely lives in the role, the next step is a conversation about what your team will build, not a brochure. Explore our Level 5 Data Engineering apprenticeship or talk to us about whether it's the right level for the work you have. →