DevOps and SRE Career Guide
Explore DevOps, SRE and platform engineering jobs, salaries and career paths. Get interview preparation, and stay current on incidents, observability, Kubernetes, cloud cost and the reliability problems AI-assisted delivery is creating.
How we research our career guides
The Top DevOps and SRE News, in 5 Minutes.
We handpick the best DevOps and reliability newsletters and distill the key incidents, releases and cloud changes into a 5-minute audio briefing, texted to you every morning.
Try the DevOps Briefing, FreeFreeSee the 4 newsletters we handpicked

At a glance
DevOps and SRE at a Glance
Reliability engineering has no occupation code of its own. Federal statistics count most of this work inside software development, which employed 1,717,800 people in 2025 at a median of $135,980, and inside network and computer systems administration, 323,600 jobs at $99,130. The familiar picture, a system administrator who picked up scripting, is now the smallest part of it. The titles are genuinely different jobs: DevOps engineers who build the delivery pipeline and the automation around it, site reliability engineers who run production against a numeric service level objective and spend an error budget against it, platform engineers who ship an internal developer platform as a product for other engineers, cloud engineers who provision and cost the infrastructure underneath, and observability engineers who own the telemetry everyone else debugs from. Pay follows which occupation you are counted in more than years served, which is why the move out of administration into software and platform work is the consequential one: those medians sit about $37,000 apart, and administration is projected to shrink 4 percent to 2035 while software development grows 10 percent. A computer science degree is the common route in, not the only one, because the field hires on evidence that you can operate something. The direction of travel is set by internal platforms, which 90 percent of organisations now report running, and by AI-assisted delivery, which raises how much change you ship without making any of it safer to release.
Key Industry Statistics
1,717,800
Software developers employed in the US (2025)US Bureau of Labor Statistics
$135,980
Median annual pay, software developers (May 2025)US Bureau of Labor Statistics
90%
Organizations running an internal developer platformGoogle Cloud DORA research, 2025
33%
Average share of Google SRE time spent on toilGoogle, Site Reliability Engineering
Common Titles
- DevOps Engineer
- Site Reliability Engineer
- Platform Engineer
- Cloud Engineer
- Infrastructure Engineer
- Observability Engineer
Where This Work Sits
- Cloud and SaaS vendors
- Banks and fintech
- Retail and marketplaces
- Media and streaming
- Healthcare and government
- Consultancies and managed providers
Credentials That Matter
- CKA and CKS
- AWS CloudOps Associate
- AWS DevOps Engineer Professional
- Google Cloud DevOps Engineer
- Terraform Associate
Key Areas in DevOps and SRE
Delivery Engineering
Pipelines, build and test automation, progressive rollout, and the ability to roll back quickly.
Reliability and SLOs
Service level indicators, objectives, and the error budget that decides whether releases continue.
Incident Response
Paging, incident command, mitigation under time pressure, then a blameless written postmortem.
Platform Engineering
An internal developer platform run as a product, with golden paths and self-service.
Observability
Traces, metrics and logs instrumented so an unfamiliar failure can still be debugged.
Cloud and Cost
Infrastructure as code, capacity planning, and treating spend as an engineering constraint.
DevOps and SRE Jobs & Salaries
Federal wage data measures occupations rather than job titles, and there is no federal occupation called site reliability engineer. This ladder therefore reads as the adjacent occupations the work is actually counted in. Every figure is the May 2025 median from the Occupational Outlook Handbook.
Computer network support specialists
$76,220
Network and computer systems administrators
$99,130
Information security analysts
$129,180
Computer network architects
$134,050
Software developers
$135,980
Computer and information systems managers
$175,140
Source: US Bureau of Labor Statistics, Occupational Outlook Handbook, May 2025 wage data, accessed October 2026.
DevOps and SRE Career Paths
This is not one ladder. It is four tracks that share a set of tools and then diverge sharply in who their user is, what they are measured on, and how much of the week is spent on someone else's emergency.
- Network or Cloud Support0 to 2 yearsTickets, monitoring and runbooks. Median $76,220. Measured on reliability of execution, not range.
- Systems Administrator2 to 4 yearsOwn real systems at $99,130 median, and start replacing manual steps with code before the occupation shrinks under you.
- DevOps Engineer4 to 7 yearsOwn the pipeline end to end. Usually counted as a software developer, where the median is $135,980.
- Senior DevOps Engineer7 or more yearsSet delivery standards across teams and answer for change fail rate and recovery time rather than for one pipeline.
Credential that fits AWS CloudOps Associate, then a DevOps professional exam
There is no federal occupation code for a site reliability engineer, a DevOps engineer or a platform engineer. Most of this work is counted under software developers, some under network and computer systems administrators or computer network architects, and management from the first-line manager upward under computer and information systems managers, which is why the figures on this page come from those occupations rather than from a job title.
A Typical Day in DevOps and SRE Jobs
Five roles that carry most of this field's headcount, ordered from the first rung to principal. The schedules are representative rather than universal, and the on-call day is deliberately shown twice: once as it is planned, and once as an incident rewrites it.
Cloud Operations EngineerEntry-Level · Managed InfrastructureThe first line on monitoring and tickets, and usually the person who notices that an alert has been firing all week and nobody owns it.
- 08:30Handover and alert triage: what fired overnight, what was acknowledged, and what is still unexplained.
- 09:30Access requests, certificate renewals and patching. The work that is obviously toil by the published definition.
- 11:30Shadow a senior engineer on a real diagnosis. This is how the pattern library gets built.
- 14:00Write or correct a runbook for the thing you had to ask about this morning.
- 16:30Script away one recurring request, and note the hours it used to take so the saving is arguable.
DevOps EngineerEntry to Mid · Delivery PipelineOwner of how change reaches production, which means most of the day is spent on other teams' releases rather than your own code.
- 09:00Check pipeline health: failing builds, flaky tests, queue depth, anything blocking a team from shipping.
- 10:00Pair with a product team on a deployment they are nervous about. Canary, flag, rollback path confirmed.
- 12:30Infrastructure as code review. Someone has hand-edited a console setting and the plan now disagrees.
- 14:00Project work: shorten change lead time on the slowest pipeline, measured before and after.
- 16:30Release window. Watch the indicators that actually page, not the dashboard that looks impressive.
Site Reliability EngineerMid-Level · On-Call RotationA planned day that an incident is allowed to take. Google's published model budgets about six hours for one incident including follow-up, which is why two in a 12-hour shift is the cap.
- 09:00On-call handover: open issues, anything degraded, and how much error budget the quarter has left.
- 10:00Planned engineering work, because at least half the week is supposed to be project time rather than operations.
- 11:40Page. Acknowledge inside the target, confirm customer impact, and declare an incident early rather than late.
- 11:55Stop the bleeding: shift traffic, roll back the suspect change, and keep the live document current.
- 13:30Service restored. Hand off command if you are now tired, and preserve the evidence for root-causing.
- 15:30Draft the blameless postmortem the same day, then watch the planned work slip to next week.
Platform EngineerMid to Senior · Internal Developer PlatformYour users are other engineers, so the day looks more like product work than operations: intake, roadmap, docs and the golden path nobody should have to think about.
- 09:00Read the platform's own support channel. Repeated questions are a design defect, not a documentation gap.
- 10:30Build: extend the service template so a new service reaches production without a human in the loop.
- 13:00Office hours with a team that wants an exception. Decide whether to pave it or refuse it.
- 15:00Review the scorecard: delivery metrics alongside developer satisfaction, because a platform can slow teams down.
- 16:30Secure defaults work: scoped credentials, policy enforcement, and the audit trail for automated actors.
Staff Site Reliability EngineerSenior-Level · Estate ReliabilityMostly other people's decisions. The day is design review, objective setting and the arguments that decide how much risk the organisation carries.
- 08:30Review the week's incidents across the estate, looking for the failure mode that repeats in three places.
- 10:00Design review on a new service. Blast radius, dependency failure modes, and what degrades instead of erroring.
- 12:00Objective setting with a product director: what the target should be, and the consequence of missing it.
- 14:00Postmortem review session. An unreviewed postmortem might as well never have existed.
- 16:00Write the proposal for next quarter's reliability work, with the cost of inaction attached.
JOB SEARCH
How to Get a DevOps or SRE Job in 2026
Whether you are moving out of operations, choosing between reliability and platform work, or deciding whether to lead a team, the same three questions decide it: what the field expects of you now, what you can already evidence, and how you answer for it in a room.
Entry-Level
Start in Infrastructure and Delivery
What the four common titles actually mean, where this work is counted and paid, the vocabulary the discipline runs on, and what a hiring manager expects from someone with no production track record yet.
What you should know about the field
The distinctions readers arrive confused about, and the definitions everything later in the career is built on.
DevOps, SRE and platform engineering are not synonyms
Google's own framing is the clearest primary source: "class SRE implements interface DevOps". DevOps is treated as a broad philosophy, usually summarised as culture, automation, lean, measurement and sharing, which says relatively little about how a specific service is operated. Site reliability engineering is a concrete job role with opinions: operations is a software problem, services are managed by service level objectives, toil is capped, ownership is shared with developers, and the same tooling is used regardless of job title.
The practical difference at interview is prescriptiveness. A DevOps answer can legitimately be about breaking down silos and shortening feedback loops. An SRE answer is expected to reach a number, because the role is defined by managing to an objective rather than by aspiring to reliability.
Platform engineering is a product discipline, and cloud engineering is not
DORA describes platform engineering as a sociotechnical discipline and an internal developer platform as "an internal product designed specifically for developers", whose main goal is hiding infrastructure complexity behind golden paths. The CNCF platforms white paper says the same thing from the standards side: a platform is an integrated collection of capabilities defined and presented according to the needs of its users, run like a product, self-service, secure by default.
Cloud engineering is the layer beneath that: provisioning compute, networking, storage and identity, and owning what it costs. The useful test is who your user is. A platform engineer's user is another engineer. A cloud engineer's user is usually the platform.
There is no federal occupation called site reliability engineer
The Bureau of Labor Statistics has no SRE, DevOps or platform engineer occupation, so this work is counted in the adjacent ones. Software developers, SOC 15-1252, recorded 1,717,800 jobs in 2025 at a median of $135,980 and 10 percent projected growth to 2035. Network and computer systems administrators, SOC 15-1244, recorded 323,600 jobs at $99,130, and is projected to shrink 4 percent.
That divergence is the single most useful fact in this career. The same person, doing recognisably similar work, is counted and paid very differently depending on whether the employer files the role under administration or under software.
SLIs, SLOs and SLAs, in the original definitions
A service level indicator is "a carefully defined quantitative measure of some aspect of the level of service that is provided", such as request latency or error rate. A service level objective is "a target value or range of values for a service level that is measured by an SLI". A service level agreement is a contract with users that carries consequences, usually financial, for missing the objectives inside it.
The test that separates the last two is simple: ask what happens if the target is missed. "If there is no explicit consequence, then you are almost certainly looking at an SLO." The chapter's other advice is worth memorising because candidates get it backwards: have as few objectives as possible, do not set a target from current performance, and start loose and tighten.
Skills employers look for
What a hiring manager is actually checking on a first infrastructure hire, beyond the tools on the posting.
Linux and systems fundamentals
Infrastructure as code
Containers and Kubernetes
Scripting plus one real language
Interview questions and answers
The screening questions, where the subject is whether you understand the discipline and can debug something live.
What is the difference between DevOps and SRE?
What they are looking for: Whether you can distinguish a philosophy from a job. The weak answer is that they are the same thing with different branding.
I use Google's framing: SRE implements DevOps. DevOps is the broad set of ideas, no silos, small frequent changes, measurement, shared ownership. SRE is a prescriptive role that implements part of it: treat operations as a software problem, manage the service to a service level objective, cap toil, and give the team authority to slow releases when the objective is at risk. DevOps tells you what to value; SRE tells you what to measure.
Make it yours: Name the prescriptive parts. An answer that stays at the culture level reads as someone who has not run a service to a number.
A service is slow. Walk me through how you would diagnose it.
What they are looking for: A method rather than a tool list. They want to see you narrow the problem instead of guessing at the component you know best.
First I check whether it is actually slow against the indicator we measure, and for whom, because a p99 regression on one endpoint is a different problem from a global one. Then I look at what changed: deploys, config, feature flags, traffic shape, a dependency. I follow a trace end to end to find where the latency is being added rather than inferring it from dashboards, and I confirm the hypothesis before I act on it.
Make it yours: Lead with the measurement and the blast radius. Jumping straight to a database or a cache is the most common way this answer fails.
What would you check when a Kubernetes pod will not start?
What they are looking for: Hands-on familiarity. Troubleshooting is the largest domain of the CKA exam for a reason: it is most of the job.
I read the pod status and events first, because the reason is usually written there: an image it cannot pull, a scheduling constraint nothing satisfies, a missing secret or config map, a volume that will not mount, or a probe failing so the container restarts in a loop. If the events are clean I look at the container logs and the previous container's logs, then at node capacity and taints.
Make it yours: Say what you read, in order. Candidates who recite failure categories without naming where they would look sound like they have only read about it.
Why this work rather than a straight software developer role?
What they are looking for: Whether you chose the discipline or ended up in it. Retention in infrastructure teams is the real question behind this.
I like the feedback loop. A feature's value is argued about for a quarter; a reliability change either holds at three in the morning or it does not. I also want the whole-system view, because the interesting failures are never inside one service. What I am not looking for is to be the person who clicks consoles, which is why I care that the team treats operations as a software problem.
Make it yours: Give a reason rooted in the nature of the feedback, not in avoiding product work. Interviewers hear the latter immediately.
Mid-Level
Own a Service and a Rotation
How on-call is supposed to be bounded, how incidents are actually run, what toil means in its original definition, and which vendor certifications employers still gate hiring on.
What you should know at this stage
The operational machinery you are now accountable for, and the numbers that say whether it is working.
On-call is bounded by design, not by stamina
Google's published model is explicit about the arithmetic. Handling an incident properly, including root-cause analysis, remediation and follow-up, averages about six hours, which caps a healthy rotation at about two incidents per 12-hour shift. The paging distribution should be flat with a median of zero pages a day, and a median above one a day is treated as unsustainable.
Response targets follow the objective rather than taste: roughly five minutes to acknowledge for user-facing or highly time-critical services, around 30 minutes for less time-sensitive ones, because a 99.99 percent quarterly target allows only about 13 minutes of downtime. Team size follows too: a minimum of eight engineers for a single-site rotation, or six per site across two sites, with each engineer on call at least once or twice a quarter so the skill does not decay.
Incident command is a role, not a rank
Serious incidents are run on a structure borrowed from emergency services. The incident commander holds the high-level state and assigns everything they have not delegated; the operations role is the only group modifying the system; a communications lead is the public face and keeps stakeholders and the live document current; and a planning role handles the longer tail, filing bugs, arranging handoffs and tracking changes so they can be reverted.
The declaration criteria are deliberately low. If you need a second team, if the outage is visible to customers, or if an hour of concentrated analysis has not solved it, it is an incident. The stated priority order is to stop the bleeding, restore service, and preserve the evidence for root-causing, in that order.
Toil has a definition and a fifty percent cap
Toil is not simply work you dislike. It is operational work that is manual, repetitive, automatable, tactical and interrupt-driven, has no enduring value, and scales linearly with the service. The more of those properties a task has, the more confidently it is toil.
The advertised goal is to keep it below 50 percent of each engineer's time, with at least half going to engineering project work. Google's own quarterly surveys report an average of about 33 percent, with individuals reporting anywhere from 0 to 80 percent, which is the honest version of the claim and the number to ask about in an interview.
Which cloud certifications employers still gate on
The vendor exams are specific enough to plan around. The Certified Kubernetes Administrator is $445 with one free retake, two hours, hands-on from a command line, and weighted toward troubleshooting at 30 percent. AWS Certified DevOps Engineer Professional expects two or more years of provisioning and operating AWS environments, and runs 180 minutes and 75 questions for $300. Google's Professional Cloud DevOps Engineer is two hours, 50 to 60 questions, $200, recommends three or more years of industry experience with one or more on Google Cloud, and explicitly assesses applying site reliability engineering practices.
Note the churn at the associate level: AWS retired the SysOps Administrator Associate exam on 29 September 2025 and replaced it with CloudOps Engineer Associate, 130 minutes, 65 questions, $150, aimed at about a year of experience. Check the current exam before you book a course against an old one.
Skills employers look for
What separates an engineer who can operate a service from one a team is organised around.
Writing and defending an SLO
Debugging in production
Progressive delivery and fast rollback
Interview questions and answers
Mid-career questions, where the subject shifts from what you know to what you did when it was broken.
Tell me about an incident you were on call for.
What they are looking for: A clean timeline, the mitigation before the diagnosis, and who you pulled in. They are testing judgement under pressure, not brilliance.
A certificate on an internal dependency expired overnight and failed closed, so requests that should have degraded gracefully returned errors. I mitigated first by pinning traffic to the path that did not need it, which bought us the error budget back, then renewed and automated the renewal. I declared an incident early and pulled in the owning team rather than trying to be the only person awake on it.
Make it yours: Lead with stopping the bleeding. Candidates who describe a long root-cause hunt while the service is down are describing the wrong instinct.
How would you set an SLO for a checkout service?
What they are looking for: Whether you can get from a vague reliability wish to a measurable target, and whether you know not to anchor on today's numbers.
I would pick a small number of indicators that represent what the user experiences: availability as the fraction of well-formed checkout requests that succeed, and a latency threshold at a percentile the business cares about. Then I would set a target with product rather than for them, start deliberately loose and tighten it, and resist copying current performance, because that locks in whatever heroics are already propping the service up.
Make it yours: Say out loud that you would use as few objectives as possible. A candidate who proposes a dozen indicators has not read the argument for restraint.
Describe a time you reduced toil.
What they are looking for: Whether you can recognise toil by its properties rather than by how much you dislike the task, and whether you measured the saving.
Our weekly capacity top-up was manual, repetitive, automatable, interrupt-driven and scaled with the number of clusters, which is the definition. I wrote a controller to do it and a report to prove it had, and the work went from about four hours a week to an alert nobody has had to act on. The point was not the hours; it was that the task scaled with the fleet and we were growing the fleet.
Make it yours: Use the properties as a checklist and give the before-and-after. Toil stories without a number read as a complaint that happened to win.
How do you make a risky deployment safe?
What they are looking for: Progressive delivery as a reflex, and whether you treat rollback as a first-class capability rather than a last resort.
Small batches first, because a change you can reason about is a change you can roll back. Then automated tests in the pipeline, a canary with the indicators we actually alert on, a flag so the behaviour can be turned off without a deploy, and a rollback path somebody has used recently. I would also check the error budget before shipping, because that decides whether the release should be going out at all.
Make it yours: End on the error budget. It converts a generic answer about canaries into one that sounds like it came from a team with authority.
Senior-Level
Build the Platform or Lead the Team
The three directions senior reliability work actually goes: deep technical leadership, ownership of an internal platform as a product, or management of the people and the budget that fund it.
What you should know at this stage
The structural facts that decide where senior reliability careers go, and what the research says is now the constraint.
Platform quality is now the ceiling on AI returns
DORA's 2025 research is unusually direct about this. Where internal platform quality is high, the effect of AI adoption on organisational performance becomes strong and positive; where it is low, that effect is negligible. Ninety percent of organisations report using an internal developer platform and 76 percent have established dedicated platform teams, so the question is no longer whether to have one.
The caution attached is the useful part: platforms can reduce throughput and change stability if they are not carefully managed, which is why DORA recommends judging one on a balanced scorecard of delivery metrics and developer satisfaction rather than on adoption alone.
AI raises throughput and lowers delivery stability
The 2025 DORA report surveyed nearly 5,000 technology professionals and found 90 percent using AI at work, more than 80 percent believing it had increased their productivity, and 30 percent reporting little or no trust in AI-generated code. It observed a positive relationship between AI adoption and software delivery throughput, and a continuing negative relationship with software delivery stability.
For a senior engineer that is a mandate rather than a statistic. The controls that absorb change volume, test automation, small batches, fast feedback and a platform that enforces them, are now the difference between AI returns and an incident rate that climbs quietly.
The administration occupation is shrinking while software grows
Network and computer systems administrators, 323,600 jobs at a median of $99,130, are projected to decline 4 percent to 2035 with about 13,400 openings a year. Software developers, 1,717,800 jobs at $135,980, are projected to grow 10 percent. Computer and information systems managers, 685,800 jobs at $175,140, grow 16 percent with about 53,500 openings a year.
Read together those are a map of the senior options. Staying in administration is the one direction the federal projections do not support, while the management occupation is both the largest pay step and the fastest-growing of the three.
Observability is a standard now, not a vendor choice
OpenTelemetry is a CNCF project covering traces, metrics and logs, and it is explicitly not a backend: storage and visualisation are left to other tools, and the project's own framing is that you own the data you generate with no vendor lock-in. The CNCF platforms white paper lists application observability among the capability domains a platform is expected to provide.
The senior consequence is architectural. Instrumenting to an open standard separates the instrumentation decision, which is expensive to change, from the backend decision, which is a procurement question you will revisit.
Skills employers look for
What an organisation is buying when it hires a senior reliability engineer rather than an experienced one.
Platform product thinking
Capacity and cloud cost engineering
Governing automation and agents
Interview questions and answers
Senior questions, where the subject is the platform, the organisation and the risk rather than one service.
Our error budget is always exhausted. What do you do?
What they are looking for: Whether you treat the budget as a management instrument or as a scoreboard. This is the senior version of the whole discipline.
First I check the objective is right, because a target copied from a competitor or set at 100 percent produces a permanently empty budget and teaches everyone to ignore it. If the target is right, the budget is telling us we are shipping faster than the system can absorb, so the response is the agreed one: slow or pause releases and spend the engineering time on testing and resilience. That only works if we have the authority to do it, so I would get that written down before I need it.
Make it yours: Interrogate the objective before proposing a freeze. Reaching for a release freeze first is how reliability teams lose the room.
How would you build an internal developer platform from nothing?
What they are looking for: Product instinct. They want to hear users, golden paths and adoption, not a list of CNCF projects.
I would treat it as an internal product with developers as the users, and start by finding the one path most teams already walk badly, usually getting a new service to production. I would pave that single golden path end to end, self-service, secure by default, with documentation and a template, and let teams adopt only the parts they need. Then I would measure it on a balanced scorecard: delivery metrics and developer satisfaction, because a platform can reduce throughput if it is not managed.
Make it yours: Name one golden path and how you would know it worked. Platform answers that start with a tool selection are the ones that get rebuilt in two years.
How do you make the case for reliability work to a product leader?
What they are looking for: Translation. Whether you can convert an engineering argument into the language of risk, cost and release velocity.
I bring the error budget rather than an opinion, because it is a shared number both of us agreed to, and it reframes the conversation from whether reliability matters to how much risk we decided to carry this quarter. Then I attach the cost: the incidents in the period, the engineering hours they consumed, and the releases we had to hold. I ask for something bounded, usually a quarter of platform work with agreed measures, because a bounded ask gets funded and an open-ended one gets deferred.
Make it yours: Lead with the shared metric and ask for something time-boxed. Arguments framed as reliability versus features lose by default.
What controls would you put around an AI agent with production access?
What they are looking for: Governance instinct. They want neither a blanket refusal nor someone who will hand an agent a production credential because the demo was impressive.
Scoped, short-lived credentials rather than a standing role, a bounded blast radius so the worst case is one service in one environment, approval gates on anything destructive or cross-cutting, and an audit trail that shows what it did and why. I would also insist the inputs are accurate, because the agent reads the service catalogue, the ownership graph and the runbooks, and a confidently wrong runbook is now an operational hazard rather than a documentation problem.
Make it yours: Name the inputs as well as the permissions. Most candidates cover access control and forget that the agent's context is now production data.
Why DevOps and SRE Engineers Need to Stay Informed
This field documents its own failures in public, and that literature is scattered across engineering blogs, incident reports and conference talks. General technology coverage reports that a service went down. The reliability press tells you the mechanism, which is the only part that transfers to your own system.
Read more
The second reason is economic. The cloud providers ship changes faster than any team can track, and a repricing or a deprecation can quietly invalidate an architecture you spent a quarter building.
The bottom line
Reliability Work Is Changing Faster Than the Tooling.
The federal numbers and the research point the same way. System administration is projected to shrink 4 percent to 2035 while software development grows 10 percent, and 90 percent of organisations now report running an internal developer platform. The work is moving toward software, and the advantage goes to engineers who see it moving.
Stay Informed with Hark's DevOps and SRE Briefing
How it works
Curated from the best newsletters
Hark's editorial team handpicks the sources worth following. See how we rank
The news that matters in 5 minutes
Hark distills the most important stories into a concise audio briefing.
Texted to you every morning
You set the time and listen when you want.
Go deeper if you want
Upgrade to the 15-minute briefing and select up to 50 newsletters.

