The week before the onsite
You got the loop scheduled. Five interviews back-to-back, probably split across two days, definitely virtual unless you are senior enough to fly. The next seven days are the gap between candidates who pass and candidates who think they prepared but did not.
Here is the day-by-day plan I run before mine, refined across four onsites in the last eighteen months. Three offers, one rejection. The rejection is in here too.
Day 7 — Map the loop
Ask the recruiter for the list. Most will share it. You want:
- Each interviewer's name
- Their role and team
- The format of each session (coding, system design, behavioral, hiring manager)
- The duration
Then look up each interviewer on LinkedIn for thirty seconds. Not stalking — context. If your system design interviewer wrote a blog post about queues, you can reference queue patterns. If your hiring manager came from the data team, the team is probably data-adjacent.
This is the only research that compounds. Skip it and you walk in cold.
Day 6 — One coding warm-up
Not a grind. One medium problem on LeetCode in your strongest language. Time-box at 45 minutes. The point is not to learn algorithms in a week — it is to refresh your fluency in writing code under a clock.
If you cannot finish the problem in 45 minutes, that is data. Either the company is too senior for your current prep level, or you need to pick a more familiar problem type tomorrow.
Day 5 — Behavioral story bank
Write down the answers to these eight prompts, three sentences each:
- A time you disagreed with a manager
- A time you missed a deadline
- A project you led
- A bug you debugged that took longer than expected
- A time you had to learn something fast
- A teammate you helped grow
- The biggest mistake you made and what you learned
- A trade-off you made between speed and quality
The point is not memorization. It is having stories ready so you do not freeze. When the interviewer asks "tell me about a time you led something," you do not want to spend ninety seconds searching your memory.
Day 4 — System design refresh
Watch one video on the most likely topic for your level. For senior IC and below, that is usually one of:
- Designing a chat system
- Designing a feed (timeline)
- Designing a URL shortener
- Designing a rate limiter
Take notes by hand. Closing your laptop and writing forces synthesis. Re-watching a video twice does not.
Day 3 — One mock interview
Live, with a person, video on. Pramp is free. So is asking a friend who interviews for a living.
The mock is not about getting feedback on technical content. It is about hearing yourself talk under pressure. Most candidates cannot recognize their own filler words ("so basically," "kind of," "like") until they hear themselves on a recording.
I rejected my own mock from two years ago after fifteen minutes. Watching a recording is brutal but it is faster than learning the same thing in a real interview.
Day 2 — Light day
This is the day people accidentally ruin. They cram. They watch three more system-design videos. They redo their LeetCode set. They walk into the loop tired.
Do something physical. Walk for an hour. Cook a real meal. Do not open the laptop.
Your brain consolidates the previous five days of prep during low-stimulation activity. Cramming on day 2 actively hurts.
Day 1 — Logistics + early sleep
Test your camera and microphone on the platform they are using. Companies use Coderpad, CoderByte, custom Notion pages, Google Docs — figure it out today, not five minutes before.
Have water, paper, pen at your desk. Close every browser tab except the meeting link. Charge your laptop and connect to power.
Eat dinner early. Be in bed eight hours before your first session.
During the loop — the three things that decide outcomes
After four onsites I am convinced these matter more than your raw technical ability:
1. Recovery. You will fumble at least once. Maybe twice. The interviewer is not deciding "did they get every answer right" — they are deciding "do I want to debug a production issue with this person at 2am." The candidate who says "I made a mistake, here is what I would change" beats the candidate who pretends the mistake never happened.
2. Pace. Talk through your thinking at a steady speed. Not too fast (panic), not too slow (uncertainty). When you do not know, say "I am thinking about whether X or Y matters more here" instead of going silent.
3. Asking real questions. "What is the team's biggest challenge right now?" is filler. "I noticed your roadmap mentions migrating off [thing] — what is the timeline and who owns it?" is a real question. Senior interviewers especially respond to candidates who clearly read the materials.
Why I failed the rejection
I went into the loop on three hours of sleep because I was rewriting my system design notes at 1am. By the third interview I could not hold context. The hiring manager was kind about it but the feedback was clear: "candidate seemed underprepared for the depth of the architecture round."
I had over-prepared on content and under-prepared on cognitive load. The week-before plan above is structured so that does not happen again.
What to do today
If your onsite is in seven days: start with day 7, the recruiter intel.
If your onsite is in three days: skip ahead — finish the story bank tonight, do the mock tomorrow, light day the day before.
If your onsite is tomorrow: close this tab, eat, sleep early.
Related deep dives:
- How to Prep for a Developer Interview in 48 Hours — the short-deadline version of this plan
- The 8 Skills Tests Companies Are Actually Using in 2026 — what to expect inside the loop
If you want a free interview prep tool that builds you a question bank from a job description, it is here.
Top comments (0)