Skip to main content
POST ATLAS
RolePlatform / DevOps

SRE

SLOs, error budgets, postmortems, building the thing that pages you less.

The verdict

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.

Pick this if
  • 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
Skip this if
  • 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 bit you're probably underestimating

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

Where this fits

Roles connect to pathways, certs and other roles. Use one to test the next.

Pathways that touch this
Roles to consider
Certifications in scope
Perspectives that bear on this

The serious 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.

Plateau zone
The flat year nobody warns you about, named and timed.
Reality vs Fantasy
Your actual five-year curve against the one you've been sold.
What to sit and what to skip
Each cert on your list: useful, optional, or skip, with reasons.
The call
A single written judgment on whether your plan holds up.
Tradeoff spectrum
What you're giving up for what you're choosing, plotted.
Decisive factors
The two or three things that will actually make or break this.
See what a Career Verdict looks like£25 · one verdict, yours to keep

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.

All roles