SRE
SLOs, error budgets, postmortems, building the thing that pages you less.
One of the best-paid infrastructure seats in the market, with an on-call profile that quietly ends careers. Worth it only if you genuinely like running other people's software.
- Domain
- Platform / DevOps
- Entry
- £45–68k
- Senior
- £115–150k
- You can code well enough to debug production at 2am without panicking
- Latency, error budgets and capacity planning sound like fun, not chores
- You want compensation that competes with senior software engineering
- You have a tolerance for ambiguity, half the job is undefined
- You can't ringfence your home life around a pager
- You want to build features, the job is mostly keeping other people's features alive
- You haven't shipped code in anger, the bar at good orgs is genuinely high
What "doing well" looks like in the seat
- Your post-incident reviews change behaviour, not just process
- You reduce a metric that someone outside engineering cares about
- You can read a flame graph and a service mesh trace without help
- Other teams ask for your input before they design, not after they ship
The on-call burnout is real and it's cumulative. A year of healthy on-call at a mature org is fine. Three years of unhealthy on-call at an immature one will cost you sleep, relationships and any appetite you had for the work. Interview the rota before you accept: pages per week, MTTR, how many engineers are on the rotation, who owns the noisy services. If the answers are vague, the rota is bad and they know it.
Tradeoffs at a glance
Hover any chip for the calibrated meaning. Ratings are directional, not absolute.
Promotion ceiling
Very high. Staff SRE comp tracks senior software engineering.
Who actually gets in
- +Backend dev who likes ops
- +Senior sysadmin who codes
Common misconceptions
- −That it's DevOps with a different name. SRE owns reliability targets formally.
Where this leads
- Platform Engineer
- Observability Engineer
- Infra Eng
Tech you'll see
- Kubernetes
- Linux
Pathways that pass through here
What this is based on
Practitioner judgement. External evidence review pending.
Last reviewed: not yet reviewed · UK market
Where this fits
Roles connect to pathways, certs and other roles. Use one to test the next.
- Platform / DevOps Engineer → SRE
Build the systems other engineers depend on. Requires coding fluency. Rarely entry-level.
- Cloud Engineer → Cloud Architect
Highest-paid generalist track. Stack: networking + Linux + cloud + IaC.
- Software Engineer (Backend / Full-stack)
Ship product, own services. Portfolio matters more than certs.
The next step
You've read about the role. The harder question is whether it's the right one for you.
A Career Verdict is the written, practitioner-authored call on your specific route into and out of this role. Six primitives, same format every time.
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 POST's practitioner-authored assessment framework, informed by two decades across helpdesk, infrastructure and security. The verdict applies that framework to your inputs.