How you’d get it

How you’d get this certificate

  1. Zavmo teaches you. You learn the units one-to-one with an AI tutor, on your own work.
  2. You register with an approved centre. That is a college, training provider or employer NCFE has approved to offer this qualification. Zavmo is not an approved centre, so you register with them, not with us.
  3. The centre assesses, and NCFE awards. A qualified assessor at the centre judges your evidence, and the certificate comes from NCFE.

More on studying for a qualification

01What it is

The Level 5 Diploma: Data Engineer is designed to give learners the knowledge and associated skills and behaviours required to work in roles relating to data engineering. It will also prepare learners to progress to further study in this area.

These are the units NCFE registers against this qualification. It is a catalogue, not a syllabus. Which of them you take depends on the combination the qualification requires, and that is set by the awarding body rather than by us. Every unit here is regulated. Zavmo teaches towards them on your own work, and work done here is recognised as prior learning under the agreements we hold.

Zavmo is not an awarding body, is not an approved centre, and is not affiliated with NCFE. It does the teaching and the mapping. NCFE sets this qualification and awards it, and a qualified human assessor makes the assessment decision.

Free first step

Try a free Future Fluency lesson first

The free part is a Future Fluency lesson on using AI at work. It is not part of this qualification. Next, a free account. We build your plan for this qualification as you set up. Teaching towards this qualification begins when you subscribe.

No card · Nothing to commit to

02The units

What each unit actually teaches you to do

Data architecture and management Real unit · NCFE
This unit covers the exploration and analysis of risks associated with data collection and usage, frameworks for data quality, and principles of data warehousing. You'll learn to create data products compliant with regulatory requirements and analyse the impact of data quality on organisational operations.

What you'll be able to do

  • Explore and analyse the inherent risks of data collection and usage Knowledge: Risks associated with data collection: • privacy and security risks • non-compliance issues • ethical concerns • misuse of data • data quality issues: o incomplete data o inaccurate data o inconsistent data. The potential impact of poor data quality on organisations.
  • Explore frameworks for data quality and how contributing dimensions support reliability Knowledge: Components of data quality frameworks: • governance • profiling • quality dimensions: o accuracy o completeness o consistency o timeliness o accessibility o uniqueness • cleansing • validation • continuous monitoring and reporting: o validity. Features of common data quality frameworks (for example, DAMA UK, TDQM). How to resolve identified risks to ensure data quality and to mitigate against future issues. Skills: Monitor and analyse data quality metrics to meet operational requirements when processing data, considering: • quality • accuracy • reliability.
  • Develop a data product that complies with regulatory requirements Knowledge: Key considerations when developing a data product: • system design • compliance and metrics (for example, regulatory requirements) • resource requirements • scalability. Skills: Apply data product design methods to meet requirements: • collation of information and requirements • creating an entity relationship diagram (ERD) • testing and evaluation • refinements: o user requirements o business requirements: ▪ cost ▪ resourcing ▪ accessibility.
  • Explore the principles of data warehousing Knowledge: The features of the ETL (extract, transform, load) process, and their role in preparing data for analysis. How to use an ETL pipeline to connect disparate data sources to meet business requirements. Core principles of data warehousing: • Kimball’s dimensional data modelling • Inmon’s data warehouse model. The principles for design and implementation: • ETL process • schema design (for example, star, snowflake) • separation of operational and analytical systems • data quality and consistency • performance and scalability • security and access control. The role of data lakes, data warehouses and data marts in meeting business requirements. Skills: Manage data manipulation tasks, applying appropriate tools and techniques (for example, filtering, joining sorting), ensuring data integrity.
  • Analyse relevant policies and strategies to ensure business continuity when implementing data solutions Knowledge: Features of key business continuity strategies (for example, system monitoring and surveillance), and their role in ensuring organisational resilience and the recovery of important data and services. The role of policies to support business continuity and mitigate against negative impact in relation to data provision: • business continuity • data backup • disaster recovery • incident reporting. Skills: Apply shell script (for example, Bash) to monitor availability, log downtime, and communicate findings to stakeholders through automated messages.
Data engineering principles and foundations Real unit · NCFE
It teaches you to explore fundamental data principles and governance concepts. You'll describe key data principles, analyse external data sources, and evaluate data governance roles within organisations.

