Skip to main content
A data analyst and colleague examine printed charts and a data-quality worksheet
Data & ML

Data Engineer / Applied AI

Data engineering makes data movement, contracts and recovery dependable.

Explore the work, check your starting point and try one scoped task before committing to a course or exam.

Try this pathway in practice

The route

From Data Analyst to Data Engineer

  1. Starting roleData AnalystRead the broader role guide
  2. Target roleData Engineer

A general route, not a personal plan. Linked guides describe the broader role family; a junior or support starting point may have a narrower remit. Compare the responsibilities with the actual vacancy.

Phased progression

Build on your existing experience, demonstrate the next responsibility and review it with the people who rely on your work.

Progress through demonstrated capability and agreed responsibility. These stages are not a fixed timetable or a salary ladder.

  1. Build on existing experience

    Your starting capability

    Practical focus

    Review your existing work against Data Analyst → Data Engineer responsibilities. Identify one gap in judgement, delivery or ownership and agree a scoped way to demonstrate it.

    Something to demonstrate

    A short account of what you can already do and the next gap to investigate.

    In focus AI-901

  2. Demonstrate readiness

    Move into the specialism

    Practical focus

    Explore Data Analyst → Data Engineer responsibilities. Check the supervision and prior experience expected; demonstrate the relevant work before increasing your scope.

    Something to demonstrate

    A data dictionary, validation report and reproducible pipeline; for AI, include baseline comparisons and failure examples.

    In focus Data Analyst → Data Engineer

  3. Demonstrate reliable practice

    Specialisation

    Practical focus

    Take on a scoped responsibility, test your decisions and collect feedback. Add a credential only where it supports that work.

    Something to demonstrate

    A test record and feedback showing how you improved a piece of work.

    In focus DP-700

  4. Broaden responsibility

    Deepen, lead or move sideways

    Practical focus

    Data Platform Lead or Applied AI Lead. Own the model-and-pipeline contract for a product line.

    Something to demonstrate

    Examples of broader ownership, with the scope and responsibility agreed.

The work itself

What you would spend time doing

Data engineering builds dependable data flows; applied AI evaluates model behaviour in a product. Choose which responsibility interests you before selecting tools or study.

Your starting point

What to bring to this route

For data work, practise SQL, data quality and repeatable transformations. For applied AI, add evaluation and failure analysis; a convincing demonstration is not enough to establish reliability.

Ask a course provider or employerDoes this role own pipelines, model evaluation or both, and who monitors quality after release?

The verdict

You enjoy data infrastructure, reliability and observability. You can write maintainable Python or SQL, not just scripts.

A pipeline can finish successfully while producing the wrong result. Ask about schema ownership, backfills, reconciliation and downstream consumers.

Certification sequence

Study options, not a checklist. Choose for the work you need to demonstrate, then check the provider’s current requirements and renewal terms.

Primary

Explore these first

Compare the subject with the work you want to do. Check eligibility before committing.

Long-term

As your responsibility grows

Revisit when your scope changes. Experience and renewal requirements still apply.

No specific credential suggested at this stage.

Practical projects

Produce something you can explain, test and improve with feedback.

A scoped starting exercise

Try the work before choosing the route

Use a small synthetic dataset with missing, duplicate and invalid records. Build a repeatable cleaning step. If exploring AI, add a separate labelled evaluation set and compare a simple baseline.

What to keepA data dictionary, validation report and reproducible pipeline; for AI, include baseline comparisons and failure examples.

Free text worksheet · no account needed. Add your checks, results and feedback as you work.

Review the evidence

  1. Do checks detect bad inputs and explain what was rejected or changed?
  2. Could another person reproduce the results, and have you avoided overstating performance beyond the tested data?

Label planned, simulated and completed work accurately. A practice exercise helps you test your interest and reasoning; it does not establish production experience or guarantee an interview.

Larger portfolio ideas for later

Choose one once you have the foundations and permissions it needs. Scope it to a task you can test and explain.

  • Build a small dbt project on Snowflake or DuckDB
  • Author an end-to-end pipeline (Airflow or Dagster) with tests
  • Ship a RAG demo with eval + observability, not just a notebook

Use synthetic or approved information. Keep employer, customer and account details out of public examples.

Analytics EngineerML EngineerMLOpsApplied AI EngineerBackend Engineer
  • ·Analytics-engineering-first via SQL
  • ·ML via research background

Realistic expectations

Check these assumptions against the course, vacancy or team you are considering.

Misconception

That a title or credential establishes readiness by itself. Distinguish analysis, data engineering, modelling and model operation.

Readiness check

Distinguish analysis, data engineering, modelling and model operation. Each asks for different evidence; a single AI label or course duration cannot establish readiness for all four.

Editorial route and career guidance. No separate external evidence review is recorded for this assessment.

Editorial evidence review: pending · UK market. Vendor facts and prices elsewhere on this page have their own sources and check dates.