Platform / DevOps Engineer → SRE
Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.
Practitioner-authored route. The evidence and review status below explain its limits. Timing depends on your starting experience and access to relevant work.
Where senior cloud and DevOps people end up when they want to be treated as engineers, not as ticket-takers. Highest ceiling in this list, but almost never an entry role.
You write code comfortably, you've owned production systems, and you find the idea of building an internal developer platform genuinely interesting rather than just a job title.
You want to get there in two years from a helpdesk seat. The job assumes years of coding plus years of running infrastructure, and there's no real shortcut.
Phased progression
Foundations → first role → specialisation → advanced. The realistic order, not a script.
Salary figures are UK base-pay practitioner estimates, not survey data. The stages cover different roles and responsibility levels; time alone does not earn the next salary band.
- 010–6 monthsFoundations
Build literacy and lab habits. These are study options, not mandatory exams; choose the platform relevant to your target work.
CKADCKS - 0212–24 months from cloud or backendFirst paid role
Land a Junior DevOps / SRE. Operational time, not more certs, earns the next move.
Junior DevOps / SRE£50–70k junior DevOps - 031.5–3 yearsSpecialisation
Add a specialist credential aligned to the work you're already doing.
AWS Solutions Architect AssociateTerraform Associate£75–105k mid - 043+ yearsAdvanced
Move into adjacent roles. Long-term credentials become worth their cost.
SRE£110–145k senior platform / SRE (UK)
- 01Foundations0–6 months
Build literacy and lab habits. These are study options, not mandatory exams; choose the platform relevant to your target work.
CKADCKS - 02First paid role12–24 months from cloud or backend
Land a Junior DevOps / SRE. Operational time, not more certs, earns the next move.
Junior DevOps / SRE£50–70k junior DevOps - 03Specialisation1.5–3 years
Add a specialist credential aligned to the work you're already doing.
AWS Solutions Architect AssociateTerraform Associate£75–105k mid - 04Advanced3+ years
Move into adjacent roles. Long-term credentials become worth their cost.
SRE£110–145k senior platform / SRE (UK)
Certification sequence
Ordered by realistic relevance, not vendor marketing.
Practical projects
What to actually build, the portfolio that opens interviews.
- Self-hosted CI with GitHub Actions runners
- GitOps with ArgoCD on a homelab cluster
- SLO dashboards in Grafana with synthetic checks
- ·Cloud-first then add automation
- ·Backend dev then add ops
Realistic expectations
What no recruiter will tell you.
That it's just DevOps with a new label. Platform engineering is product work. You're building tools other engineers depend on, with a roadmap, users and feedback loops.
Twelve to twenty-four months from a strong cloud or backend role. Cold entry isn't really a thing here, and the postings that say otherwise are usually mis-titled SRE roles.
What this is based on
Practitioner judgement. External evidence review pending.
Last reviewed: not yet reviewed · UK market
Where this fits
A pathway is a sequence, not a destination. Here are the roles and certs along it.
- Cloud Engineer → Cloud Architect
A broad infrastructure track combining networking, Linux, cloud and infrastructure as code.
- Cloud Security Engineer
Cloud-native IAM, workload security, policy-as-code. Entered from cloud, not from SOC.
- Software Engineer (Backend / Full-stack)
Ship product, own services. Portfolio matters more than certs.
- Cloud engineering isn't entry-level anymore
In progress. The market that hired junior cloud engineers in 2019 doesn't exist. What replaced it, and the realistic path in.
- DevOps vs platform engineering. What actually changed
In progress. It isn't a rename. The hiring bar, day-to-day, and career ceiling are all different. Most candidates pick the wrong one.
The next step
The pathway is plausible. Whether it holds for five years is a different question.
A Career Verdict applies the framework to your actual stage and stack: what holds, what breaks, what would change the call.
A route shows what is possible. A Career Verdict makes the call.
Career Verdict
Helpdesk → Security Architect
- 01The callA clear judgement on whether your route is realistic, and under what conditions.
- 02Where the route breaksThe most likely point to stall, and why it happens in practice.
- 03What to do nextSpecific priorities for the next 6–24 months, and what to drop.
Career Verdict
- The callA single written judgement on whether the route is realistic for you.
- Plateaus and failure modesThe flat years and the specific ways this route tends to stall.
- Where you standThe strongest and weakest parts of your current position, named.
- Salary realityWhat this route actually pays, set against what you've been told it pays.
Usually within minutes of payment. Kept 24 months, then deleted. Deletion on request at any time.
Built on TechWaymark's practitioner-authored assessment framework, informed by two decades across helpdesk, infrastructure and security. The verdict applies that framework to your inputs.