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
Mid-level Systems/Network Engineer
2-3 years at mid-levelSkills to master
- Independent ownership of specific systems, strong troubleshooting skills across multiple layers, basic automation scripting, and a solid understanding of core cloud concepts.
You're ready to move on when
- You're consistently solving problems that stump your peers.
- You're the informal go-to person for a specific technology.
- You've successfully delivered 2-3 small to medium-sized projects end-to-end.
- You're actively mentoring new joiners or less experienced colleagues.
- 2
Cloud Engineer / DevOps Engineer
2-4 years in a dedicated cloud/DevOps roleSkills to master
- Deep expertise in a specific cloud provider, strong IaC skills, CI/CD pipeline management, and a good understanding of containerisation and microservices architecture.
You're ready to move on when
- You've designed and deployed complex applications on a cloud platform.
- You're writing production-grade Terraform/Ansible code.
- You're comfortable with Kubernetes and its ecosystem.
- You're advocating for automation and 'shift-left' security practices.
- 3
Specialist Technical Consultant (Infrastructure focus)
3-5 years in consultingSkills to master
- Broad exposure to various client environments, strong problem-solving under pressure, excellent client communication, and the ability to quickly grasp new technologies and business contexts.
You're ready to move on when
- You've led technical engagements and delivered solutions for multiple clients.
- You can quickly diagnose and propose solutions for diverse infrastructure challenges.
- You're adept at translating business needs into technical requirements.
- You're looking for a role with deeper, long-term ownership of infrastructure.