Role Pack · Mid to Senior
DevOps / SRE Interview Pack
CI/CD, containers, Kubernetes, IaC, observability, SLOs and incident response.
The reliability questions: pipelines, containers, orchestration, infrastructure as code, SLOs and on-call.
- Questions
- 360
- Topics
- 20
- Pages
- 263pages
- 360 questions, every one with a model answer
- CI/CD + Kubernetes cheat sheet
- SLO & error-budget framework
- Incident response playbook
Get the DevOps / SRE Interview Pack — $9
One-off. Delivered as a PDF by email the moment payment clears.
Prices shown are a USD base. Your local-market price is calculated at checkout in your own currency, plus any local sales tax.
What is inside
20 chapters, in the order the interviews tend to ask them:
- Defining SLIs, SLOs and error budgets
- Choosing targets and running on the error budget
- Signals, instrumentation and designing for debuggability
- Metrics, label cardinality and retention
- Logs, structure, sampling and retention
- Distributed tracing and context propagation
- Symptom based alerting and paging policy
- Incident command, on-call and handover
- Postmortems and the learning loop
- Overload, load shedding and cascading failure
- Linux runtime, cgroups and resource limits
- Container images, builds and supply chain integrity
- Kubernetes core workload objects and rollouts
- Services, DNS, ingress and network policy
- Probes, configuration and secret management
- Autoscaling, capacity planning and cost controls
- Storage, stateful workloads and recovery testing
- CI/CD delivery pipelines and GitOps reconciliation
- Infrastructure as code, state and drift
- Platform security hardening and policy enforcement
How the answers are built
Each chapter opens with the checklist the question is really testing. A few from this pack:
- An SLI measures a user visible property such as the proportion of requests that succeeded.
- A target should be set from the business cost of downtime, then negotiated rather than declared by engineering.
- Metrics answer whether something is wrong, traces explain where, and logs give the detail of a single request.
- Series count is the product of label value combinations, so cardinality is a design budget rather than an afterthought.
- Structured logs turn free text into queryable fields, which is what makes aggregation and alerting possible.
- A span carries a trace identifier, a parent reference, a name, timing and attributes that describe one operation.
Questions this pack covers
- How would you choose a service level indicator for checkout?
- Why does request success rate beat CPU utilisation as an indicator?
- How do you justify a 99.9 target to a sceptical executive?
- What burn rate should trigger a page rather than a ticket?
- Which signal answers a question the other two cannot?
- Why is user identifier labelling a metrics outage waiting to happen?
- How do you calculate the series count for a label set?
- Why does adding a status code label multiply cost?
Each one is answered in full in the pack, with the reasoning written out rather than a bullet list.
About this pack
- How many questions?
- 360, spread across 20 topics, written out in full across 263 pages.
- Do the answers just list keywords?
- No. Each answer is written as prose, because that is what you have to reproduce when someone asks you the question.
- How do I get it?
- Pay once and the PDF arrives by email immediately, with a signed download link.
- Can I get it refunded?
- Yes, if it is not what you expected. See the refund policy.
