DevOps Engineer interview questions
Grouped by interview stage, with what a strong answer actually sounds like — the part most question lists leave out.
When interviewing a devops engineer, structure questions by stage and assess against the role's actual requirements. DevOps engineers build and run the infrastructure and delivery pipelines other engineers depend on. The questions below cover screening through final round, each with what a strong answer sounds like and the warning signs of a weak one.
How to use these
Pick four to six for a 45-minute interview — not all 7. A well-followed-up question takes six to eight minutes, and the information is almost always in the follow-up rather than the first answer. Ask the same core questions of every candidate so you can actually compare them; vary the follow-ups.
Screening questions
Walk me through what happens when an engineer merges to main in your current setup.
Why ask it: Reveals the real maturity of their environment quickly.
A strong answer: Concrete pipeline with gates, rollback path and observability at each step.
A weak answer: Vague, or a manual process they have not tried to improve.
Tell me about the worst outage you were part of.
Why ask it: Outages are where infrastructure judgement is formed.
A strong answer: Timeline, mitigation before root cause, blameless follow-up that changed something.
A weak answer: Blames a person, or no lasting change resulted.
Technical questions
How do you make deploys safe to roll back?
Why ask it: Reversibility is the highest-leverage property of a delivery system.
A strong answer: Backwards-compatible migrations, feature flags, decoupling deploy from release.
A weak answer: Restore a database backup — which usually means losing data.
How do you approach cloud cost?
Why ask it: Frequently ignored until it becomes urgent, and highly visible to leadership.
A strong answer: Attribution by team or service, rightsizing, spotting waste before it compounds.
A weak answer: Not their problem.
What is your view on how much platform teams should abstract from product engineers?
Why ask it: Tests judgement about internal tooling, where over-abstraction is a common failure.
A strong answer: Paved road with escape hatches; abstraction where it removes real toil.
A weak answer: Abstract everything, or nothing.
Final questions
How do you handle being the bottleneck for other teams?
Why ask it: Platform teams almost always become one, and how they respond determines whether they help or hinder.
A strong answer: Self-service, documentation, and being explicit about queue and priority.
A weak answer: Absorbs everything until burnt out, or gatekeeps.
What is on-call like where you are now, and what would you change?
Why ask it: Reveals both their experience and their standards.
A strong answer: Specific about alert volume, rotation fairness and follow-up discipline.
A weak answer: Has never been on call for something they built.
Red flags for this role
- Infrastructure entirely click-configured with no code
- No incident experience
- Dismissive of developer experience
What a devops engineer actually does
DevOps engineers build and run the infrastructure and delivery pipelines other engineers depend on. The role is judged on reliability, deployment speed and how much friction the rest of engineering experiences.
See the full devops engineer job description, including how to assess each requirement.
Generate questions specific to your role — and that account for what previous interviewers already asked — with the free interview question generator.