Data Engineer → Data Architect

A realistic transition from Data Engineer to Data Architect: transferable skills, the gaps to close, a step-by-step learning plan and alternative routes. Estimated skill overlap 60%. Difficulty: Medium.

Difficulty: Medium6 stepsDuration: 9 to 13 monthsOverlap: 60%

Transition from Data Engineer to Data Architect.

Transferable skills

  • Data architecture
  • Data modelling
  • Data warehousing
  • Data governance
  • Big data platforms

Skills to learn

  • Pipelines & ETL/ELT
  • Documentation
  • Mentoring

Step-by-step learning plan

  1. 1. Build on your Data Engineer experience

    2–4 weeks

    Leverage

    • Data architecture
    • Data modelling
    • Data warehousing
    • Data governance

    Map transferable skills — Data architecture, Data modelling, Data warehousing — against what a Data Architect needs.

  2. 2. Learn the core of the Data Architect role

    6–10 weeks

    Learn

    • Pipelines & ETL/ELT
    • Documentation

    Technologies

    DatabricksS3Azure Data Lake

    Cover the biggest gaps first: Pipelines & ETL/ELT, Documentation.

  3. 3. Master advanced Data Architect skills

    6–10 weeks

    Learn

    • Mentoring

    Technologies

    Power BITableauGitHub

    Handle the advanced topics: Mentoring.

  4. 4. Get productive with the Data Architect toolchain

    4–8 weeks

    Technologies

    DatabricksS3Azure Data LakePower BITableauGitHub

    Be hands-on with Databricks, S3, Azure Data Lake and the rest of the target stack.

  5. 5. Practise Data Architect work in real conditions

    4–8 weeks

    Ship a portfolio project or take on Data Architect tasks at work.

  6. 6. Get certified and position yourself as a Data Architect

    4–8 weeks

    Technologies

    Google Cloud Professional Data EngineerDatabricks Certified Data EngineerTOGAF 9 Foundation

    Update your CV and LinkedIn around Data Architect, then apply to target roles.

Alternative routes