What you'll be able to do

  • Explore the principles of data Knowledge: Principles of data: • lawfulness, fairness, and transparency • purpose limitation • data minimisation • accuracy • storage limitation • integrity and confidentiality • accountability. Types of datasets: • open and public • administrative • research. Approaches to gaining data through research. The value of external data sources for enriching internal data. How direct data acquisition can enhance business operations.
  • Explore the concepts of data governance Knowledge: Appropriate legislation and how it is applied to the safe use of data: • UK General Data Protection Regulation (GDPR)/Data Protection Act 2018 • Digital Economy Act 2017 • Computer Misuse Act 1990. Considerations for regulatory requirements: • data and information security standards: o NIST o PCI DSS. The use of data governance frameworks (for example, government led (UK), industry recognised). Features of policies and procedures relating to data governance: • compliance with regulatory requirements • data privacy • data anonymisation • data ownership • data lineage • ethical usage • metadata • security • quality control: o completeness o timeliness o consistency. Skills: Apply data solutions to address common organisational requirements. Work collaboratively with appropriate stakeholders to meet requirements.
  • Explore and apply the principles of data normalisation and redundancy in relational databases Knowledge: Principles of data normalisation: • Codd’s 12 rules • normal form (NF): o 1NF – eliminating duplicate records o 2NF – eliminating partial dependencies o 3NF – eliminating transitive dependencies o BCNF (Boyce-Codd normal form) – a stricter version of 3NF o 4NF – removing multi-valued dependencies o 5NF – eliminating join dependencies. Features of relational database management systems (RDBMSs). Advantages of data normalisation to databases with regards to key concepts: • data protection • data redundancy • inconsistent dependency. Skills: Query, manipulate and organise data to meet requirements, using industry- standard tools and programming languages (for example, SQL and Python). Manage and implement database access controls to meet business requirements: • access levels (for example, resource, administrator) • types of access (for example, guest, standard) • access control methods (for example, MAC, RBAC). Implement automated validation checks.
  • Explore approaches to data integration Knowledge: Approaches to data integration: • manual integration • API (application programming interface) integration • third-party integrations • direct integration. How integration of disparate data sources supports business outcomes.
  • Explore the unique features and functions of different data formats Knowledge: Characteristics of different data formats. Data formats: • structured • semi-structured • unstructured. How different data formats can be stored: • data stores: o relational database (SQL) o non-relational database (NoSQL) • distributed systems: o distributed file systems (for example, Apache Hadoop, Amazon S3) o distributed database o distributed NoSQL o distributed object storage. Skills: Apply a range of data storage solutions and distributed file systems to implement a system that meets specified requirements. Use data systems securely to meet requirements, in compliance with relevant legislation, policies and procedures.
  • Explore common data development frameworks and architectures Knowledge: Processes involved in developing the data product to function within the organisation. Characteristics of common architectures: • cloud • on-premises • monolithic • modular. Features and uses of common frameworks (for example, Apache Spark, DBT, Apache Airflow).
Data pipelines and automation Real unit · NCFE
You'll explore various approaches to data handling and storage, data transfer applications, and deployment methods for data pipelines and automation. They will gain the ability to apply data ingestion frameworks and critically analyse cloud migration strategies and data engineering tools.

