How do SRE and DevOps relate?
whether you see SRE as a concrete implementation of DevOps principles, not a rival.
DevOps is a broad culture of breaking down silos; SRE is one prescriptive way to do it with specific practices.
WHAT THIS TESTS The interviewer wants to see whether you understand the conceptual relationship rather than reciting buzzwords, and whether you can articulate that one is a philosophy and the other a concrete practice that realizes it.
A GOOD ANSWER COVERS Frame DevOps as a broad cultural philosophy: reduce silos between development and operations, accept that failure is normal, implement change gradually, leverage tooling and automation, and measure everything. Then frame SRE as a specific, prescriptive implementation of that philosophy that predates the popular DevOps term at Google. SRE supplies concrete practices: defining SLIs and SLOs, allocating error budgets that balance velocity against reliability, conducting blameless postmortems, capping toil, and sharing on-call between dev and ops. Use the analogy that SRE is to DevOps as a concrete class is to an interface, one possible implementation of the abstract principles.
COMMON WRONG ANSWERS Saying they compete or that an organization must choose one. Saying they are identical. Reducing DevOps to a job title or a CI/CD tool, or reducing SRE to a renamed ops team.
LIKELY FOLLOW-UPS Which DevOps pillar does the error budget address? Can a company do DevOps without SRE, or SRE without DevOps language? Where do the two diverge in practice?
ONE CONCRETE EXAMPLE A company embraces the DevOps principle that failure is normal and feedback loops should be short. SRE makes that actionable: it sets an SLO and an error budget so the team has a quantified, shared definition of acceptable failure, and uses blameless postmortems to feed lessons back quickly. The abstract DevOps value gains a measurable mechanism, demonstrating that SRE enables and operationalizes DevOps rather than opposing it.
Interview question
Which statement best captures the relationship between SRE and DevOps?
- a.SRE is a prescriptive implementation of the broader DevOps philosophyCorrect
- b.SRE and DevOps are identical with no meaningful distinction
- c.They are competing philosophies and an organization must choose one
- d.DevOps is simply the name for an SRE team's CI/CD pipeline
Why? this is the answer
SRE provides concrete practices, SLOs, error budgets, blameless postmortems, that implement the abstract DevOps principles. They are complementary, not competing, and they operate at different levels of abstraction.
Just read this? Test yourself on what you have been reading.
Read the original → sre.google
- #sre
- #devops
- #culture
- #error-budget
- #interview
Put your scrolling time to good use
Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on sre — each one lists the topics its interview covers.
See open roles