DevOpsInterviewPrep logo

DevOps Interview Questions & Answers

A curated, continuously updated set of 510 DevOps interview questions with worked answers, organised by topic and by company. Every answer carries the same four things: how to open, the substance, the follow-up the interviewer is holding in reserve, and the answer that sounds reasonable and fails the round. Written for DevOps, SRE and platform engineering loops from the graduate screen to the staff design round.

510 questions12 topics32 companiesupdated 2026

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.

What a DevOps interview actually tests

Five dimensions, and they are not equally weighted. Most preparation goes into the one that carries the least weight.

  • Production troubleshooting

    The round that decides most loops, and the one candidates prepare least. A broken system you did not build, incomplete information, and a score for how you narrow the search space rather than for the answer.

  • Infrastructure design under constraint

    Capacity, failure domains and blast radius, with arithmetic before architecture. When the prompt contains a number, that number is the question.

  • Tool depth beneath the abstraction

    Not what a Deployment is. Why a StatefulSet will not reschedule, what Terraform state actually maps, what the kernel did when the container died.

  • Automation and coding

    Real code in a shared editor. Idempotence, streaming a large input, and error handling matter more than algorithmic cleverness.

  • Ownership and communication

    An outage you commanded, a decision you lost, a risk you quantified for someone who does not write code. At staff level this is roughly half the loop.

Linux & Networking Interview Questions for DevOps

Signals and the OOM killer, cgroups v2 and namespaces, systemd, /proc, TCP states and TIME_WAIT, DNS resolution order, and the Bash/Python/Go a Google SRE or Meta PE screen actually asks you to write.

See all 46 Linux, Networking & Scripting questions with answers →

AWS & Cloud Architecture Interview Questions

IAM least privilege, VPC design, security groups versus NACLs, why peering is not transitive, Transit Gateway routing, multi-account landing zones and multi-region failover across AWS, Azure and GCP.

See all 48 Cloud Platforms & Architecture questions with answers →

Terraform & Infrastructure as Code Interview Questions

Terraform and OpenTofu state, remote backends and locking, drift detection, count versus for_each, module design, lifecycle blocks, Ansible idempotence, and the BUSL license split every interviewer now probes.

See all 38 Infrastructure as Code & Configuration questions with answers →

Kubernetes & Docker Interview Questions

Control plane internals, the full kubectl apply to running pod path, scheduling and affinity, native sidecars, in-place pod resize, CNI and network policy, CSI and StatefulSet identity, RBAC, operators and service mesh.

See all 66 Containers & Kubernetes questions with answers →

CI/CD, Jenkins & GitOps Interview Questions

Pipeline design and caching, artifact promotion, rolling versus blue-green versus canary and what each costs, progressive delivery with Argo Rollouts and Flagger, ArgoCD and Flux reconciliation, and the DORA metrics behind them.

See all 46 CI/CD, Release Engineering & GitOps questions with answers →

SRE, Prometheus & Observability Interview Questions

Metrics versus logs versus traces, PromQL, Prometheus cardinality blowups, OpenTelemetry collectors and temporality, exemplars, SLI and SLO design, error budget math, and burn-rate alerting that survives an on-call rotation.

See all 42 Observability, SLOs & Reliability questions with answers →

DevOps Scenario-Based & Troubleshooting Interview Questions

The highest-signal round on the loop. CrashLoopBackOff with empty logs, exit code 137, ImagePullBackOff, stuck PVC finalizers, 503s from a healthy-looking service, p99 tails, incident command, and the blameless postmortem.

See all 55 Incident Response & Production Debugging questions with answers →

DevSecOps & Supply Chain Security Interview Questions

SAST, DAST, SCA and IAST placement in a pipeline, Trivy and Checkov gates, secrets management and rotation with Vault, image signing and SLSA provenance, zero trust in Kubernetes, and compliance as code.

See all 38 DevSecOps & Supply Chain Security questions with answers →

