Cramming the week before an onsite rarely works. A steady four-week plan with one or two mock interviews a week builds the kind of calm you need on the day. Here is the schedule I recommend to friends.
Week 1: Baseline
- One untimed mock covering your weakest area (for most engineers, system design; for most PMs, estimation).
- Write down every question you could not answer cleanly. This list drives the next three weeks.
- Prepare four behavioural stories: a conflict, a failure, a project you led, and a hard trade-off.
Week 2: Volume
- Two timed mocks, 45 minutes each, one technical and one behavioural.
- After each, spend 20 minutes on a written debrief: what went well, the one thing to fix, and the exact phrase you wish you had said.
- Re-practise only the fix, not the whole interview.
Week 3: Pressure
- Two mocks with a stranger or a stricter interviewer. Familiar practice partners get too kind.
- Add interruptions on purpose: "Why not a queue here?" or "That's too slow, try again." Learning to recover is the real skill.
- Do one full loop day: three short mocks back to back, to test stamina.
Week 4: Taper
- One light mock early in the week, then stop adding new material.
- Re-read your debrief notes and story outlines.
- Sleep, logistics, and a short warm-up problem on the morning of the interview.
Making the debriefs count
The plan only works if every mock produces a concrete fix. Keep the notes in one document so you can see patterns: if "I jumped into code too fast" shows up three times, that is your top priority.
For practice partners, a peer, a former colleague, or a tool all work. I help build Linkjob AI, an interview assistant that can run mock rounds, and the same schedule applies whichever you use.
Disclosure: I work on Linkjob AI.