The most important file here. Fill it in every session, immediately after. Retrospective honesty is what makes Week 7 repair possible.
Coding log
First pass? = was the code correct before you started debugging. This is the L5 signal — track it religiously.
| Date | Problem | Topic | Diff | Time | Solved unaided? | First pass correct? | Why I missed it / what to redo |
|---|---|---|---|---|---|---|---|
Redo queue — anything failed or solved with help goes here, and gets re-solved cold on a Sunday ≥ 5 days later.
| Problem | Failed on | Redo #1 (date/result) | Redo #2 (date/result) |
|---|---|---|---|
System design log
| Date | Problem | Full 45 min? | Scoped first? | Estimated? | Deep dive topic | Self-score /5 | Biggest gap |
|---|---|---|---|---|---|---|---|
Self-score rubric: 1 = couldn’t structure it · 2 = structured but shallow · 3 = solid high-level, weak deep dive · 4 = drove it end-to-end with real tradeoffs · 5 = would hire at L5.
Mock interviews
| Date | Type | Interviewer | Verdict | Top 2 things to fix |
|---|---|---|---|---|
Weekly review
Fill this in every Sunday. Five minutes, no more.
Week ___
- Problems attempted / solved unaided: ______ / ______
- First-pass correctness rate: ______%
- Designs completed at full length: ______
- Stories rehearsed out loud: ______
- Weakest area this week: ______________________
- One concrete change for next week: ______________________
Targets to hit by end of Week 7
- ≥ 80% cold solve rate on mediums at 25 minutes
- ≥ 40% cold solve rate on hards at 35 minutes
- ≥ 70% first-pass correctness
- 10 of 12 system design problems run end-to-end at full 45 minutes
- 10+ behavioral stories, each rehearsed out loud under 2.5 minutes
- 2 full mock loops completed, with written feedback
- Redo queue empty