DevOps System Design Interview Questions

Google-style NALSD with napkin math before boxes, multi-region active-active, disaster recovery under a real RTO, capacity planning, blast radius, and designing a delivery platform for hundreds of services.

See all 41 DevOps System Design & Architecture questions with answers →

Platform Engineering & FinOps Interview Questions

Internal developer platforms, golden paths, Backstage catalogs and templates, Crossplane, self-service without a ticket queue, plus cost allocation, showback, Karpenter, spot strategy and commitment management.

See all 19 Platform Engineering & FinOps questions with answers →

MLOps & GPU Infrastructure Interview Questions

The fastest-growing DevOps sub-domain: GPU scheduling with MIG, time-slicing and DRA, vLLM paged attention and continuous batching, KServe and Ray, gang scheduling with Kueue, and the cost model behind inference.

See all 52 AI & GPU Infrastructure questions with answers →

DevOps Behavioral & Leadership Interview Questions

Amazon Leadership Principles in STAR form, the outage story that shows ownership rather than blame, pushing back on a bad deadline, driving a migration nobody wanted, and explaining risk to people who do not write code.

See all 19 Behavioral & Leadership questions with answers →

DevOps interview questions by company

Every company runs DevOps, so what matters is which kind of loop you are walking into. These pages break down the process round by round, compiled from public sources, each with an explicit confidence level.

Before the interview: the role itself

DevOps interview questions: FAQ

What questions are asked in a DevOps interview?

Five kinds, in roughly this order of weight: a troubleshooting scenario in a system you did not build, an infrastructure design question with a number in the prompt, a coding or automation exercise, tool depth across Linux, Kubernetes, Terraform and CI/CD, and a behavioral round about an outage you owned. Definitions appear in the screen and almost nowhere after it.

How do I prepare for a DevOps interview in one week?

Drill troubleshooting scenarios for your target stack, memorise the error budget arithmetic (99.9 percent is about 43 minutes a month), and write three behavioral stories properly with numbers in them. Skip revising tool breadth. It is the cheapest round to lose and the most expensive to cram.

What is the hardest round in a DevOps interview?

Troubleshooting, and it is also the least prepared. You are given a broken system with incomplete information and scored on whether you narrow the search space with evidence rather than guessing. The specific failure candidates make is proposing the fix that worked last time instead of stating a hypothesis and the observation that would rule it out.

What DevOps questions are asked for experienced candidates?

The tool questions get replaced by ownership questions. Expect Terraform state and drift rather than Terraform syntax, why a StatefulSet will not reschedule rather than what a Deployment is, how you would roll a change across a fleet, how you set an SLO with a team that does not want one, and what you would cut from a cloud bill first.

Are DevOps interviews the same as SRE interviews?

They overlap heavily and differ in weight. A DevOps loop leans toward pipelines, infrastructure as code and cloud architecture. An SRE loop leans toward Linux internals, reliability arithmetic and distributed systems, and at large companies it is interviewed against the software engineering ladder, which raises the coding bar.

Do I need coding for a DevOps interview?

Yes, and treating it as a formality is a common way to fail. The round is usually Python, Bash or Go, on something practical like parsing a log stream or calling an API. Interviewers watch for whether the script is safe to run twice, handles the empty input, and streams a large file rather than loading it into memory.

Is there a DevOps interview questions PDF?

One page holding every DevOps interview question on this site, grouped by topic and by company, each with its worked answer. It is regenerated as questions are added, which is the thing a downloaded PDF cannot do. Every entry links to the full answer rather than a one-line note.

Unlock every answer, including the follow-ups

510 questions across 12 topics, ordered easy to hard, each with a worked senior-engineer answer, the probe an interviewer holds back, and the mistake that fails the round. The first questions in every track are free.

Loops get revised constantly and differ by team, by level and by region. Prepare in this direction, then ask your recruiter what the rounds actually are.