finds.dev

NotHarshhaa/DevOps-Interview-Questions

Collection of 2,200+ DevOps, SRE & Platform Engineering interview questions with in-depth answers covering CI/CD, GitOps, Cloud (AWS, Azure, GCP), Kubernetes, Terraform, OpenTofu, Linux, Observability (OTel/Prometheus), Security, System Design & Incident Debugging. Perfect for all experience levels! 🌟🚀

View on GitHubHomepage ↗

★ 1,286updated Aug 2026

// the take

A large, topic-organized collection of DevOps/SRE/platform engineering interview questions and answers, split into modules (CI/CD, Kubernetes, cloud, IaC, observability, security, Linux, scripting, Git, system design). Aimed at anyone prepping for a DevOps or SRE interview, from junior through senior/lead system-design rounds.

Covers a genuinely wide span of the job, including current tooling (OpenTofu, Cilium/eBPF, Karpenter, SLSA/SBOM, OTel) rather than just the usual Docker/Jenkins basics. It goes beyond flashcard Q&A into mock interview scenarios and live-outage triage questions (504s, OOM, DNS storms), which is closer to what a real interview loop tests. Split into per-topic README files instead of one giant document, so you can jump straight to the section you need. Push history shows it's still being updated, not a one-and-done dump.

At 2,200+ answers there's no visible review or fact-checking process beyond a generic CONTRIBUTING guide, so correctness and depth almost certainly vary a lot between questions and between contributors — nothing here gives you confidence any individual answer is right. The docs/ folder is a pile of unrelated PDFs scraped from elsewhere (multiple overlapping 'DevOps Interview Questions' PDFs, random HR-round and job-interview-tips PDFs) with no attribution, which says more about how this was assembled than about its quality. It's a reference/cram list, not a practice tool — there's no way to test yourself, track what you've answered, or get feedback, so it's easy to pattern-match answers without being able to actually do the thing in an interview. Being crowd-sourced and un-versioned per answer, cloud-specific or version-specific content (AWS/Azure/GCP features, Terraform behavior) will quietly go stale with no way to tell which entries are outdated.

We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →

// at a glance

Stars
1,286
Forks
934
Last commit
28 Aug 2026

// nearby

If DevOps-Interview-Questions isn't quite it.

All repos →