The 4 DevOps and SRE Newsletters We Handpicked
DevOps Weekly
Gareth Rushgrove
- Free
- Weekly
A long-running weekly email of curated DevOps news and articles assembled by Gareth Rushgrove, running since 2010.
Why DevOps and site reliability engineers read it
Gareth Rushgrove's curated weekly, running since 2010, on the tools, practices and writing worth your attention. Longevity matters in a field full of vendor noise: this is a human filter with fifteen years of taste behind it.
More about this newsletter
Each week Rushgrove (a veteran of Puppet, Docker, and Snyk) sends a plain list of the DevOps articles, tools, and talks he found most interesting, spanning infrastructure automation, delivery pipelines, and operations culture. One of the oldest continuously running newsletters in the space. Free, delivered via Mailchimp.
SRE Weekly
Lex Neva (Tinker Tinker Tinker, LLC)
- Free
- Weekly
A weekly curated newsletter on site reliability engineering (availability, incident response, human factors, and automation) curated by Lex Neva since 2015.
Why DevOps and site reliability engineers read it
Lex Neva's weekly on availability, incident response, human factors and automation, curated since 2015. It is the best single route to other people's postmortems, which is the fastest way to learn failure modes you have not lived through.
More about this newsletter
Weekly links with commentary covering everything related to keeping services available: incident write-ups, resilience engineering, observability, databases, Kubernetes, and human factors. Neva is a staff SRE (Honeycomb, previously Fastly, Heroku, and Linden Lab) and has published 500+ issues over roughly a decade. Free, with email, RSS, and Mastodon delivery.
See the other 2 newsletters
TLDR Dev
TLDR (TLDR Media)
- Free
- Daily
- 470k readers
Daily software engineering news, tools, and web dev links in a five minute read.
Why DevOps and site reliability engineers read it
A daily five-minute read of engineering news, tools and links for roughly 470,000 developers. The weeklies give you depth, this gives you the clock, so a major release or a serious vulnerability does not wait for the weekend.
More about this newsletter
TLDR Dev is the software engineering edition of the TLDR network: one daily email of programming news, new tools, and web development links, each with a one-paragraph summary. It is aggregation, not commentary, tuned for working developers across the stack. Best for engineers who want the day's dev news skimmed in five minutes.
Last Week in AWS
Corey Quinn (The Duckbill Group)
- Free
- Weekly
Corey Quinn's snarky weekly roundup of AWS announcements and cloud-industry news, written from his perspective as a cloud economist.
Why DevOps and site reliability engineers read it
Corey Quinn's weekly round-up of AWS announcements and cloud-industry news, written by a cloud economist with an eye for what a change actually costs. It is the rare source that treats cloud spend as an engineering concern rather than a finance one.
More about this newsletter
A weekly digest of AWS news, releases, and security items with Quinn's trademark sarcastic commentary; the pitch is taming the 'drinking from a firehose' pace of AWS announcements. Quinn is Chief Cloud Economist at The Duckbill Group, an AWS cost-optimization consultancy, and also hosts the AWS Morning Brief and Screaming in the Cloud podcasts. Free.
You May Also Like
- Software EngineersThe occupation most reliability work is actually counted in, so this is the honest picture of the pay band, the hiring process and the specialisms either side of infrastructure.
- Cybersecurity ProfessionalsShares your tooling and most of your incident process, and the information security analyst occupation is projected to grow 21 percent, the fastest of the adjacent computing roles.
- Data EngineersPipelines with a different payload. Useful if the part of this job you enjoy is building durable systems rather than carrying a pager for them.
- CTOs and Engineering LeadersWhere the management track ends up, covering the budget, vendor and headcount decisions that set how humane any on-call rotation is allowed to be.
Frequently Asked Questions
Entry-Level
What is the difference between a DevOps engineer and a site reliability engineer?
Google's own framing is the clearest answer: SRE implements DevOps. DevOps is a broad philosophy, usually summarised as culture, automation, lean, measurement and sharing, and it says relatively little about how a particular service is operated. Site reliability engineering is a concrete, opinionated job: operations is treated as a software problem, the service is managed to a service level objective, toil is capped below half the week, ownership is shared with developers, and the team holds the authority to slow releases when the objective is at risk. In practice a DevOps role is defined by the delivery path and an SRE role is defined by a number.
How does platform engineering differ from DevOps and cloud engineering?
By who the user is. DORA defines platform engineering as a sociotechnical discipline whose output is an internal developer platform, described as an internal product designed specifically for developers, whose main goal is hiding infrastructure complexity behind golden paths. The CNCF platforms white paper adds the attributes: run like a product, consistent interfaces, self-service, documented, secure by default, adoptable in parts. Cloud engineering is the layer underneath, provisioning compute, networking, storage and identity and owning the bill. A DevOps engineer owns how change reaches production. A platform engineer's customers are other engineers.
Is DevOps and site reliability engineering a good career in 2026 and beyond?
The federal numbers favour the software-leaning end of it. Software developers, where most of this work is counted, recorded 1,717,800 jobs in 2025 at a median of $135,980 with 10 percent projected growth to 2035. Computer and information systems managers sit at $175,140 and 16 percent growth. The warning sign is the opposite direction: network and computer systems administrators, 323,600 jobs at $99,130, are projected to decline 4 percent. So the career is strong, but the direction of travel runs out of administration and into software, platform and management work.
What qualifications do you need to get into DevOps or SRE work?
There is no licence and no single required degree. The Bureau of Labor Statistics lists a bachelor's degree as the typical entry-level education for software developers, network architects and information security analysts, while network support specialists typically need an associate's degree and may also qualify with a high school diploma plus relevant IT certifications. In practice employers hire on evidence that you can operate something: infrastructure you declared as code, a service you ran, an incident you can describe honestly. Certifications substitute for a degree more readily here than in most engineering fields.
What do SLIs, SLOs and error budgets actually mean?
A service level indicator is a carefully defined quantitative measure of some aspect of the service, such as request latency or the fraction of well-formed requests that succeed. A service level objective is a target value or range for that indicator. A service level agreement is a contract with users carrying consequences, usually financial, for missing those objectives, and the test for telling the last two apart is whether a miss has an explicit consequence. The error budget is the gap between the objective and measured reality: while it remains, releases proceed, and when unreliability consumes it, releases slow or pause.
Which first jobs lead into DevOps and reliability engineering?
Three routes are common. Operations-side roles such as computer network support specialist, at a $76,220 median and 152,500 jobs, give you production exposure early but sit in an occupation with only 1 percent projected growth, so treat them as a doorway rather than a destination. A junior software engineering role gets you into the better-paid occupation sooner and lets you join a rotation with a mentor. A cloud or infrastructure engineer post sits between the two. Whichever you take, the thing that moves you on is replacing manual work with code.
Do you need to learn Kubernetes to get hired, and how deep should you go?
Deep enough to debug it, which is not the same as deep enough to build it. The Certified Kubernetes Administrator exam is a fair map of employer expectations and its weighting is instructive: troubleshooting is the single largest domain at 30 percent, cluster architecture and configuration 25 percent, services and networking 20 percent, workloads and scheduling 15 percent and storage 10 percent. It is a hands-on, command-line, two-hour proctored exam costing $445 with one free retake. Being able to read pod events and container logs under pressure matters more at interview than knowing the control plane internals.
Mid-Level
How much do DevOps engineers and SREs earn, and which parts of the field pay most?
Pay tracks which occupation you are counted in. The May 2025 medians are $76,220 for computer network support specialists, $99,130 for network and computer systems administrators, $129,180 for information security analysts, $134,050 for computer network architects, $135,980 for software developers and $175,140 for computer and information systems managers. The practical consequence is that the largest single raise available in this field is usually not a performance review. It is being reclassified from operations into software, or into management, which is a roughly $37,000 and $75,000 step respectively against the administration median.
What does on-call actually involve, and how do you tell a humane rotation from a bad one?
Ask for the numbers, because the published model has them. Handling one incident including analysis and follow-up averages about six hours, which caps a sustainable rotation at roughly two incidents per 12-hour shift. The paging distribution should be flat with a median of zero pages a day, and a median above one a day is treated as unsustainable. A single-site rotation wants at least eight engineers, or six per site across two sites. Operational work should stay under half of each engineer's time, with on-call no more than a quarter of it. A team that cannot answer those questions has not measured them.
How does incident response work, and what is an incident commander?
Serious incidents are run on a structure borrowed from emergency services. The incident commander holds the high-level state and assigns every role they have not delegated. An operations role is the only group permitted to modify the system. A communications lead is the public face, issuing updates and keeping the live document current. A planning role handles the longer tail: filing bugs, arranging handoffs and tracking changes so they can be reverted. The declaration bar is deliberately low: if you need a second team, if customers can see it, or if an hour of concentrated analysis has not solved it, declare. The priority order is stop the bleeding, restore service, preserve the evidence.
What is toil, and why is there a fifty percent cap on it?
Toil is operational work that is manual, repetitive, automatable, tactical and interrupt-driven, carries no enduring value and scales linearly with the service. It is defined by those properties rather than by whether you enjoy it. The cap exists because the whole premise of the role is that operations is a software problem, so at least half of each engineer's time has to be available for engineering project work. Google's own quarterly surveys report an average of about 33 percent toil, with individuals reporting anywhere between 0 and 80 percent, which is worth knowing because the advertised cap and the lived reality are different numbers.
Which DevOps and cloud certifications are worth the money?
The ones employers screen on, and the specifics are published. Certified Kubernetes Administrator: $445 with one free retake, two hours, hands-on. AWS Certified DevOps Engineer Professional: $300, 180 minutes, 75 questions, with two or more years of AWS provisioning and operations recommended. Google Professional Cloud DevOps Engineer: $200, two hours, 50 to 60 questions, recommending three or more years of industry experience and explicitly assessing site reliability engineering practices. Watch the churn at associate level: AWS retired SysOps Administrator Associate on 29 September 2025 and replaced it with CloudOps Engineer Associate at $150 for 130 minutes.
How should you prepare for a DevOps or SRE interview?
Expect four kinds of question and prepare one answer each. A definitional one, where you distinguish DevOps from SRE and reach for objectives rather than culture. A live debugging one, where you narrow by measurement and blast radius before naming a component. An incident story, where you mitigate before you diagnose and say who you escalated to. And a design question, usually about setting an objective or making a release safe, where you should name small batches, canaries, feature flags, a rehearsed rollback and the error budget. Have real numbers for the toil you removed.
What does a typical day look like, and what does an incident do to one?
The planned shape depends on the role. A DevOps engineer spends most of it on other teams' releases: pipeline health, a nervous deployment, an infrastructure-as-code review, then a release window. A platform engineer runs closer to product work, with intake, build time, office hours and a scorecard review. An on-call SRE plans for handover then project work. An incident takes the rest. Because one incident including root-cause analysis and follow-up averages about six hours, a single page at midday reliably consumes the afternoon, the postmortem draft and whatever was planned for the next day.
Senior-Level
What skills do employers expect from a senior reliability or platform engineer?
Four things beyond depth in the tooling. Platform product thinking: treating the platform as an internal product with golden paths, self-service, secure defaults and real documentation. Capacity and cost engineering, because cloud architecture decisions are repriced by the provider rather than by you. Governance of automation, which now means scoped credentials, bounded blast radius, approval gates and audit trails for anything acting on production. And the ability to argue reliability in the language of risk, cost and release velocity, which is what the error budget was designed to make possible.
How do you move from SRE into platform engineering, architecture or management?
They are three different labour markets. Platform work is a lateral move that changes your customer from a service to other engineers, and the qualification is credibility rather than a credential. Architecture is the nearest counted occupation at $134,050, 181,800 jobs and 8 percent projected growth. Management is the largest step and a change of profession: computer and information systems managers are a 685,800-job occupation at $175,140, growing 16 percent to 2035 with about 53,500 openings a year, where the work becomes hiring, budget, vendors and the on-call contract rather than the systems themselves.
What opportunities exist beyond running production systems?
Several, and most are under-competed because they are not separately counted in the federal statistics. Internal developer platform ownership is the largest, with 90 percent of organisations reporting a platform and 76 percent running dedicated teams. Beyond that: developer experience and productivity engineering, cloud cost and capacity work, security engineering, where the information security analyst occupation is growing 21 percent, solutions and reliability architecture, observability vendor and consulting roles, and the open-source project work that makes an external reputation. Each keeps the systems knowledge and drops the pager.
How is AI changing DevOps and site reliability work?
It has changed the ratio, not the job. The 2025 DORA research, from nearly 5,000 technology professionals, found 90 percent using AI at work and more than 80 percent believing it raised their productivity, with 30 percent reporting little or no trust in the code it produces. Critically, it observed a positive relationship between AI adoption and delivery throughput and a continuing negative relationship with delivery stability. AI made change cheap to produce and did nothing to make it safe to release, so the cost lands on whoever owns production, and the response is the control system: test automation, small batches, progressive delivery and fast rollback.
What should you put in place before giving an AI agent production access?
Treat it as an operator with no judgement rather than as a tool. Scoped, short-lived credentials instead of a standing role; a bounded blast radius so the worst outcome is one service in one environment; approval gates on anything destructive or cross-cutting; and an audit trail that records what it did and why. Then the inputs, which teams routinely forget: an agent reads the service catalogue, the ownership graph and the runbooks, so a confidently wrong runbook stops being a documentation problem and becomes an operational hazard. This is also the argument for a good platform, which is where those controls live.
What is the structural risk in a DevOps and SRE career?
Being counted in the wrong occupation. Network and computer systems administration, the historical home of this work, is projected to decline 4 percent to 2035 at a median of $99,130 with about 13,400 openings a year, while software development grows 10 percent at $135,980. The same person doing similar work is paid and projected very differently depending on whether the employer files the role under administration or under software. The second risk is reliability work that is funded only after an outage, which is what the error budget and a balanced platform scorecard exist to prevent.
How do you build and justify an internal developer platform to leadership?
Build it as a product and justify it with DORA's result. Start by paving the single path most teams already walk badly, usually getting a new service into production, end to end and self-service, with documentation and templates, and let teams adopt the parts they need. Then measure it on a balanced scorecard of delivery metrics and developer satisfaction, because a poorly managed platform reduces throughput and change stability. The justification leadership responds to is the research finding: where platform quality is high, AI adoption's effect on organisational performance is strong and positive, and where it is low that effect is negligible.
Get Tomorrow's DevOps and SRE Briefing
DevOps Weekly has been curating this field since 2010 and SRE Weekly since 2015, which means the patterns your peers treat as obvious were usually explained there first. TLDR Dev reaches nearly half a million engineers daily. Showing up to an incident review having never read about that failure mode is a choice.