Day 179 Β· Training camp, final week

Interview Gym

You will be able to
  • Recognize the DSA pattern for 15 classic prompts in under a minute each and sketch the solution shape
  • Answer 20 ML/LLM rapid-fire questions in two sentences each without notes
  • Complete one full AI-system-design mock under the Day 160 rubric
  • Bank six STAR stories mined from your 180 days, each with a quantified result
  • Close the interview error log: every remaining DRILL item exercised today
Today's ~120 minutes
Warm-up: DRILL list + due flashcards10 min
Ring 1: 15-prompt DSA recognition drill25 min
Ring 2: 20-question rapid-fire20 min
Ring 3: system-design mock + self-grade30 min
Ring 4: STAR stories + error-log close-out25 min
Quiz + schedule tonight's revisions10 min

Builds on: Day 35 β€” Interview drill I (DSA) Β· Day 84 β€” Interview drill II (ML viva) Β· Day 160 β€” AI system design Β· Day 175 β€” The DRILL list

The analogy

The last week before a title fight, boxers stop learning new punches. Training camp becomes rehearsal: pad work to keep combinations sharp, film study of the opponent's favorite openings, and sparring rounds under fight rules β€” with the corner shouting the one or two habits that still leak. Nobody gets stronger in the final week; they get READY, which is different. The fighter who tries to learn a new hook on Thursday shows up confused on Saturday.

Today is fight camp for interviews. Nothing new enters your head β€” everything already in it gets retrieval-tested at speed, in the four rings you'll actually fight in: the DSA round (pattern recognition, not memorized solutions β€” see "sorted array, find pair" and FEEL two pointers), the rapid-fire knowledge round (two crisp sentences beat two rambling minutes), the system-design round (the Day 160 method under a clock), and the human round (six true stories from your own 180 days, shaped so a stranger can follow them in 90 seconds). Your error log β€” kept since Day 28 β€” is the film study: it knows your leaky habits better than any coach.

Why this matters on the job

The 2026 AI engineer loop is remarkably standardized: a DSA screen, an ML/LLM knowledge round, an AI system design round, and behavioral/FDE-case interviews β€” you will meet all four within any two-week interview sprint. Preparation is disproportionately about retrieval speed: candidates who KNOW the material but retrieve slowly read as juniors. You have 178 days of material and artifacts; today converts them from "things I did" into "answers I can produce in 90 seconds," which is the only form interviews accept.

Guided practice

guided 1

Ring 1 β€” the 15-prompt DSA recognition drill

25 min

Timer: 60 seconds per prompt. Say aloud: pattern, approach in one sentence, time/space complexity. Answers at the bottom β€” check after each five. Then pick TWO you hesitated on and code them fully (15 of the 25 minutes).

  1. Given an array and a target, return indices of two numbers summing to target.
  2. Longest substring without repeating characters.
  3. Given a string of brackets, determine if it is valid.
  4. Reverse a singly linked list.
  5. Determine if a linked list contains a cycle.
  6. Merge two sorted linked lists into one sorted list.
  7. Return the level-order traversal of a binary tree.
  8. Validate that a binary tree is a BST.
  9. Return the k most frequent elements in an array.
  10. Count islands of 1s in a 2D grid.
  11. Given course prerequisites, determine if all courses can be finished.
  12. Search a target in a rotated sorted array.
  13. Find the first version that fails, given a boolean API over versions.
  14. House robber: max sum of non-adjacent elements.
  15. Fewest coins to make an amount from given denominations.
ANSWERS: 1 hash map complement, O(n)/O(n) (D23). 2 variable sliding window +
set, O(n) (D24). 3 stack of openers, O(n) (D25). 4 pointer reversal, O(n)/O(1)
(D26). 5 fast/slow pointers, O(n)/O(1) (D26). 6 two pointers/dummy head, O(n+m)
(D24/26). 7 BFS with queue, O(n) (D29/31). 8 DFS with min/max bounds, O(n)
(D29). 9 hashmap counts + heap of size k, O(n log k) (D30). 10 DFS/BFS flood
fill, O(rows*cols) (D31). 11 topological sort / cycle detection, O(V+E) (D31).
12 modified binary search on the sorted half, O(log n) (D33). 13 binary search
for first true, O(log n) (D33). 14 1D DP: rob[i]=max(rob[i-1], rob[i-2]+v),
O(n)/O(1) (D34). 15 DP on amount, O(amount*coins) (D34).

