Structured learning pathways for data engineers - from graduate through to data architect. Each pathway maps the skills, behaviours, reading, and hands-on projects that drive progression.
Data Engineering Pathways
Graduate Data Engineer → Junior Data Engineer
Graduate Data Engineer to Junior Data Engineer
9-18 monthsBuild the foundational data engineering skills and professional habits that allow you to deliver well-scoped data work independently and reliably.
🧠 AI for learning SQL patterns and data debugging View Pathway →Junior Data Engineer → Intermediate Data Engineer
Junior Data Engineer to Intermediate Data Engineer
12-24 monthsDesign and own complete data pipelines independently, build data quality frameworks, and begin understanding how data flows and is governed across the wider platform.
🧠 AI for pipeline code generation and data quality reasoning View Pathway →Intermediate Data Engineer → Senior Data Engineer
Intermediate Data Engineer to Senior Data Engineer
18-36 monthsLead the technical direction of the data platform, own data quality and reliability end-to-end, mentor your team, and begin shaping data strategy.
🧠 AI for data platform intelligence and governance View Pathway →Senior Data Engineer → Data Architect
Senior Data Engineer to Data Architect
24-48 monthsDevelop organisation-wide data architecture authority by mastering lakehouse design at scale, data governance, technology strategy, and the credibility to make hard data architecture decisions stick.
🧠 AI as a data platform component and governance challenge View Pathway →Shared Leadership Pathways
Lead Engineer → Technical Team Lead
Lead Engineer to Technical Team Lead
12-24 monthsMake the shift from technical authority to people leadership - running a high-performing team while remaining a credible technical voice, and learning that your primary leverage is through others.
🧠 AI in team processes and responsible adoption leadership View Pathway →Technical Team Lead → Engineering Manager
Technical Team Lead to Engineering Manager
12-24 monthsMove from hands-on technical leadership to full people management - your job is no longer to be the best engineer in the room but to create the conditions where engineers can do their best work.
🧠 AI tool strategy, team adoption, and ethical leadership View Pathway →Engineering Manager → Head of Engineering
Engineering Manager to Head of Engineering
24-48 monthsMove from managing a team to leading an engineering organisation - setting conditions for multiple teams to perform, shaping technical culture and strategy, and operating credibly with executive stakeholders.
🧠 AI strategy, ethics, organisational adoption, and responsible leadership View Pathway →Architect → Head of Engineering
Architect to Head of Engineering
24-48 monthsA rare and demanding transition - from deep technical authority to broad organisational leadership. Architects who make it to HoE do so by developing the people leadership, commercial awareness, and organisational design capability to match their existing technical credibility.
🧠 AI governance and organisational AI capability View Pathway →Head of Engineering → VP of Engineering
Head of Engineering to VP of Engineering
24-48 monthsThe transition to VP is as much about organisational influence and executive presence as it is about engineering excellence. You move from owning the engineering function to co-owning the company's technology strategy at board level.
🧠 AI as a strategic and organisational capability View Pathway →