Skip to main content
Platform engineering

Platform / DevOps Engineer → SRE

Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.

Last reviewed May 2026Reviewed by a practitioner working in junior devops / sre hiringUpdated quarterly against live job listings
The verdict

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 POST practitioner estimates, not survey data.

  1. 01Foundations
    0–6 months

    Literacy, lab habits, the cert that opens first conversations.

    AWS Solutions Architect Associate
  2. 02First paid role
    6–18 months

    Land a Junior DevOps / SRE. Operational time, not more certs, earns the next move.

    Junior DevOps / SRE
    £50–70k junior DevOps
  3. 03Specialisation
    1.5–3 years

    Add a specialist credential aligned to the work you're already doing.

    Terraform AssociateCKAD
    £75–105k mid
  4. 04Advanced
    3+ 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.

  • AWS Solutions Architect Associate
  • Terraform Associate
  • CKA
None on this route.

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
SRECloud EngineerBackend EngineerDevSecOps
  • ·Cloud-first then add automation
  • ·Backend dev then add ops

Realistic expectations

What no recruiter will tell you.

Misconception

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.

Honest window

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.

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.

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.

POST ATLASVerdict no. PA-2026-0512
Career analysis report

Career Verdict

Helpdesk → Security Architect

“Realistic, but not by adding another certification.”
  1. 01
    The callA clear judgement on whether your route is realistic, and under what conditions.
  2. 02
    Where the route breaksThe most likely point to stall, and why it happens in practice.
  3. 03
    What to do nextSpecific priorities for the next 6–24 months, and what to drop.
Generated within POST’s practitioner-authored assessment frameworkPOST ATLAS

Career Verdict

£39One-off payment. No subscription.
  • 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.
See the Career Verdict

Usually within minutes of payment. Kept 24 months, then deleted. Deletion on request at any time.

Built on POST's practitioner-authored assessment framework, informed by two decades across helpdesk, infrastructure and security. The verdict applies that framework to your inputs.