Log any prompt where the pattern took > 60 s into the error log with its revisit day.

guided 2

Ring 2 β€” 20 ML/LLM rapid-fire

20 min

Cover the answers. One minute per question, spoken aloud in ≀ 2 sentences. Score βœ“ (matched the gist) or βœ— (log it).

  1. Precision vs recall β€” and when do you prioritize each?
  2. Your model is overfitting. Name the signs and two remedies.
  3. Why is cross-entropy the standard classification loss?
  4. Explain bias vs variance in one breath.
  5. L1 vs L2 regularization β€” practical difference?
  6. Why do tree ensembles usually win on tabular data?
  7. What is data leakage and its sneakiest form?
  8. What is an embedding?
  9. Attention in one sentence: what do Q, K, V do?
  10. Why do transformers need positional encoding?
  11. Why BPE tokenization instead of words or characters?
  12. What do temperature and top-p actually control?
  13. Pretraining vs SFT vs RLHF β€” one line each.
  14. Why is hallucination structural rather than a bug?
  15. When RAG vs fine-tuning?
  16. Chunk size in RAG: what breaks when too small? Too large?
  17. Why hybrid (dense + lexical) search?
  18. Name two biases of LLM-as-judge and one mitigation.
  19. TTFT vs tokens/sec β€” and what does the KV cache buy?
  20. Prompt injection vs jailbreak β€” and one architectural defense.
ANSWERS: 1 P=of flagged, how many right; R=of actual, how many found. Optimize R
when misses are costly (fraud), P when false alarms are (spam) (D75). 2 train
metric >> val metric; remedies: more data, regularization, simpler model, early
stopping (D76). 3 It is the log-loss of the true class under your predicted
distribution - minimizing it = maximizing likelihood; gradient stays informative
even when confident and wrong (D62/72). 4 Bias = too simple, misses pattern;
variance = too flexible, memorizes noise; total error trades them (D76). 5 L1
zeroes weights (feature selection); L2 shrinks smoothly (D76). 6 Tabular has
heterogeneous features & sharp interactions; trees split natively, no scaling
needed; bagging/boosting cut variance/bias (D74). 7 Test info reaching training:
target leakage, preprocessing fit on full data, temporal leakage - the sneakiest
(D69/76). 8 A learned dense vector where geometric closeness = semantic
similarity (D92). 9 Each token's Query scores every Key; the weights mix Values
- a soft, learned lookup (D94). 10 Attention is permutation-invariant; position
must be injected or word order vanishes (D95). 11 Subwords balance vocab size
vs sequence length; handles rare words; but causes arithmetic/spelling quirks
(D96). 12 Temperature rescales logits (flatter/sharper distribution); top-p
truncates to the smallest set with cumulative prob p (D102). 13 Pretrain: next
token on web scale; SFT: imitate curated demonstrations; RLHF/DPO: optimize
toward human preference (D100). 14 The objective is plausible continuation, not
truth - fluent fabrication is the training goal working as designed; grounding
must come from outside (D101/104). 15 RAG for knowledge (fresh, cited,
per-tenant); FT for form/style/format; often both (D113/127). 16 Too small:
context fragments, answers lack support; too large: retrieval blurs, irrelevant
text dilutes and costs tokens (D114). 17 Dense misses exact identifiers/rare
terms; BM25 misses paraphrase; fuse (RRF) to cover both failure modes (D116).
18 Position bias, verbosity bias, self-preference; mitigate: swap order, pin
length, calibrate vs human labels (D135). 19 TTFT = time to first token (UX);
tokens/sec = generation rate; KV cache stores past attention keys/values so
each new token avoids recomputing the prefix (D155). 20 Injection: hostile
instructions in DATA (docs, web); jailbreak: user attacks the model's own
policy. Defense: privilege separation - tools/permissions assume the model may
be compromised (D132).

On your own

Ring 3 β€” the full system-design mock

25 min

30-minute clock, whiteboard or paper, spoken aloud. Prompt:

"Design an AI assistant for a 5,000-agent contact center: agents handle customer calls and chats; the assistant should suggest grounded answers from the company knowledge base in real time, draft follow-up emails, and flag compliance risks. The customer is a regulated telecom. They want agent handle-time down 20%."

