The pathway
How you actually get there, here
How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.
- 1
Principal Database Engineer / Staff Database Engineer
3-5 years as a Principal/Staff EngineerSkills to master
- Deep technical leadership, cross-functional influence without direct authority, solving the hardest technical problems, setting technical standards, mentoring senior engineers.
You're ready to move on when
- You've successfully architected and delivered multiple large-scale data platform components.
- You're the go-to person for complex technical challenges that no one else can solve.
- You've consistently influenced technical direction across multiple teams or departments.
- You've informally mentored and developed other senior engineers.
- 2
Head of Data Engineering / Database Development Manager (L5)
3-5 years as a Head of/ManagerSkills to master
- People leadership, budget management (up to £500K-£2M), organisational design, strategic planning for a department, stakeholder management at a senior level.
You're ready to move on when
- You've successfully built and led a high-performing team of 10-25 data professionals.
- You've owned and managed a significant departmental budget, delivering projects on time and within cost.
- You've consistently met or exceeded departmental KPIs and objectives.
- You're adept at managing upwards and sideways, getting buy-in for your team's initiatives.
- 3
Director of Engineering (with a strong data background)
2-4 years as a Director of EngineeringSkills to master
- Broader engineering leadership (beyond just data), managing multiple disparate teams, understanding full-stack implications, strategic resource allocation across diverse technical domains.
You're ready to move on when
- You've led multiple engineering teams (not just data) to deliver complex software products.
- You have a strong understanding of the full software development lifecycle and its various specialisms.
- You're comfortable making trade-offs between different technical priorities (e.g., front-end vs. back-end vs. data).
- You've demonstrated the ability to scale engineering organisations and processes.