How would you introduce SRE practices in an organization where developers throw code over the wall to operations?
Short answer
Move to shared ownership: product teams own their services in production ("you build it, you run it") with SLOs and error budgets, an SRE/enabling team builds tooling and coaches, on-call is shared with fair rotations and support, blameless postmortems drive learning, and toil is measured and automated.
Detailed answer
Steps: pick pilot services; define SLOs with product owners; set up error-budget policy; give teams observability and runbooks via the platform; introduce shared on-call with SRE support and compensation; postmortems with tracked actions; measure toil and automate. Expand gradually.
What the interviewer expects
Cultural and organizational change plus concrete practices.
Common mistakes to avoid
Renaming the ops team "SRE" without changing ownership or practices.