Answer frameworks
STAR for behavioural and incident questions
- Situation — context and stakes, briefly.
- Task — what you were responsible for.
- Action — what you did, step by step, with technical detail.
- Result — outcome with numbers, and what changed afterwards.
Keep it to about two minutes. End with the lesson or the permanent improvement — that's what makes it senior.
Technical "explain X" questions
- One-sentence definition.
- How it works (the mechanism).
- When you'd use it / trade-offs.
- A real example from your work, or a gotcha.
Example: "What's IRSA?" → definition → OIDC/STS flow → least privilege, vs node roles and Pod Identity → "we used it for External DNS and Flux's ECR access".
Troubleshooting questions: narrate a method
Interviewers care about how you think. Say your steps aloud:
- Clarify scope and impact: who's affected, since when, what changed.
- Mitigate first if users are hurting: roll back, fail over, scale.
- Narrow down layer by layer with evidence (commands, metrics, logs).
- Root cause, then fix.
- Prevent: alerts, tests, guardrails, runbooks.
"First I'd check what changed — deploys in the last hour. If a deploy correlates and errors persist, I'd roll back via a Git revert. Then I'd look at ELB vs target 5xx..."
System design questions
- Clarify requirements — scale, SLOs, compliance, team size, existing tools, budget. Ask 2–4 good questions; state assumptions.
- High-level design — draw the main components and flows.
- Deep dive where it matters — security, failure modes, scaling, data.
- Trade-offs — what you chose and what you rejected, and why.
- Operations — monitoring, alerting, runbooks, cost, how teams use it.
Whiteboard rounds grade: requirement clarification, sound trade-offs, reliability thinking and communication — not a single "correct" architecture.
When you don't know
Say what you do know, how you'd find out, and reason aloud: "I haven't used Istio's ambient mode in production. My understanding is it moves the proxy out of sidecars into per-node components... To decide, I'd check..." Never bluff — senior interviewers probe until bluffing collapses, and honesty scores well.
If you realise an earlier answer was wrong, go back and correct it briefly — it shows self-awareness.