What you'll be able to do

  • Explore approaches used for handling and storing data Knowledge: The considerations and use of data handling and storage approaches. Considerations: • relational and non-relational storage • cloud and on-premises solutions • structured versus unstructured data handling. Handling approaches: • ETL (extract, transform, load) • ELT (extract, load, transform) • API (application programming interface)-based transfer • manual transfer. Storage approaches: • data warehousing • data lakes • cloud storage and backups • archive and retention. Processes and considerations involved in supporting the movement of data during cloud migration: • migration planning • data transfer methods • tools and platforms • security and compliance • testing. The considerations of different data transfer methods (for example, batch, streaming, on-demand) to meet business requirements.
  • Explore the application of data transfer from one location to another Knowledge: Features and use cases of data ingestion frameworks (for example, Apache NiFi). Different data ingestion modes (batch, streaming, and on-demand) and their application for data processing. Appropriate tools and technologies used for streaming, batching, and on- demand data transfer between systems (for example, Apache Kafka, ETL platforms, REST APIs). The 7 Rs of cloud migration as a strategy for moving applications and data to the cloud. Types and implementation of migration strategies (for example, big bang, trickle, zero downtime) to meet requirements. Skills: Use different techniques to optimise data ingestion processes using appropriate data ingestion frameworks: • batch • streaming • on-demand.
  • Explore deployment methods for data pipelines and automated processes Knowledge: Functions and features of pipeline deployment methods (for example, manual, scheduled, serverless) to ensure data flows reliably, securely, and efficiently. How version control and rollback planning are critical in data pipeline development and deployment: • collaboration • tracking • automated testing • recover from failure. Techniques and tools to effectively identify and troubleshoot issues within data processing pipelines: • monitoring and logging tools (for example, AWS CloudWatch) • debugging methodologies (for example, unit testing) • performance tuning techniques (for example, parallel processing). Skills: Apply appropriate techniques and tools to identify and troubleshoot issues with data processing pipelines.
  • Explore the types and uses of common data engineering tools and applications Knowledge: Features and application of data engineering tools used to design, build, manage, and optimise data pipelines and infrastructure: • data ingestion tools (for example, Apache NiFi) • data transformation tools (for example, Talend) • data storage tools (for example, Snowflake) • orchestration and workflow management tools (for example, Prefect) • data monitoring (for example, Monte Carlo). Common programming languages used in data engineering: • Python • SQL • Scala • Java • Bash/Shell • R • Golang. The role of YAML as a configuration and metadata format in data engineering. How data engineering tools, programming languages, and configuration formats are applied within an organisation to design, build, automate, and manage data pipelines and infrastructure. Skills: Automate batch, real-time, and on-demand data pipelines utilising programming languages and data integration platforms with graphical user interfaces or infrastructure-as-code tools. Develop and apply appropriate processes and algorithms to support extraction of structured data from unstructured data.
Software development for data products Real unit · NCFE
This unit introduces the principles of software development for data products, including costing and building systems aligned with organisational sustainability. You'll produce technical documentation and explore technology and service management relevant to data products, as well as evaluation processes.

What you'll be able to do

  • Explore the principles of software development for data products Knowledge: The principles of software development and how to apply them to data products: • version control • designing for modularity, reusability, and maintainability • code readability and documentation • debugging, logging, and traceability • automated testing and CI/CD (continuous integration/continuous deployment) • privacy by design. The role of development (DEV), staging (STG), and production (PRD) environments, and how each supports the software development lifecycle. The use of best practice approaches (for example, DRY) to enhance code quality, reusability, and testability within data-centric environments. Skills: Produce and maintain technical documentation for the data product containing the required technical and non-technical information for stakeholders. Contribute to and apply best practice approaches in software development principles when working with stakeholders.
  • Analyse how to cost and build a system to align with organisational sustainability responsibilities Knowledge: Considerations when costing a system build: • requirements analysis (for example, features) • materials (for example, hardware, software) • staffing and operational costs (for example, development) • cost estimation methods (for example, return on investment (ROI)) • cloud versus on-premises. Factors to consider when undertaking and implementing a system build: • architecture design (for example, modular) • technologies (for example, cloud services) • development environment (for example, CI/CD) • testing. How system design and implementation decisions can be aligned with organisational sustainability strategies (for example, E-waste reduction). Skills: Design a secure data product to meet business and user requirements.
  • Explore the appropriate use of technology and service management in relation to data products Knowledge: How configuration management practices maintain accurate and up-to-date information on IT assets and systems to support effective service delivery and change control. The role and use of change management processes to control, assess, and authorise system modifications. Techniques to manage and respond to IT incidents by prioritising, diagnosing, and resolving service disruptions. How industry-standard tools (for example, service desk) support service management activities. How service management practices align with recognised frameworks and standards. Skills: Review use and configuration of existing tools and techniques to identify potential implementation issues to support business change or transitions.
  • Explore the processes for evaluating and implementing prototypes within a production environment Knowledge: How to evaluate prototypes against defined criteria (for example, functionality, usability) to determine readiness for implementation. Developmental process to refine prototypes into production-ready solutions. How release strategies (for example, phased) are used to support the effective implementation of prototypes. Skills: Evaluate prototype data products by assessing their cost–benefit value, compatibility with organisational data infrastructure, and the availability of open-source tools and online support.
  • Explore the lifecycle of implementing data solutions within a business Knowledge: Processes involved in the lifecycle of implementing data solutions within a business: • ensure that data solutions are scoped accurately and align with business objectives, with consideration for: o business context o stakeholder needs o success criteria • evaluation of prototype data solutions to test feasibility, validate technical approaches, and gather feedback to inform further development • the building and integration of data pipelines, models, and interfaces in line with design specifications • completion of testing and implementation of production deployment strategies • evaluation and monitoring of the performance of implemented data solutions. Skills: Review and monitor the health and performance of data systems (for example, identifying technical debt) as part of continuous improvement.
