How do SRE and DevOps relate?

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.