DevOps/SRE Interview Guide
Answer the on-call questions with confidence — infrastructure design, incident-response scenarios, CI/CD pipeline design, and the reliability concepts SRE panels probe.
Product Preview
Try the interactive reader and demo tools below, or get the full product with all content unlocked.
Interactive Reader (Free Preview) ⚙ Try Demo Tools Download Free SampleFile Structure 8 files
Documentation Preview README excerpt
DevOps & SRE Interview Guide
110+ real interview questions with detailed answers, shell commands, YAML configs, and ASCII architecture diagrams for landing DevOps Engineer and Site Reliability Engineer roles at top tech companies.
Whether you're a sysadmin moving into DevOps, a developer shifting toward SRE, or a senior engineer preparing for staff-level reliability interviews — this guide gives you the technical depth, scenario-based practice, and structured study plan you need to walk in confident.
Table of Contents
- [What's Included](#whats-included)
- [How to Use This Guide](#how-to-use-this-guide)
- [File Index](#file-index)
- [Tips for Interview Day](#tips-for-interview-day)
- [FAQ](#faq)
- [Support](#support)
- [License](#license)
What's Included
| Category | Count | Description |
|---|---|---|
| Infrastructure & Cloud | 24 | Cloud architecture, networking, IaC (Terraform), containers, Kubernetes, load balancing |
| CI/CD Pipelines | 22 | Pipeline design, deployment strategies, artifact management, secrets handling, rollbacks |
| Incident Response | 20 | On-call scenarios, production debugging, severity triage, postmortems, blameless culture |
| Reliability Engineering | 22 | SLI/SLO/SLA, error budgets, observability, four golden signals, chaos engineering |
| Linux & Networking | 25 | Linux internals, process management, filesystems, DNS/TCP/HTTP, troubleshooting commands |
| Study Plan | 1 | 4-week structured prep plan with daily topics and self-assessment checkpoints |
| Total questions | 113 | Every question has a detailed answer with commands, configs, or diagrams |
How to Use This Guide
For Structured Prep (recommended)
1. Start with the study plan (study-plan/devops-sre-study-plan.md) — it maps out a 4-week schedule covering all five topic areas
2. Read each topic file front-to-back — questions progress from Junior to Senior difficulty within each file
3. Practice answering out loud — explaining technical concepts verbally is a different skill than reading about them
4. Run the commands — spin up a VM or use a cloud free tier to actually execute the shell commands and configs shown in answers
For Targeted Review
- Jump to a specific topic via the [File Index](#file-index) below
- Each file is self-contained — no need to read them in order
- Use
Ctrl+F/Cmd+Fto search for specific technologies (e.g., "Terraform", "Kubernetes", "TCP")
For Mock Interviews
1. Pick a random topic file
2. Have a friend read you 5-6 questions from mixed difficulty levels
3. Answer each one in 2-3 minutes (the way you would in a real interview)
4. Compare your answer to the guide's answer — note what you missed
5. Repeat with a different topic file the next day
File Index
... continues with setup instructions, usage examples, and more.
Content Sample questions/cicd-pipelines.md
CI/CD Pipelines
22 interview questions on pipeline design, deployment strategies, artifact management, secrets handling, and rollback patterns — with difficulty ratings, thorough answers, YAML examples, and ASCII diagrams.
Questions
Q1. What is the difference between Continuous Integration, Continuous Delivery, and Continuous Deployment?
Difficulty: Junior
Answer:
CI CD (Delivery) CD (Deployment)
┌──────────────────┐ ┌──────────────────┐ ┌──────────────────┐
│ Code commit │ │ Artifact ready │ │ Auto-deploy to │
│ ──► Build │ │ ──► Manual gate │ │ production │
│ ──► Unit tests │ │ ──► Deploy to │ │ (no human │
│ ──► Integration │ │ staging │ │ approval) │
│ tests │ │ ──► Approval │ │ │
│ ──► Artifact │ │ ──► Prod deploy │ │ │
└──────────────────┘ └──────────────────┘ └──────────────────┘
Merge to main Deployable at Deployed
multiple times/day any time automatically
- Continuous Integration: Developers merge code to a shared branch frequently (multiple times a day). Each merge triggers an automated build and test cycle. The goal: catch integration bugs early.
- Continuous Delivery: Every change that passes CI is automatically deployed to a staging environment and is ready to be deployed to production — but a human makes the final call.
- Continuous Deployment: Every change that passes all automated checks is deployed to production automatically. No human gate.
Key points:
- CI is the foundation — without it, the rest is meaningless
- Most teams do CI + Continuous Delivery (manual prod approval)
- Continuous Deployment requires very high confidence in your test suite
- The pipeline should get faster as you move right — fast tests first, slow tests later
Follow-up: "What test coverage and confidence level would you need before adopting Continuous Deployment?"
Q2. Design a CI/CD pipeline for a microservices application. Walk me through each stage.
Difficulty: Mid
Answer:
... and much more in the full download.