How to become a site reliability engineer
SRE is the discipline of treating operations as a software problem, and its defining idea is that perfect reliability is the wrong target because it costs more than it returns. You set an error budget, spend it deliberately on shipping speed, and automate the toil that would otherwise consume the team. When it works, the on-call load falls year on year — that reduction is the actual deliverable.
Written by the JobStraight team · pay and hiring figures measured 2026-08-25 · page updated 2026-09-01
The realistic ways in
Which people each route suits, and what it honestly costs.
From software engineering
The route the discipline was designed for. You already write code; you apply it to reliability, capacity and automation instead of features.
From DevOps or platform engineering
Very close, and often the same job with a different title. The genuine difference is the measurement culture — SLOs, error budgets, and the argument they enable.
From system administration
Viable and requires real commitment to coding. An SRE who does not write software is an administrator with a newer title, and the ceiling arrives quickly.
The title you get hired into first
The titles this role is actually hired under:
- Site Reliability Engineer
- Platform Engineer
- DevOps Engineer
- Infrastructure Engineer
- Production Engineer
- Systems Engineer
135 live site reliability engineer openings are on the site right now, refreshed on every build and linking to the employer's own posting.
What to learn, in order
Ordered by dependency, not by interest. Durations assume eight to ten hours a week and are an estimate, not a measurement.
-
Linux and distributed systems 8 weeks
Processes, memory, networking, and what actually happens when one node in a cluster stops answering.
-
Code, seriously 10 weeks
Python or Go to a standard where you write tools others depend on. This is the line between SRE and traditional operations.
-
Observability and SLOs 6–8 weeks
Metrics, logs, traces, and the discipline of defining what "working" means before an incident rather than during one.
-
Incident practice ongoing
Response, blameless postmortems, and the follow-up actions actually being done. A postmortem nobody acts on is a diary entry.
The one piece of work that changes the conversation
A service with an SLO you defined, monitoring that proves whether you are meeting it, and one piece of toil you automated away with the time saved measured. The measurement is what makes it an SRE artifact rather than a DevOps one — the discipline is fundamentally about being able to argue with numbers.
What it pays, measured
From salary figures on live site reliability engineer postings, not a survey. Half sit between the outer two columns.
| Market | Lower quarter below | Midpoint | Upper quarter above | Postings with a figure |
|---|---|---|---|---|
| India | ₹10L | ₹15L | ₹22L | 105 |
| the UK | £68k | at least £70k | at least £70k | 151 |
| the US | $140k | at least $140k | at least $140k | 1,005 |
How much of this the source estimated rather than read off a posting: India 0%, the UK 29%, the US 70%. The full note, and what it means for each market, is on the salary page below.
The full distribution for each market, the twelve-month movement and the employers posting most of these roles are on the site reliability engineer salary page.
What the role is screened on
Our skill study covers six role groups and site reliability engineer is not one of them. So this list is editorial — what the interviews test — not a count of postings.
Who is hiring, right now
Ranked by how often each appears in site reliability engineer advertisements, measured 2026-08-25. Advertisement frequency, not vacancy count — which is why there is an order here and no number.
- India: Oracle, H & R Johnson, GENPACT, Bank of America, BP Ergo
- the UK: J.P. Morgan, JPMorgan Chase, Amazon, Barclays, London Stock Exchange Group
- the US: Oracle, Ford, JPMorgan Chase, Cognizant, Google
Appearing high can mean growth, turnover, an agency posting for a client, or a bulk feed repeating one advertisement. Research, not a recommendation.
What gets people rejected
Aiming for 100% uptime. It is the answer that shows the candidate has not met the core idea of the field, which is that the last fraction of a percent costs more than it is worth and the budget should be spent shipping.
Whatever you write, make sure the resume that gets you the interview can survive the questions it invites — everything on it is fair game, and the numbers attract the most scrutiny. Check it against a real posting before you send it.
How long it really takes
Twelve to twenty-four months from software engineering or strong operations. Not an entry-level role, and job postings that describe it as one usually mean DevOps support.
Who finds this harder than expected. People who want their weekends guaranteed. The pager is the job, and although good SRE work reduces it over time, it never reaches zero.
Common questions
How long does it take to become a site reliability engineer?
Twelve to twenty-four months from software engineering or strong operations. Not an entry-level role, and job postings that describe it as one usually mean DevOps support.
Do you need a degree to become a site reliability engineer?
Not usually a specific one — From software engineering; From DevOps or platform engineering; From system administration are all routes people take here. Where a degree matters it is a filter at large employers rather than something the work needs.
What should be in a site reliability engineer portfolio?
A service with an SLO you defined, monitoring that proves whether you are meeting it, and one piece of toil you automated away with the time saved measured. The measurement is what makes it an SRE artifact rather than a DevOps one — the discipline is fundamentally about being able to argue with numbers.
What gets people rejected for site reliability engineer roles?
Aiming for 100% uptime. It is the answer that shows the candidate has not met the core idea of the field, which is that the last fraction of a percent costs more than it is worth and the budget should be spent shipping.
Which job title should you apply to first?
Not site reliability engineer necessarily — Site Reliability Engineer, Platform Engineer, DevOps Engineer, Infrastructure Engineer are where people are actually hired in.
Is site reliability engineer the right role for you?
It is harder than the internet implies for one group in particular: people who want their weekends guaranteed. The pager is the job, and although good SRE work reduces it over time, it never reaches zero.
Where to go next
- Live site reliability engineer openings — current vacancies, linking to the employer's own posting.
- Site Reliability Engineer salary in detail — full distribution, twelve-month movement, top employers.
- Check your resume against a real posting — actual skill overlap and the knockout rules, not a keyword score.
- All career paths — the other roles covered the same way.