2 min lesson
Top three gaps, one action each
Use "Top three gaps, one action each" to explain each part and the role it plays.
Step 1 of 3
Top three gaps, one action eachGap plan
- Gap 1 (weakest)
- Assign reps, not reading. A sub-3 in coding-cold means three more timed no-AI primitives, recorded and re-scored - not another article.
- Gap 2
- Target the exact failure from the tape. If design lost on tradeoffs, redo one prompt focused only on defending cost and latency under pushback.
- Gap 3
- Build the missing story or check. If a values answer sounded rehearsed, rewrite it around a real number from your past work before you re-record.
Front-load the weakest. A 5 elsewhere cannot rescue a 2 here.
Learn more
Full explanation
Re-confirm the logistics
Re-confirm the logisticsBefore you book
- 1Location & format. Confirm you're set for in-person SF or NY and a multi-day onsite, including the team-fit days that can run over meals for senior roles.
- 2Intensity. Re-confirm honestly that the fast, flat, sometimes-six-day-week pace is a real yes, not a yes you're talking yourself into.
- 3Availability. Block the calendar for the paid 8-hour build and a possible two-day onsite before you schedule, so the decision round gets your best work, not your leftover hours.
The go/no-go bar
Don't schedule the loop until three things clear on the recordings: coding-cold (you can build a primitive with autocomplete only), design (latency, cost and eval defended under pushback) and authenticity (your Cursor usage and why-Cursor sound true, not prepped). If any of the three is faking a yes, that's exactly where this week's reps go.
QYour mock scores are: coding-cold 5, AI-systems design 2, end-to-end build 4, values 4. How should you spend your prep week?