Platform / DevOps Engineer → SRE
Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.
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.
- 010–6 monthsFoundations
Literacy, lab habits, the cert that opens first conversations.
AWS Solutions Architect Associate - 026–18 monthsFirst 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.
Terraform AssociateCKAD£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
Literacy, lab habits, the cert that opens first conversations.
AWS Solutions Architect Associate - 02First paid role6–18 months
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.
Terraform AssociateCKAD£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.
Where this fits
A pathway is a sequence, not a destination. Here are the roles and certs along it.
- Cloud Engineer → Cloud Architect
Highest-paid generalist track. Stack: networking + Linux + cloud + IaC.
- 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 people usually do. A Career Verdict judges whether it's realistic for you.
A Career Verdict includes
Built on POST's practitioner-authored assessment framework, calibrated by James from twenty years across helpdesk, infrastructure and security. Framework is human-authored; the verdict applies it to your inputs.