Twelve interviews,
one reading list.
This isn't a curriculum you finish before you start mocking. It's cut into twelve slices, one per mock interview, front-loaded so the early rounds carry more new material and the later ones are close to a real cold screen. Read a slice, close the laptop, run a mock (DRW or Jump, alternating), then come back for the next slice. The order mixes topics deliberately and has nothing to do with the problem bank, so finishing a slice won't tell you which problem shape is coming next.
Why the order is what it is
Forty-seven sections across the six fundamentals pages, split into twelve blocks that shrink as you go: 6 sections in interview 1, down to 3 by interview 9 and after. Early on you won't have covered half of what a mock throws at you, and that's fine. Lean on the coding problem and let the fundamentals questions be where you visibly reason toward an answer instead of stating one from memory. By the last few interviews the reading is light because you've already seen almost everything once, so those rounds should feel close to the real thing.
Each block interleaves Python semantics, runtime, NumPy, pandas, OS, and networking rather than clearing one topic before starting the next. That's closer to how a real interviewer jumps around, and it means no block maps onto a single problem shape from the mock bank, so reading ahead won't make the next mock predictable.
| Badge | What it means here |
|---|---|
| Mechanism | Worth rebuilding from a lower-level fact, not just recognising |
| Predict | Worth being able to state the output before running it |
| Fluent | Worth writing from memory at normal speed |
| Name only | One sentence is enough, don't overinvest |
A few things to keep in mind
- Alternate DRW and Jump every session. The underlying skill is the same; the format difference is what needs the reps.
- Read the block, then close the tab before the mock. The point is retrieval under pressure, not open-book recognition.
- Don't reread earlier blocks out of order to get ahead on a topic. The interleaving is deliberate, and going linear undoes the front-loading.
- If a mock exposes a gap outside the current block, that's fine. It'll be covered a couple of interviews later; note it and move on instead of derailing the reading plan.
- The résumé strand and the coding problem itself are left out of this plan on purpose. They're practiced live in the mock, not pre-read.