DevOpsInterviewPrep logo

DEVOPS · SRE · PLATFORM ENGINEERING

Modern DevOps interview questions.
Answered in full.

510 of them, across 12 topics: Kubernetes, Terraform, Linux, cloud, CI/CD and the incident round, plus GPU and inference operations for roles that run AI workloads. Every one has a worked answer, the follow-up an interviewer asks next, and mistakes to watch for. Browse them by topic and by company, or start with today's, which is unlocked.

Start practising free →See what unlocking costs ↓

10 answers per topic open to anyone · $25 or ₹2,000, paid once, for 6 months · nothing renews

Not sure this is where to begin? Follow the map instead: the four stages of preparing, and which one your background already puts you in.

questions with worked answers
510
concepts, one idea each
33
answers carrying a diagram
230
company interview guides
32
notes from the contributor network
296

RESEARCHED FROM HIRING LOOPS AT

All 32 company guides →

WHY THIS BANK EXISTS

The five banks we reviewed cover Linux far more deeply than GPU operations.

Our review of 5 open-source DevOps question repositories found 657 distinct Linux prompts and two on AI infrastructure. The chart uses the corroborated subset: prompts also found in another repository or in our commissioned research. None of those two AI prompts met that corroboration rule.

This measures the selected repositories, not interview frequency. Our comparison uses editorial targets for a 300-question bank. Use your target role to choose which topics deserve the most time.

The 4 categories below our comparison threshold are where this bank spends its weight. There are 167 questions here across those categories.

Read the full argument →Go straight to the GPU questions →

CORROBORATED PROMPTS / OUR TARGET MIXour questions / target ratio
  • Linux, Networking & Scripting46 / 22.2×
  • Containers & Kubernetes66 / 15.2×
  • DevSecOps & Supply Chain Security38 / 10.5×
  • Cloud Platforms & Architecture48 / 10.3×
  • CI/CD, Release Engineering & GitOps46 / 10.0×
  • Infrastructure as Code & Configuration38 / 9.0×
  • Observability, SLOs & Reliability42 / 6.1×
  • Behavioral & Leadership19 / 4.2×
  • Platform Engineering & FinOps19 / 2.4×
  • DevOps System Design & Architecture41 / 2.3×
  • Incident Response & Production Debugging55 / 1.8×
  • AI & GPU Infrastructure52 / 0.0×

Bars show corroborated prompts divided by our editorial target for each topic, on a square-root scale. The tick is 1× our target; red marks ratios below our comparison threshold. The left figure counts questions written here today.

THE SHAPE OF EVERY ANSWER

Five parts, from the first decision to the follow-up.

Anyone can find the question. What decides the round is the reply: what you lead with, how deep you go before stopping, and whether you have already thought about the thing the panel asks next. So every answer here is assembled the same way, and 230 carry a diagram, because a scheduler decision or a request path is quicker to draw than to narrate.

Grounded in researched DevOps, SRE and platform engineering interview loops, written to a senior-engineer editorial bar, and never padded to hit a word count.

  1. 01TL;DRThe main decision and its assumptions, before the detailed explanation.
  2. 02How to approach itWhere to start, what to clarify, and which evidence to inspect first.
  3. 03A strong answerThe full working: the mechanism, the numbers that matter, the command you would actually run, and a diagram where one earns its place.
  4. 04What interviewers probe nextFollow-up questions with worked responses, so you can test the limits of your first answer.
  5. 05Common mistakesPlausible mistakes and the technical reasons they fail.
  6. No filler section exists. If a paragraph would sit just as well under a different question, it is cut before it ships.See it on a real answer →

FOUR WAYS IN

Four stages. The trick is knowing which one you are actually in.

  1. 01Start here →

    Orient. Find out what the loop actually contains.

    Preparation priorities and 32 company guides. 4 carry documented outlines; confirm the details for your role.

  2. 02Read the concepts →

    Understand. One idea per page, beneath the tooling.

    33 concepts across the 12 tracks the questions assume you already hold. Read the mechanism, then follow the links into practice.

  3. 03Open the bank →

    Practise. Work the questions in the order they get harder.

    510 questions, easy through expert within a topic. Nothing is left as a prompt: each carries the worked reply, the follow-up and the failure mode.

  4. 04See the courses →

    Build. Run the thing the interview is really about.

    4 courses with worked exercises and a final design or incident review. 4 lessons are free.

THE 12 TOPICS

Every topic, and how hard it gets inside each one.

easymediumhardexpert

PREMIUM

One payment for 6 months of full-library access.

  • ✓Every one of the 510 answers. Anyone gets 120; a free account raises that to 238; Premium is the remaining 272.
  • ✓All 33 concepts, with their worked explanations and practice links.
  • ✓The 32 company preparation guides, with evidence caveats and related practice.
  • ✓Mastery tracking that keeps a running estimate of what you recall per topic, and points at the weakest one.
  • ✓Content added during your 6 months is included. Hourly reading limits apply.
$25or ₹2,000
one payment · 6 months · no auto-renewal

Available payment methods are shown at checkout. The payment provider handles card details; this site does not store them. Nothing renews automatically. Access attaches to your Google account after the server confirms payment.

Unlock the whole bank →Or carry on free: 10 per topic now, 20 once you sign in

JUST ADDED

  1. Reliability work keeps losing to features. How do you change that?
  2. Tell me about an AI feature you shipped that did not work as promised. What did you do?
  3. How do you get engineers to report their own mistakes early instead of hiding them?
  4. A teammate keeps merging changes that skip tests and rubber-stamp reviews. How do you handle it?
  5. Tell me about harsh criticism you received in a performance review. What did you change as a result?
  6. Everything on your board is marked urgent by somebody. How do you decide what actually gets done this sprint?

THE REST OF THE SITE