DevOps, SRE and platform titles, untangled
Updated
Three names for overlapping work: practices, reliability math and internal products, and how to pick your lane.
Job boards treat DevOps, SRE and platform as different species. In practice they overlap heavily: all three ship software, carry pagers and automate toil. The names mark emphases, and knowing the emphasis helps you pick work you enjoy.
Three emphases
DevOps: the practice. Small releases, owned operations, fast feedback across dev and ops. Culture plus automation, applicable in a five-person team.
SRE: reliability with math. Error budgets, SLIs and SLOs turn reliability into decisions: when to ship features versus harden. Needs enough traffic for statistics to mean something.
Platform: leverage for others. Build the paved path: templates, pipelines and environments product teams adopt voluntarily. Success is measured in other teams' speed.
Worked example: a fictional career fork
The context below is fictional. Fictional engineer Deniz (fictional) loves firefighting and measurement in equal parts. Year one in a DevOps-titled role builds deploy discipline; year two adds SLOs and error budgets to settle ship-versus-harden fights; year three turns the accumulated scripts into a small internal platform two teams adopt.
No title change was the point. Each emphasis stacked on the previous, and the resume tells a story of widening leverage.
Decision table: pick your lane
| You enjoy | Lane | First proof |
|---|---|---|
| Shipping calmly | DevOps practice | Gated pipeline plus calm releases |
| Measuring trade-offs | SRE | One SLO with an error budget policy |
| Multiplying others | Platform | One adopted template or pipeline |
Related reading
- Start with practice: What is DevOps really.
- The program behind the practice: DevOps program.
Straight answers
Frequently asked questions
DevOps or SRE, which first?
DevOps practices first: they apply everywhere. SRE math matters once you have traffic worth budgeting.
What does platform engineering add?
Internal products: paved paths other teams choose. It turns tribal knowledge into self-service.
Which title should I chase?
Chase the work, not the title: shipping, reliability and leverage. Titles converge; skills transfer.