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
Director of Cloud Operations / Head of SRE (Large Enterprise)
5-10 yearsSkills to master
- Mastering multi-team management, setting departmental strategy, managing significant budgets (multi-million £), driving large-scale reliability initiatives, and building strong relationships with C-suite peers.
You're ready to move on when
- Successfully led a major cloud migration or infrastructure transformation programme.
- Consistently achieved high SLOs for critical services under your purview.
- Built and retained a high-performing leadership team within your department.
- Demonstrated strong financial acumen in managing cloud spend and negotiating vendor contracts.
- 2
CTO / VP of Engineering (Mid-Sized / Scale-Up Company)
3-7 yearsSkills to master
- Broadening scope beyond just operations to include product engineering, architectural oversight, investor relations, and full P&L accountability for the entire technology function. This path often means gaining experience with broader business strategy.
You're ready to move on when
- Successfully scaled a technology organisation through rapid growth phases.
- Developed and executed a comprehensive technology strategy that directly enabled business growth.
- Effectively managed investor expectations and presented technology vision to external stakeholders.
- Demonstrated ability to attract and retain top engineering talent across multiple disciplines.
- 3
Principal / Distinguished Engineer (Large Enterprise)
7-12 yearsSkills to master
- While not a direct management path, a Principal Engineer who has driven enterprise-wide architectural standards, influenced strategic technical decisions, and mentored numerous technical leaders can transition into a VP role if they also develop strong organisational leadership and P&L management skills.
You're ready to move on when
- Architected and overseen the implementation of multiple mission-critical, enterprise-scale systems.
- Recognised as an industry expert, influencing technical direction across multiple organisations.
- Demonstrated ability to lead through influence without direct authority, shaping technical culture and best practices.
- Developed strong business acumen and understanding of the financial impact of technical decisions.