Interview Preparation¶
Every question below ties back to a real operational concept, not a memorized definition. Reciting "a Service has four types" is worth far less than being able to explain what breaks when a selector doesn't match — which is the difference between passing a screening question and holding up under a senior follow-up.
How This Is Organized¶
By subject, since that's how you'll actually study:
- Core Concepts — Pods, Deployments, Services, namespaces, ConfigMaps/Secrets, labels/selectors
- Architecture & Networking — control plane components, kubelet/kube-proxy, CNI, DNS, Ingress vs. Service
- Scenario-Based Questions — full debugging walkthroughs for the classic production scenarios
- Security & RBAC — RBAC design, service accounts, Pod Security Admission, secrets handling
- Senior & Architect Questions — multi-cluster strategy, capacity planning, disaster recovery, cost, build-vs-buy
By Level, Roughly¶
| Level | Where to focus |
|---|---|
| Beginner | Core Concepts |
| Intermediate | Architecture & Networking, Security & RBAC |
| Advanced | Scenario-Based Questions |
| Senior / Architect | Senior & Architect Questions |
How senior interviews actually differ
A senior interview rarely asks "what is a Service" in isolation — it asks you to reason through a live situation ("15% of requests are 503ing during peak traffic, go") using several concepts at once. Scenario-Based Questions is built around exactly that shape.
Next¶
Start with Core Concepts, or skip ahead to Quick Reference.