Explaining DevOps: Why It Exists, Its Core Practices and How It Is Measured

As a candidate for a product manager role at Google, you are asked to explain DevOps. What is it, and what does it look like when a team actually works that way? ```hint Start from the friction Picture how software shipped when one group wrote the code and a different group kept it running in production, and ask what each group was rewarded for. Your definition should explain how DevOps changes that relationship, not just name tools. ``` ### Clarifying Questions - Should the answer stay at the level of culture and process, or also cover concrete practices such as deployment pipelines and infrastructure defined in code? - Do you want me to place DevOps next to Agile and Site Reliability Engineering, the operations approach Google is known for? - Are you interested in how DevOps changes a product manager's work, such as release planning and launch decisions? ### What a Strong Answer Covers - A crisp definition that treats DevOps as a mix of culture and practices rather than a tool, a team or a job title - The problem it was created to solve and the business outcomes it targets - The concrete practices that put it into effect across building, releasing and running software, illustrated with an example - How teams measure whether DevOps is working, and how it differs from Agile and SRE - What it changes for a PM, including release planning, experimentation and the balance between reliability work and new features ### Follow-up Questions - A team tells you it "does DevOps." What evidence would convince you that it ships faster and more safely than before? - Engineering wants to pause feature work for a quarter to automate deployments. How would you weigh that against the roadmap? - How does an error budget change the conversation between product and engineering about launching quickly?