Follow the Day 160 method in order: requirements (functional + non-functional β€” what does "real time" mean in ms here?), constraints & scale envelope (5,000 concurrent agents Γ— calls/hour β†’ QPS; token cost at that volume), architecture (ingestion, retrieval, suggestion service, streaming path to the agent desktop), quality strategy (golden set from historical transcripts, groundedness gates, judge calibration, compliance-flag precision/recall targets β€” false accusations of agents are the political risk), rollout (shadow mode β†’ pilot team β†’ gates), and the trade-off closing (latency vs quality vs cost β€” pick and defend).

Self-grade 1–4 per rubric line, evidence required: [1] Requirements & constraints made explicit and quantified before any boxes. [2] Architecture coherent end-to-end with the streaming path and failure modes named. [3] Quality strategy has a golden set, gates, AND the compliance-precision discussion. [4] Scale/cost envelope computed with real arithmetic. [5] Trade-offs closed with a recommendation, not a menu. Score ≀ 2 anywhere β†’ that section is tonight's revision.

Ship before you stop

The interview kit: six STAR stories + error log close-out

Write portfolio/interview-prep/star-stories.md: six stories, each ≀ 200 words in STAR form with a quantified result and the artifact that proves it (commit, doc, report). Required coverage: (1) ambiguity β†’ shipped scope (Day 164/168 or 174 sim); (2) pushing back on a stakeholder with options (Day 171/174 β€” the change request); (3) a production incident you debugged methodically (Day 172's scenarios or a real capstone incident); (4) a failure and what it changed in your process (mine the error log β€” e.g. the Day 133 red-team findings); (5) learning something hard fast (backprop week, or the eval-statistics arc); (6) building trust with a skeptic (the CISO objection). Then close the error log: every DRILL item from Day 175 either exercised today (mark done + date) or explicitly moved to your post-program plan. Rehearse two stories aloud, timed ≀ 90 seconds each.

Rubric β€” check what you completed (0/6)

Common mistakes & misconceptions

  • Learning new material today. Fight-camp rule: the marginal value of one new topic is near zero; the marginal value of faster retrieval on 178 days of existing material is enormous.
  • Coding before naming the pattern. Interviewers grade the recognition and narration; silent typing reads as memorization even when it isn't. Pattern β†’ complexity target β†’ then code, aloud.
  • Two-minute answers to rapid-fire questions. Length signals uncertainty; the two-sentence form (answer + one depth-proving caveat) signals ownership. Practice the compression, not the content.
  • Drawing boxes before requirements in system design. It is the single most-punished failure in the round β€” the Day 160 method exists because "requirements first" collapses under adrenaline unless drilled.
  • STAR stories with "we" throughout. The interviewer is hiring YOU; "we shipped" hides your contribution. First-person singular in the Action section, honestly scoped.
  • Polishing your six stories into fiction. Every story should survive "show me" β€” that's why each cites a commit or document. Verifiable modest beats impressive unverifiable, every time.
Knowledge check

Q1. "Find the longest substring with at most k distinct characters." The pattern reflex should be:

Q2. In the rapid-fire round, the strongest answer shape is:

Q3. What must an AI-system-design answer contain that a classic one usually does not?

Go deeper β€” curated resources

courseNeetCode Roadmap β€” final pattern pass β†—30 minrepoTech Interview Handbook β€” behavioral & loop logistics β†—20 minbookML Interviews Book (Chip Huyen) β€” rapid-fire coverage check β†—25 minrepoLLM Interview Questions repo β€” extra rapid-fire rounds β†—20 minarticleFDE Interview Guide (Exponent) β€” the case round format β†—15 min
If you have a third hour
  • Live mock with a human β€” Book one real mock (peer, community, or a platform) within 7 days. Solo drills calibrate knowledge; a live stranger calibrates nerves β€” different muscle, same rubric.
Done means
  • 15/15 prompts attempted; hesitations logged; two coded fully
  • Rapid-fire scored; every βœ— has a revisit day scheduled
  • System-design mock completed in 30 min and self-graded with evidence
  • Six STAR stories committed with artifacts; two rehearsed ≀ 90 s; error log closed
How this connects

← Back: This day cashes out Day 28's error log, Day 35 and 84's drills, Day 160's design method, and the simulations' stories β€” nothing today was new, which was exactly the point.

Forward β†’: Tomorrow is Demo Day: the mastery final samples these same wells program-wide, and the job-search checklist puts the STAR stories and the capstone link into motion. The gym never fully closes β€” the post-program plan keeps a weekly maintenance round.

Unlocks: D180 Demo Day