Interview & Placement¶
Prep — the placement finale: interview rehearsal + portfolio presentation · prereq the core path + the Capstone (you rehearse defending real work you've shipped); no new concepts here · ~1–2 hours, best spread across several short sessions in the run-up to a real interview
An interviewer rarely stops at the question on the card — the real test is the follow-up ('why not X instead', 'what would you change now'). A memorized answer survives the first question and falls apart on the second. The deck already exists; the job here is rehearsal — drilling it until your answers come out unprompted, in your own words, under a little pressure.
TL;DR — in 30 seconds:
- The deck already exists; this module is rehearsal, not new content — drilling answers until they come out unprompted, in your own words, under a little pressure.
- The loop: Pair (mock interview surfaces your weak theme) → Do (answer 5 aloud, log gaps) → Self-check (rate each theme) → back to Pair, or on to Retain.
- No mandatory gate — you self-check repeatedly until the real interview, and the placement rep's 2-minute capstone walkthrough rehearses exactly how a real interview opens.
Learning objectives¶
By the end, the candidate can:
- Deliver a concise, structured, out-loud answer for a question from each of the 5 prep themes (behavioral, CI/CD & deployment strategies, security, AWS & serverless, Kubernetes/architecture & observability) without reading from notes.
- Defend their own project's choices under a follow-up 'why not X instead' — not just recite the prepared answer.
- Name their single weakest theme and know which specific cards need another rehearsal pass before a real interview.
Pair, Do and Prove run in Claude Code, with the onboarding-tutor skill. Click a button to copy the exact prompt, then paste it into Claude Code in this repo.
1. Learn · how to use this prep deck¶
There's nothing new to learn here — you already lived these answers on a real project. This beat is about how to rehearse effectively, not what to study:
- Treat each card as retrieval practice: cover the Back, answer out loud, in under ~90 seconds, then reveal.
- Don't memorize the Back verbatim — extract the shape (situation/problem → your approach → the trade-off → the result) and rebuild it in your own words each time. An interviewer's follow-up question exposes a memorized script instantly.
- The deck is grouped into 5 theme subdecks (see Retain below) — drill one theme at a time when you're weak on it, or shuffle the whole parent deck for mixed rehearsal closer to the interview date.
- If a card's answer feels thin, dated, or no longer matches how you'd explain it today, that's a signal to refresh it — not to skip it.
The rehearsal is a loop, not a one-shot: Pair surfaces your weak theme, Do drills it and logs gaps, Self-check tells you whether to loop back or move on.
flowchart LR
P["Pair: mock interview"] --> D["Do: answer 5 aloud, log gaps"]
D --> S["Self-check: rate each theme"]
S -->|weak theme found| P
S -->|80%+ on every theme| R["Retain: keep drilling to interview day"]
Read next: Why retrieval practice works (retrievalpractice.org — the research behind cover-answer-reveal beating re-reading). Retain deck (beat 5):
SE Onboarding::13 Interview Prep.
2. Pair · have the tutor mock-interview you¶
Drive the onboarding-tutor:
- "Mock-interview me from the
SE Onboarding::13 Interview Prepdeck — one question per theme, random order, and push back with a real interviewer's follow-up ('why not X', 'what would you change now')." - "Here's my answer to [question] — was that concise enough for a live interview? What would you cut or tighten?"
- "Based on how I'm answering, which theme am I weakest on?"
Done when: you've taken at least one full mock-interview pass and can name the theme(s) the tutor pushed back on hardest.
3. Do · answer 5 aloud, record gaps¶
Exercise: Pull 5 cards, spanning at least 3 themes, and answer each out loud, unprompted (no peeking at the Back first), timing yourself to roughly 90 seconds per answer.
- Starting point:
SE Onboarding::13 Interview Prep(or a single theme subdeck if you're targeting a weak spot). - Deliverable: a short gap log (a scratch note is fine) — one line per question: what was missing, what ran too long, or what trade-off you forgot to mention. "Nothing — clean answer" is a valid, useful entry too.
- The tutor coaches but doesn't hand you the answer — if you blank, ask for a one-word hint, not the script.
- Then, the placement rep: give a 2-minute out-loud walkthrough of your capstone — the PR, one design choice you can defend, and one thing you'd change now. This is exactly how a client interview opens.
Done when: you have 5 logged entries (gap or "clean") and one clean 2-minute capstone walkthrough — the artifact is the gap log, not a flawless performance.
Common gotchas
- Memorizing the Back verbatim. Fix: extract the shape (situation/problem → your approach → the trade-off → the result) and rebuild it in your own words each time — a memorized script survives the first question and falls apart on the interviewer's follow-up.
- Only preparing the happy-path answer, not the follow-up. Fix: for every card, also rehearse "why not X instead" and "what would you change now" — that follow-up is the actual test, not the first answer.
- Rehearsing silently instead of out loud. Fix: answer out loud, timed to roughly 90 seconds, every time — silent recall feels stronger than it is and doesn't train the delivery a live interview needs.
- Cramming one long session right before the interview. Fix: spread rehearsal across several short sessions in the run-up — retrieval practice compounds with spacing, it doesn't work as a single cram.
- Answering with generic deck content instead of your own project's specifics. Fix: anchor every answer to your own shipped work (the capstone, in particular) — a generic answer can't survive "walk me through your reasoning," a specific one can.
4. Self-check · lightweight — no mentor gate¶
Not a mandatory gate. The standard modules run a mandatory, heavier-bar Socratic gate (see the Socratic gate); this one doesn't. Interview-readiness is closer to fitness than to a one-time proof of understanding — you self-check, repeatedly, until the real interview.
Ask yourself, per theme:
- Can I answer every card in this theme unprompted, out loud, without reading the Back first?
- Am I answering with my own project's specifics, or a memorized script? (A real follow-up question will expose a script.)
- Is there a theme where I hesitate on more than 1 in 3 cards? That theme needs another Do pass before a real interview.
Self-check passes when: you can unprompted-answer each theme at roughly 80%+ (your own honest count) and can name your single weakest theme. No mentor sign-off required.
5. Retain · fight forgetting¶
Study the module deck SE Onboarding::13 Interview Prep — its theme subdecks let you drill one area at a time:
1 Behavioral & background2 CI/CD & deployment strategies3 Security & secrets4 AWS & serverless5 Kubernetes, architecture & observability
The deck syncs to your Anki automatically on pull (anki-sync). Done when you can recall, from the deck, a structured answer for every card across all 5 themes.
Check yourself — why does rebuilding an answer in your own words each time matter more than memorizing the deck's Back verbatim?
Because a memorized script survives the first question but falls apart on the interviewer's follow-up ("why not X instead", "what would you change now"). Rebuilding the shape (situation → approach → trade-off → result) each time trains you to reason live, not recite.
Check yourself — what should you do if you blank on a card during Do?
Ask the tutor for a one-word hint, not the full script — the tutor coaches but doesn't hand you the answer, since the point of the exercise is retrieval practice, not re-reading.
Check yourself — how do you know a theme needs another rehearsal pass before a real interview?
If you hesitate on more than 1 in 3 cards in that theme during self-check, it needs another Do pass. Self-check passes overall once every theme is at roughly 80%+ unprompted and you can name your single weakest theme.
Key takeaways¶
- This module is rehearsal, not new content — the 5 themes are answers you already lived on a real project; the work is drilling them until they come out unprompted, in your own words, under pressure.
- Rebuild the shape, don't memorize the Back — situation/problem → your approach → the trade-off → the result — because a memorized script survives the first question and falls apart on the follow-up.
- The real test is the follow-up, not the first answer — always rehearse "why not X instead" and "what would you change now" alongside the happy-path response.
- Answer out loud, timed, not silently — silent recall feels stronger than it is and doesn't train the delivery a live interview actually needs.
- There's no mandatory mentor gate here — you self-check repeatedly (per theme, roughly 80%+ unprompted) until the real interview, closer to a fitness practice than a one-time proof.
- The 2-minute capstone walkthrough with the placement rep rehearses exactly how a real interview opens — the PR, one defensible design choice, and one thing you'd change now.
Go deeper — curated resources¶
Hand-picked external material to take this topic further — the best books, courses, talks, and writing. Cost is tagged Free, Free online (full text/course free on the web), or Paid.
- Book · System Design Interview – An Insider's Guide (Vol 1) — Alex Xu. The standard system-design prep. Paid.
- Docs · Tech Interview Handbook — Yangshun Tay. Behavioral + coding prep, well organized. Free.
- Repo · DevOps Exercises — Arie Bregman. 2,600+ DevOps interview questions and answers. Free.
- Book · Google SRE Workbook — Google. Practical SRE, excellent for ops interviews. Free online.
Gate log (mentor fills on pass)¶
Optional here — no mandatory mentor gate for a prep module. Fill in if a mentor spot-checks you, or log your own self-check passes.
- Date passed:
- Passed by: / checked by:
- Weak spots noticed (feeds system improvement):