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, FreeFree
See 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

    152,500 jobs · +1% to 2035

  • Network and computer systems administrators

    $99,130

    323,600 jobs · -4% to 2035

  • Information security analysts

    $129,180

    192,900 jobs · +21% to 2035

  • Computer network architects

    $134,050

    181,800 jobs · +8% to 2035

  • Software developers

    $135,980

    1,717,800 jobs · +10% to 2035

  • Computer and information systems managers

    $175,140

    685,800 jobs · +16% to 2035

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.

  1. Network or Cloud Support0 to 2 yearsTickets, monitoring and runbooks. Median $76,220. Measured on reliability of execution, not range.
  2. Systems Administrator2 to 4 yearsOwn real systems at $99,130 median, and start replacing manual steps with code before the occupation shrinks under you.
  3. DevOps Engineer4 to 7 yearsOwn the pipeline end to end. Usually counted as a software developer, where the median is $135,980.
  4. 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.
  1. 08:30Handover and alert triage: what fired overnight, what was acknowledged, and what is still unexplained.
  2. 09:30Access requests, certificate renewals and patching. The work that is obviously toil by the published definition.
  3. 11:30Shadow a senior engineer on a real diagnosis. This is how the pattern library gets built.
  4. 14:00Write or correct a runbook for the thing you had to ask about this morning.
  5. 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.
  1. 09:00Check pipeline health: failing builds, flaky tests, queue depth, anything blocking a team from shipping.
  2. 10:00Pair with a product team on a deployment they are nervous about. Canary, flag, rollback path confirmed.
  3. 12:30Infrastructure as code review. Someone has hand-edited a console setting and the plan now disagrees.
  4. 14:00Project work: shorten change lead time on the slowest pipeline, measured before and after.
  5. 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.
  1. 09:00On-call handover: open issues, anything degraded, and how much error budget the quarter has left.
  2. 10:00Planned engineering work, because at least half the week is supposed to be project time rather than operations.
  3. 11:40Page. Acknowledge inside the target, confirm customer impact, and declare an incident early rather than late.
  4. 11:55Stop the bleeding: shift traffic, roll back the suspect change, and keep the live document current.
  5. 13:30Service restored. Hand off command if you are now tired, and preserve the evidence for root-causing.
  6. 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.
  1. 09:00Read the platform's own support channel. Repeated questions are a design defect, not a documentation gap.
  2. 10:30Build: extend the service template so a new service reaches production without a human in the loop.
  3. 13:00Office hours with a team that wants an exception. Decide whether to pave it or refuse it.
  4. 15:00Review the scorecard: delivery metrics alongside developer satisfaction, because a platform can slow teams down.
  5. 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.
  1. 08:30Review the week's incidents across the estate, looking for the failure mode that repeats in three places.
  2. 10:00Design review on a new service. Blast radius, dependency failure modes, and what degrades instead of erroring.
  3. 12:00Objective setting with a product director: what the target should be, and the consequence of missing it.
  4. 14:00Postmortem review session. An unreviewed postmortem might as well never have existed.
  5. 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.

Sources:

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.

Sources:

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.

Sources:

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.

Source:

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

Processes, file descriptors, memory, networking and what a kernel is actually doing when a request is slow. Every abstraction above this leaks, and the engineer who can read the leak is the one who finishes the incident.

Source:

Infrastructure as code

Declaring infrastructure in version-controlled configuration rather than clicking it into a console. DORA treats version control and deployment automation as core capabilities, and a self-service platform cannot exist without them.

Sources:

Containers and Kubernetes

The CKA exam is a fair map of what employers assume: cluster architecture and configuration at 25 percent, workloads and scheduling 15, services and networking 20, storage 10, and troubleshooting the largest single domain at 30 percent.

Source:

Scripting plus one real language

SRE's first principle is that operations is a software problem, which is why the role expects you to build rather than only configure. Shell is table stakes; a language you can write a service and a test suite in is what moves you out of the administration pay band.

Sources:

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.

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

  1. Curated from the best newsletters

    Hark's editorial team handpicks the sources worth following. See how we rank

  2. The news that matters in 5 minutes

    Hark distills the most important stories into a concise audio briefing.

  3. Texted to you every morning

    You set the time and listen when you want.

  4. 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

  1. 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.

    Listen to DevOps Weekly free

    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.

  2. 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.

    Listen to SRE Weekly free

    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
  1. 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.

    Listen to TLDR Dev free

    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.

  2. 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.

    Listen to Last Week in AWS free

    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.

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.

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.