Site Reliability Engineer: the engineers who keep production running
What SREs actually do between incidents, how the role differs from DevOps, platform and sysadmin work, what current postings ask for, and the realistic routes in.
A site reliability engineer (SRE) is a software engineer who owns how well production systems run: whether services stay available, how quickly problems are detected, and how fast the team recovers when something breaks. SREs write code to automate operations, build the monitoring and alerting that shows what systems are doing, join an on-call rotation, and lead the follow-up after incidents so the same failure does not happen twice. The title is used by internet companies, SaaS and cloud providers, and increasingly by organisations running regulated or government systems.
What a Site Reliability Engineer does
The defining idea of SRE is that reliability is an engineering problem, not a ticket queue. Instead of fixing the same outage by hand every month, an SRE writes the tooling, automation or design change that removes the cause. Teams usually agree reliability targets with product engineers, such as how much downtime a service can have in a quarter, and use those targets to decide when to ship features and when to slow down and fix things.
Day to day the work splits between project time and operational time. Project time goes into automation, platform improvements, capacity planning and better observability. Operational time is the on-call shift: responding to alerts, debugging live systems under pressure and writing up what happened afterwards. How the split falls varies a lot by employer and team, so ask about on-call load and incident volume in interviews.
- Taking an on-call shift: triaging alerts, mitigating an incident and handing over clearly to the next engineer.
- Writing a postmortem that explains the root cause without blame and lists the fixes that will stop it recurring.
- Automating a manual operation, such as cluster upgrades or certificate rotation, so nobody has to do it by hand again.
- Adding dashboards, alerts or tracing to a service that failed quietly last month.
- Reviewing a product team's launch plan for capacity, failure modes and rollback before it reaches production.
O*NET lists Site Reliability Engineer as a job title under Software Developers (15-1252.00). That grouping does not describe the day-to-day work well, so this page does not use O*NET's task or skill data.
What employers ask Site Reliability Engineers to do and bring
- Employers put on-call and incident response at the centre of the job: taking part in a rotation, mitigating live incidents and following up afterwards.
- Observability comes up in every posting we read: building monitoring, alerting, logging and tracing so problems are found before users report them.
- SRE is a coding role: employers ask for real programming ability, often Go or Python, and expect you to automate operational work rather than repeat it.
- Container orchestration, usually Kubernetes, and infrastructure as code such as Terraform are the platform skills postings name again and again.
- Deep Linux knowledge is asked for, especially in infrastructure-heavy and government roles.
- Reliability practice, meaning service-level objectives, error budgets, capacity planning and production-readiness reviews, is part of the job description at several employers.
- Palantir's government SRE posting asks for an active security clearance and lists DoD 8570 certifications such as Security+ or CISSP as preferred.
These points come from current job postings on the employers' own public job boards, read on the dates shown. Each general point is backed by at least two independent sources; points that rest on a single employer name that employer. They describe what employers commonly ask for, not legal requirements, and any one employer may differ.
| Source | Posting or document | Read |
|---|---|---|
| Axon | Site Reliability Engineer II | Nov 14, 2026 |
| Elastic | Senior Site Reliability Engineer (Hosted Infra) | Nov 14, 2026 |
| MongoDB | Senior Site Reliability Engineer, InfraSec | Nov 14, 2026 |
| palantir | Site Reliability Engineer - US Government | Nov 14, 2026 |
| Senior Site Reliability Engineer, Ads | Nov 14, 2026 | |
| Roblox | Senior Site Reliability Engineer, Compute | Nov 14, 2026 |
Reading a specific posting? See what Site Reliability Engineer job descriptions list: duties and asks counted across the postings we read, and how to tailor your resume to them.
SRE vs DevOps engineer, platform engineer and system administrator
- A DevOps engineer usually focuses on delivery: build pipelines, deployment and developer workflow. An SRE focuses on how services behave once they are live, measured against reliability targets.
- A platform engineer builds the internal platform other engineers use; many SRE teams do platform work too, but SREs are judged on production outcomes such as availability and recovery time.
- A system administrator traditionally operates servers by hand and by script; SRE treats operations as software, so expect coding interviews alongside systems questions.
- The titles overlap in practice. Read the duties: if the posting centres on on-call, incidents and service-level objectives, it is an SRE role whatever it is called.
How to become a Site Reliability Engineer
- Start from software or systems. Many people reach SRE from backend software engineering or from systems administration and then fill the other half of the skill set.
- Get fluent in Linux and networking. Debugging at the operating-system level and understanding DNS, load balancing and TCP is the core of incident work.
- Learn one language well. Go and Python appear again and again in the postings we read; build a real tool, not just scripts.
- Run something in production. Deploy a small service on Kubernetes with Terraform, add metrics and alerts, break it on purpose and write the postmortem.
- Move inside your company if you can. Volunteering for on-call, incident reviews or observability work on your current team is a common bridge into an SRE title.
What Site Reliability Engineers work with
- Orchestration and containers: Kubernetes, Docker and the managed services on AWS, Azure or GCP.
- Infrastructure as code: Terraform or similar, with reviewed, testable modules rather than hand-built servers.
- Observability: metrics, logs and tracing tools such as Prometheus and Grafana, and alert design that avoids noise.
- Programming: Go or Python for automation and services; Bash for glue work.
- Incident practice: runbooks, blameless postmortems and clear writing under time pressure.
Credentials: what exists and what employers rely on
- SRE is not a licensed occupation, and the postings we read ask for experience and demonstrable skills rather than a certificate.
- Vendor certifications can help show platform knowledge, for example the Kubernetes certifications, Terraform certification, AWS certifications or Linux certifications.
- Government and defense SRE roles can list security certifications such as CompTIA Security+ or CISSP as preferred.
Certifications are optional unless an employer or regulator says otherwise; read the posting, and check eligibility on the issuer's own site before you apply.
Where this role leads
- devops engineer: for delivery pipelines and developer workflow.
- platform engineer: for building the internal platform other teams use.
- Software Engineer: the broader occupation O*NET groups SRE under, for product and backend development.
What Site Reliability Engineers earn
TryHired does not print a salary for site reliability engineers. The U.S. Bureau of Labor Statistics publishes pay for occupations, not job titles, and no BLS occupation matches this title closely enough for us to quote its pay here.
Pay for this title depends on employer, industry, region and level, so ask how the role is graded and compare offers against the posting's own range where one is published.
Every page for Site Reliability Engineers
What real postings list.
Open →SkillsSite reliability engineer skillsKeeping production healthy, and showing you can.
Open →Interview questionsSite reliability engineer interview questionsPractice explaining incidents, automation and the reliability trade-offs you made.
Open →Applying for Site Reliability Engineer jobs
- Lead your resume with incidents and outcomes: what broke, what you did, and how detection or recovery time changed afterwards.
- Show automation that removed toil, and say what it replaced, for example a manual upgrade or a weekly cleanup.
- Expect a coding interview and a systems-debugging interview; practise talking through a live outage step by step.
- Ask about on-call: rotation size, pages per week and whether follow-up work gets time on the roadmap.
Two free tools start from this job title, so you only add your own experience: draft a resume summary for a Site Reliability Engineer role or write a LinkedIn headline for a Site Reliability Engineer role. Neither fills in skills or results for you: list only the work you have actually done.
Disclosure: TryHired makes HIRED, a paid job-search program, so we have a conflict of interest when we mention it. Everything on this page is free to use without buying anything.
Other job titles in this group
Questions people ask
What does a site reliability engineer do?
Is SRE the same as DevOps?
Do site reliability engineers need to code?
How this page is built
The employer section summarises current postings from the employers' own public job boards, saved on the read date shown; every general point is backed by at least two independent sources and single-employer points name the employer; each maps to short verbatim quotes in this page's claims ledger. Employers' preferences are not legal requirements. The job, difference, path, tools and hiring sections are TryHired's explanation and advice, labelled as such. TryHired does not print pay for job titles that BLS does not publish separately.
- Pay for this title: BLS publishes occupations, not titles.
- Whether a particular employer requires a degree, a certification or a license for this title.
- How a specific company levels or names this role.
- Axon, “Site Reliability Engineer II” job posting, read Nov 14, 2026.
- Roblox, “Senior Site Reliability Engineer, Compute” job posting, read Nov 14, 2026.
- Elastic, “Senior Site Reliability Engineer (Hosted Infra)” job posting, read Nov 14, 2026.
- MongoDB, “Senior Site Reliability Engineer, InfraSec” job posting, read Nov 14, 2026.
- Reddit, “Senior Site Reliability Engineer, Ads” job posting, read Nov 14, 2026.
- palantir, “Site Reliability Engineer - US Government” job posting, read Nov 14, 2026.
- U.S. Bureau of Labor Statistics publishes pay by occupation; no occupation matches this title closely enough to quote.