Site reliability engineer career path: from SRE to staff engineer or SRE manager
Each step up the SRE ladder, from site reliability engineer through senior to staff and principal site reliability engineer, or to SRE manager and head of platform: what changes in the job, the gap to close, how to show it on your CV and in interviews, and a plan.
The cvscored team
Contents
The ladder at a glance
| Step | What you are measured on next | Typical time |
|---|---|---|
| Site reliability engineer to senior site reliability engineer | Services you own and incidents you lead | 2 to 3 years |
| Senior site reliability engineer to staff site reliability engineer | Reliability across many teams | 2 to 4 years |
| Staff site reliability engineer to principal site reliability engineer | The production estate of the company | After several large changes |
| Senior site reliability engineer to SRE manager | A team, its on-call and its growth | After leading people |
| SRE manager to head of platform | Reliability, platform and their budget | Several years |
This ladder has three neighbours. DevOps engineers reach head of platform from the delivery side; their steps are on the DevOps engineer career paths. SREs who turn to cloud design follow the cloud engineer career paths to cloud architect and head of cloud.
Platform engineers build the paved roads that SREs help keep reliable, and the two roles often sit in one department; the platform engineer's own steps, from senior to staff and principal, are set out in the platform engineer career paths.
From site reliability engineer to senior
Site reliability engineer to senior site reliability engineer
What changes: you own the reliability of a group of services: their targets, alerts and capacity. You lead incidents rather than help in them, and other teams ask you before a risky change.
The gap: leading incidentsAsked in 25% of site reliability engineer ads (as of 5 Nov 2026).Lead an incident: roles, updates, a timeline, the way back to service, and the review afterwards., SLOs that the product owner agreed to, KubernetesAsked in 33% of site reliability engineer ads (as of 5 Nov 2026).Run production clusters: scheduling, health checks, autoscaling, upgrades and what fails when a node dies. and the cloud under load, and automation in PythonAsked in 67% of site reliability engineer ads (as of 5 Nov 2026).Tools that remove repeated work: checks, clean-ups, reports and small services that fix things on their own. or GoMany reliability tools and operators are written in Go; read them and write small services in it. that others use.
On the CV and in interviews: a service whose reliability you changed, in numbers; an incident you led; a piece of toil you removed. Expect an incident role play and a design with a target.
Plan (12 to 18 months): lead the incident rota for your services; set SLOs and an error budget policy with one product team; remove the biggest source of night pages; run a game day.
Staff and principal SRE, SRE manager and head of platform
Senior site reliability engineer to staff site reliability engineer
What changes: your work crosses teams: the standards for SLOs and alerts, the incident process, the hardest cross-team incidents and the reliability parts of big designs. You lead through reviews and writing, not through a team.
The gap: influence without authority, written proposalsAsked in 8% of site reliability engineer ads (as of 5 Nov 2026).Calm, short updates during an incident, and reviews that teach without blaming anyone. people adopt, and the cost side of reliability in terms leadership understands.
On the CV and in interviews: a practice many teams took up and what it changed, and a design review that prevented an outage. Expect to discuss a trade-off between speed and reliability with a product leader.
Plan (12 to 24 months): write the reliability standard and bring three teams onto it; lead the review of the worst incident of the year; mentor two engineers through their first incidents as lead.
Staff site reliability engineer to principal site reliability engineer
What changes: you look after the reliability of the whole production estate: which regions, which dependencies, which risks the company accepts, and where the next large outage will come from.
The gap: company-wide risk thinking, provider and architecture choices, and a record of large changes that held.
On the CV and in interviews: a strategy you wrote and the incidents it prevented, measured at company level. Expect a question from the board's point of view: what would a day without the main region cost us?
Plan (several years): own the resilience plan for the critical services; lead a recovery test across regions; build a group of staff engineers who review each other's designs.
Senior site reliability engineer to SRE manager
What changes: you lead the SRE team: hiring, growth, the on-call model, priorities and the relationship with product teams. Your hands leave the keyboard for most of the week.
The gap: leading peopleAsked in 8% of site reliability engineer ads (as of 5 Nov 2026).Calm, short updates during an incident, and reviews that teach without blaming anyone., a fair on-call that people can keep up, planning and a budget for tools and headcount.
On the CV and in interviews: a team you built or grew, how its on-call load changed, and reliability results across its services. Expect a case: the team is burning out on pages; what do you do in the first month?
Plan (12 to 24 months): line-manage two engineers; take over the on-call model and its numbers; agree the team's goals with product leadership each quarter.
SRE manager to head of platform
What changes: you run reliability and the platform together, with several teams, the budget for cloud and tools, and the targets the company commits to customers.
The gap: leading leads, budgets and suppliers, and goals in business terms such as outage cost, release speed and cost per customer.
On the CV and in interviews: the department you led, its budget and the change in incidents, speed and cost. Expect a case on cloud spend rising while incidents also rise.
Plan (several years): take over the platform team next to yours; own the reliability and tool budget for a year; find a mentor who runs an infrastructure department.
Above head of platform the steps lead to infrastructure and technology leadership, which differ too much between companies to describe here; the cloud architecture road is on the cloud engineer page linked at the top.
Your CV for the next step
Moving up in SRE shows on a CV as a wider reach: from the services you kept running, to practices many teams use, to the reliability a company promises its customers. Three rules:
- Leave every past title exactly as it was. Let the lines below it show the size of what you looked after.
- Speak the next level's language. Senior ads say "own", "lead incidents", "SLOs"; staff ads say "across teams", "standards", "design reviews"; manager ads say "team", "on-call model", "hiring".
- Tie a figure to every line. Incidents, time to restore, pages per week, services covered.
| Skill | Weak line | Strong line, with proof |
|---|---|---|
| Reliability standard | Defined SRE practices. | Wrote the SLO and alerting standard taken up by fifteen teams in a year; customer-facing incidents fell by a third. |
| Incident leadAsked in 25% of site reliability engineer ads (as of 5 Nov 2026).Lead an incident: roles, updates, a timeline, the way back to service, and the review afterwards. | Led incidents. | Led the response to the largest outage of the year and its review; the fix to failover was tested and in place within six weeks. |
| SRE teamAsked in 8% of site reliability engineer ads (as of 5 Nov 2026).Calm, short updates during an incident, and reviews that teach without blaming anyone. | Managed the SRE team. | Grew the SRE team from three to eight engineers and moved on-call to a follow-the-sun rota; night pages per person fell sharply. |
| Resilience plan | Worked on disaster recovery. | Wrote and tested the plan to run the core services from a second region; the yearly test now passes within the target time. |
Key takeaways
- The ladder runs SRE, senior, then staff and principal, or SRE manager and head of platform.
- Senior means owning services and leading incidents; staff means practices across many teams.
- DevOps engineers reach head of platform by their own road; the two career pages link to each other.
- Cloud architecture continues on the cloud engineer page, platform steps on the platform engineer page.
- Show each step with a wider reach and a figure, under the job where it happened.
Frequently asked questions
- What comes after senior site reliability engineer?
- Staff site reliability engineer for practices across teams without managing people, or SRE manager to lead the team.
- Can I move up without managing people?
- Yes. Staff and principal site reliability engineer are senior steps without a team.
- Do I need a certification to move up?
- No law asks for one. Senior ads ask mostly for services you kept reliable and incidents you led.
- How is an SRE manager different from a head of platform?
- An SRE manager leads one team and its on-call; a head of platform runs several teams, the platform and its budget.
- What should my CV show for a staff role?
- Practices many teams adopted, design reviews that prevented outages, and measured changes in incidents.