03The standards

The national standards these units are built against

What the job actually needs, in the words employers and awarding bodies already use for the work itself.

  • Cleanse Data to Resolve Quality Issues

    Standard
  • Design Data Processing Systems

    Standard
  • Develop algorithms and pipelines for the analysis of life science data

    Standard
04Where it leads

The jobs these credits are mapped to

A qualification is never a dead end here. Each of these is a job record this qualification is a mapped route into.

Showing 6 roles, drawn from 187 job records mapped to this qualification. Near-identical records are folded together, and each row says how many it stands for.

Where this can lead

Associate Data Engineer

This role gives a grounding in data engineering. From here, the path can lead to Senior Data Engineer, Staff Data Engineer, or Data Engineering Manager.

See the whole journey
05The credits

The credits, and who awards them

Level 5 credits are regulated, and they are awarded by NCFE rather than by Zavmo. They don’t vanish when a subscription ends or a website closes. They travel to any employer, and Zavmo keeps the map of what you have covered and what is next.

What you would be collecting

Data architecture and managementData engineering principles and foundationsData pipelines and automationSoftware development for data products

Each one is a real unit registered against this qualification.

How you’d practise it

You don’t watch this. You do it.

You are not assessed on remembering this. You are assessed on applying it, analysing it, evaluating it and producing something. So that is what the practice is: projects, role play and your own live cases, with a tutor in the room.

The Analyst The Analyst · your map-it-properly tutor Illustration
The Analyst In “Data architecture and management” you have moved the target from 48 hours to 24. Where does that time come from?
You The team prioritises better, I suppose.
The Analyst Or it comes out of the follow-ups, and reopened cases climb in about six weeks. Let us map it and find out which, before it is a surprise.
The same lesson on the real thing: the conversation in the middle, the thinking ladder on the left, and the criteria each answer is evidencing on the right.
  • Map a live decision Analyse

    “Data architecture and management” runs on a decision you are facing now. Zavmo maps it with you and shows what the second-order effect looks like before you find out the slow way.

What you leave holding

The standards this credential builds, in the shape the product keeps them

Nothing here is marked learned. There is no learner on a public page, so the map shows what the qualification covers rather than what anybody has done.

See Your Progress Grow Illustration
NCFE Level 5 Diploma: Data Engineer
  • Cleanse Data to Resolve Quality Issues
  • Design Data Processing Systems
  • Develop algorithms and pipelines for the analysis of life science data
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Data architecture and management, one of this qualification's own units.

Data architecture and management Level 5

Applied to your work in any of these jobs

This unit covers the exploration and analysis of risks associated with data collection and usage, frameworks for data quality, and principles of data warehousing. Learners will develop skills to create data products compliant with regulatory requirements and analyse the impact of data quality on organisational operations.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time. Teaching towards this qualification begins when you subscribe.

Your Plan Illustration

Built for NCFE Level 5 Diploma: Data Engineer

4 units in this credential, in the order it lists them, awarded by NCFE.

  1. Data architecture and management
  2. Data engineering principles and foundations
  3. Data pipelines and automation
  4. Software development for data products
These are the real units of this credential, in its own order. Nothing here is marked done, because this plan has not been started by anyone yet. Yours would fill in as you go.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Learned on your own work, taught one-to-one.

Everything you just read, learned one-to-one on the job you already do. Your free first module is Future Fluency, so you can see how the teaching works before you pay for anything.

Build my plan, free

No card. See how this qualification maps onto your role and meet the tutors who’d teach it, free. The learning begins when you subscribe. It’s £70 a month, billed monthly. Cancel any time and billing stops.

The title, level, credits, guided learning hours and unit learning outcomes on this page are taken from the Ofqual Register of Regulated Qualifications. Contains public sector information licensed under the Open Government Licence v3.0. Where this data comes from.