FoundationWays of working

What does DevOps actually mean, and what problem was it invented to solve?

What they are really testing: Whether you have a point of view or just a tool list. Naming Jenkins and Docker here is a trap: they are asking about the organisational problem, and tools are the answer to a different question.

A real interview question

What does DevOps actually mean, and what problem was it invented to solve?

What most people say

drag me

DevOps is using tools like Jenkins, Docker, Kubernetes and Terraform to automate deployment.

It answers "what tools do you know" instead of the question asked. A team can run all four tools and still throw releases over a wall every 6 weeks, which is exactly the failure DevOps was named for.

The follow-ups they ask next

  • Is a dedicated DevOps team a contradiction then?

    It can be, if it becomes a new silo doing deployments for others. It works when it is a platform team building paved roads that product teams use themselves, so ownership stays with the builders.

  • How would you measure whether a team is actually doing this well?

    The DORA four: deployment frequency, lead time for change, change failure rate, time to restore. They capture both speed and stability, so you cannot game one by wrecking the other.

What the interviewer is listening for

  • Leads with incentives and ownership
  • Explains why small batches are safer
  • Treats tools as downstream of the idea

What sinks the answer

  • Recites a tool list
  • Cannot describe the pre-DevOps failure mode
  • Thinks DevOps means a job title that does deployments for other people

If you genuinely do not know

Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.

It exists because [devs were rewarded for change and ops for stability, which are opposing incentives]. That produced [big risky releases thrown over a wall]. The fix is [the team that builds it also runs it], and the tooling exists to [make small frequent changes safe and reversible].

Keep going with ways of working

All 87 devops engineer questions

Knowing the answer is not the same as recalling it under pressure

Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.

Start free