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
From Senior IT Systems Engineer (L3)
Roughly 4-7 years at L3/L4 level.Skills to master
- Transitioning from deep technical expertise to broader team leadership, budget management, and strategic vendor negotiation. You'll need to prove you can delegate effectively and manage through others.
You're ready to move on when
- Successfully led multiple complex IT projects end-to-end, demonstrating strong project ownership.
- Consistently mentored junior team members, showing a knack for developing talent.
- Proactively identified and proposed solutions for systemic IT issues, not just individual problems.
- Demonstrated ability to communicate technical concepts to non-technical audiences effectively.
- 2
From IT Infrastructure Lead / Staff Engineer (L4)
Around 2-4 years at L4 level.Skills to master
- Moving from architecting solutions and leading technical domains to full people management, budget accountability, and influencing at a more senior, cross-functional level. This path requires a shift from technical 'doing' to strategic 'directing'.
You're ready to move on when
- Defined technical strategy for a specific domain (e.g., cloud, networking) and successfully implemented it.
- Managed small project budgets (e.g., £50K-£100K) with good oversight.
- Demonstrated strong influence with peer leads and senior stakeholders on technical direction.
- Acted as an informal leader or mentor for a small group of engineers.
- 3
From IT Project Manager (with strong technical background)
Roughly 5-8 years in project management, plus prior technical roles.Skills to master
- Adding direct people management, operational ownership, and deep technical governance to your project management expertise. You'll need to prove you can move beyond project timelines to ongoing service delivery and team development.
You're ready to move on when
- Managed complex IT projects involving infrastructure or operations teams.
- Demonstrated a strong understanding of technical risks and dependencies.
- Built effective relationships with technical teams and senior IT leadership.
- Showed initiative in understanding the 'why' behind projects, not just the 'what'.