# Prometheus
All Prometheus notes →3 — Deep Dive Discussions
Interview-framed answers to the 'why' questions candidates get asked about Prometheus — why pull, why not SQL, why labels — honestly scoped to what this book actually has source material for.
1 — Prometheus System Design
Designing Prometheus-based monitoring at scale — multi-region topology, HA design, cost optimization, and capacity planning as a system-design interview prompt.
2 — Interview Questions
A seniority-tiered Prometheus/monitoring interview question bank, from beginner fundamentals through staff/architect-level system design and trade-off framing.
4 — Real Production Architectures
Worked case studies of real Prometheus deployment shapes — Kubernetes-native, multi-cluster, hybrid-cloud, multi-tenant, large-enterprise, and SaaS monitoring platform architectures.
# Ci Cd
All Ci Cd notes →1 — CI/CD Platform System Design
Covers how to approach a CI/CD platform system design interview end to end — see system-design's dedicated CI/CD platform case study for a fully worked example.
2 — Designing Enterprise Build Platforms
Covers the interview framing for designing a distributed build platform at enterprise scale — requirements, architecture, and trade-offs.
3 — Progressive Delivery Design
Covers the interview framing for designing a progressive delivery system — feature flags, traffic shifting, automated verification, and rollback.
4 — GitHub Actions Interview Questions
GitHub Actions interview questions graded beginner through principal, for calibrating depth expected at each level.
5 — Release Engineering Case Studies
Walks through worked release-engineering case studies — release trains, promotion pipelines, rollback design — in interview format.
6 — Staff/Principal Platform Engineering Scenarios
Covers open-ended staff/principal-level platform engineering scenarios that probe organizational, not just technical, judgment.
7 — GitHub Actions: Enterprise Scenarios
Covers designing a CI platform, securing multi-tenant pipelines, monorepo-at-scale builds, thousands of concurrent builds, and a global runner fleet as MAANG-style design prompts.
8 — GitHub Actions: Case Studies
Walks CI/CD platform design through real-world shaped case studies — SaaS, microservices, monolith, and enterprise migration.
# Data Engineering
All Data Engineering notes →1 — SQL Interview Problems
SQL interview problems by difficulty — easy, medium, and hard — with a dedicated focus on window function problems.
2 — Spark Interview Questions
Spark interview questions covering architecture, optimization techniques, debugging approaches, and performance tuning.
3 — Data Engineering System Design Interviews
How to run an open-ended data engineering system design interview — framing trade-offs, capacity estimation, and bottleneck analysis.
4 — Behavioral Interviews
Behavioral interview preparation framed around ownership, reliability, incident response, and leadership principles.
# Dbms
All Dbms notes →1 — Frequently Asked Interview Questions
Covers the recurring DBMS comparison questions asked in interviews — ACID vs BASE, clustered vs non-clustered indexes, B-tree vs B+-tree, 2PL vs MVCC, OLTP vs OLAP, and normalization vs denormalization.
2 — SQL Coding Interview
Covers a SQL coding interview practice set spanning easy through hard window-function and recursive SQL problems.
3 — Internal Architecture Deep Dive
Covers internals deep dives across PostgreSQL, MySQL InnoDB, Oracle, and SQL Server.
4 — Mock Interview Problems
Covers full mock-interview problem sets spanning theory, SQL, database design, performance, and troubleshooting.
# Infrastructure Platform Engineering
All Infrastructure Platform Engineering notes →1 — Infrastructure Platform System Design
Works through infrastructure platform system design at the MAANG Staff/Principal bar — control plane, execution plane, and multi-tenant trade-offs.
2 — Designing Self-Service Infrastructure
Works through a self-service infrastructure design exercise — catalog, request flow, guardrails, and approval automation.
3 — Terraform/OpenTofu Architecture Discussions
Covers interview-style discussion points on Terraform/OpenTofu architecture — module design, state, and pipeline trade-offs.
4 — Landing Zone Design Exercises
Works through landing zone design exercises for interview practice — account structure, governance, and network topology trade-offs.
5 — Infrastructure Governance Case Studies
Works through infrastructure governance case studies — policy as code, cost governance, and compliance trade-offs under interview conditions.
6 — Staff/Principal Infrastructure Scenarios
Covers open-ended Staff/Principal-level infrastructure platform scenarios that probe judgment under ambiguity and organizational constraints.
# Internal Developer Platforms
All Internal Developer Platforms notes →1 — Internal Developer Platform System Design
A worked IDP system-design prompt at the Staff/Principal bar: requirements, architecture, and the trade-offs an interviewer will probe.
2 — Designing Self-Service Platforms
A self-service-focused design exercise, distinct from the general IDP prompt, that probes provisioning workflows and approval boundaries specifically.
3 — Backstage Architecture Interview Questions
A question bank on Backstage's own architecture, catalog processing, scaffolder internals, plugin boundaries, for platform-engineering-flavored interviews.
4 — Golden Path Design Exercises
Whiteboard exercises for designing a golden path from scratch for a given workload shape under interview time pressure.
5 — Platform API Design Interviews
API design interview practice specific to platform resource, infrastructure, and event APIs.
6 — Staff/Principal Platform Engineering Case Studies
End-to-end case studies calibrated to the Staff/Principal (L6/L7) bar for platform engineering interviews.
# Kubernetes
All Kubernetes notes →1 — Kubernetes Design Questions
Why the strongest answer to a multi-tenant platform design question starts from isolation boundaries (namespace vs. cluster vs. node) rather than jumping straight to YAML.
2 — Kubernetes Troubleshooting Interviews
Why interviewers grade the diagnostic sequence (events, describe, logs, then metrics) more heavily than whether you name the eventual root cause.
3 — Kubernetes Internals Interviews
Why grasping the reconciliation loop (watch, diff, act) explains almost every 'why didn't my change take effect' internals question the interviewer can ask.
4 — Production Incident Walkthroughs
Why a credible incident narrative names the blast-radius containment step before the root cause, since sequencing is what separates senior candidates from mid-level ones.
5 — Leadership & Architecture Discussions
Why staff+ architecture interviews probe how you built cross-team consensus on a platform decision, not just whether the decision itself was technically correct.
6 — Common MAANG Kubernetes Questions
Why 'what happens when a pod is scheduled' and 'what happens when a node dies' stay the two highest-frequency questions because they force you to narrate the whole control plane.
7 — Whiteboard Exercises
Why whiteboard Kubernetes exercises reward drawing the control plane and data plane as separate boxes first, since conflating them is the most common early mistake.
8 — Final Revision Checklist
Why a pre-interview revision checklist should be organized by failure mode (scheduling, networking, storage, control plane) rather than by Kubernetes object type.
# Operating System
All Operating System notes →1 — Classic Interview Problems
Covers producer-consumer, readers-writers, dining philosophers, deadlock detection, memory allocation, page replacement, and scheduling problems as interview prompts.
2 — System Design Connections
Covers how threads in web servers, process models, database memory management, scheduler impact on latency, caching/paging, and storage systems connect back to OS fundamentals.
3 — Linux Interview Questions
Covers common Linux questions, debugging scenarios, process investigation, memory leak investigation, high CPU diagnosis, the OOM killer, and kernel panic basics.
4 — MAANG Interview Masterclass
Covers frequently asked questions, whiteboard explanations, common pitfalls, optimization techniques, and mock interview scenarios.
# Platform Engineering Fundamentals
All Platform Engineering Fundamentals notes →1 — Platform Engineering Fundamentals Interview Questions
A working set of fundamentals-level platform engineering interview questions and how to structure the answers.
2 — Architecture Trade-Off Discussions
Framing for architecture trade-off discussions specific to platform engineering interviews.
3 — Platform Design Case Studies
Worked platform design case studies in the style MAANG system-design interviews expect.
4 — Common Staff/Principal Platform Engineering Questions
Common Staff/Principal-level platform engineering interview questions and what differentiates a strong answer at that level.
5 — Whiteboard Exercises
Whiteboard exercises for practicing platform design live, under interview conditions.
6 — Platform Engineering Interview Cheat Sheet
A condensed cheat sheet for last-mile review before a platform engineering interview.
# Sre
All Sre notes →1 — Linux Interview Questions
The Linux-internals questions that actually come up in SRE loops, and the level of depth — not just the right answer — that separates an L4 response from an L6 one.
10 — System Design for SRE
How an SRE-flavored system-design interview differs from a generic one — operability, failure modes, and observability weighted as heavily as the happy-path architecture.
11 — Troubleshooting Interviews
Live, ambiguous debugging exercises where the interviewer is grading your hypothesis-and-elimination process, not whether you guess the bug in one try.
12 — Behavioral Interviews for SRE
STAR-format incident and leadership stories, and why 'what did you personally do' is the follow-up that separates a real story from a team-credit one.
13 — Staff/Principal SRE Interviews
What changes at L6/L7 — cross-org influence, strategy, and ambiguous scope replace hands-on execution as the thing being evaluated.
14 — End-to-End Production Case Studies
Full incident-to-postmortem case studies that string together design, detection, response, and review into the single narrative a real interview loop is actually testing for.
2 — Networking Interview Questions
TCP, DNS, load balancing, and TLS questions framed the way interviewers actually ask them — as a debugging scenario, not a trivia quiz.
3 — Kubernetes Interview Questions
The Kubernetes questions that probe whether you've actually operated a cluster under failure, not just deployed a YAML file that worked once.
4 — Cloud Architecture Interview Questions
Designing for a specific cloud's failure domains and managed-service trade-offs — the questions that test whether you understand what you're actually building on.
5 — Distributed Systems Interview Questions
CAP, consensus, and consistency questions posed as system-design trade-offs, which is how they actually show up in a Staff-level loop.
6 — Observability Interview Questions
Questions that test whether you can design an SLI/SLO and instrumentation strategy from scratch, not just recite what Prometheus and OpenTelemetry do.
7 — Incident Response Scenarios
Live incident-simulation questions that evaluate triage judgment and communication under pressure — the format most SRE loops actually weight heaviest.
8 — Performance Debugging Interviews
Being handed a symptom — high latency, high CPU — and narrating a systematic diagnosis instead of guessing, which is what the interviewer is actually scoring.
9 — Reliability Design Interviews
Designing SLOs, redundancy, and failure handling for a system from a one-line prompt — the reliability-flavored half of an SRE system-design loop.
# System Design
All System Design notes →Chapter 1 — Interview Methodology
Requirement gathering, capacity estimation, API design, data modeling, scaling, and bottleneck analysis as the repeatable sequence behind every design in this book.
Chapter 2 — Whiteboarding & Communication
Diagramming and narrating a design out loud so an interviewer can follow the trade-off reasoning, not just the final architecture.
Chapter 3 — Architecture Reviews: Defending Decisions
Handling interviewer pushback and "what if 10x scale" challenges without abandoning a defensible design under pressure.