The single highest-leverage thing you can do on interview day is arrive already warm. Do not walk into your first coding round cold. In the 60 to 90 minutes before it starts, solve two or three easy problems you have seen before, get your blood moving, and rehearse your opening narration out loud. That is it. This is not the day to learn dynamic programming or grind hard problems; it is the day to prime the reflexes you already built.
We run mock interviews all day, and the pattern is consistent: candidates who bomb the first 10 minutes usually were not warm, not underprepared. They knew the material but spent the opening minutes shaking off rust while a clock ran and an interviewer watched. Below is the routine we tell people to use.
Why warming up actually works
A coding interview is an executive-function task: you are holding constraints in working memory, planning, and switching between reading, coding, and talking. Research on acute exercise finds that a short bout of moderate aerobic activity measurably improves cognitive control shortly afterward, and that simply anticipating exercise does not produce the effect. In plain terms, a brisk walk before the interview does something a mental pep talk does not.
The same logic applies to the coding part. Your first problem of the day is always the slowest because you are context-switching into problem-solving mode. If that switch happens on a throwaway warm-up problem at your kitchen table, it does not happen on the real question in front of an interviewer. The goal is to spend your "first problem tax" before the meeting, not during it.
The 90-minute warm-up timeline
Here is the schedule we recommend for a morning interview. Shift it earlier or later, but keep the sequence.
| Time before start | What to do |
|---|---|
| 90 min | Wake up with margin, eat something with protein, hydrate |
| 75 min | 15 to 20 min brisk walk or light workout |
| 55 min | Solve 2 to 3 easy problems you already know (timed, out loud) |
| 25 min | Coffee if you drink it, set up your environment, re-read the format |
| 10 min | Bathroom, water, close every tab you do not need |
| 0 min | Join early, breathe, smile |
A few notes on the pieces that matter most.
Do the physical part first
Twenty minutes of walking is enough. You want elevated heart rate and alertness, not exhaustion, so skip a hard lift or long run that leaves you depleted. If you drink coffee, time it so it peaks during the interview rather than before your warm-up; caffeine takes roughly 30 to 45 minutes to hit, so a cup about 30 minutes before start is reasonable. Do not introduce caffeine on interview day if you never drink it. Novelty and adrenaline are not what you want.
Then warm up your hands and your mouth
The mistake we see most is warming up silently. Interviews are performances: you have to code and narrate at the same time, and that dual-tasking is the actual skill under test. So when you solve your warm-up problems, talk through them out loud exactly as you would with an interviewer. Say the brute force, say the complexity, say why you are choosing a hash map. You are warming up your explaining voice, not just your typing.
Which problems to warm up on
Pick problems that are easy for you and that touch the patterns you expect. The point is fluency and confidence, not difficulty. Three warm-up problems in the 15 to 25 minute total range is plenty.
Good warm-up candidates from our question bank:
- Minimum Amount of Time to Fill Cups (junior). A clean greedy problem you can reason through in a few minutes. It gets you saying "the bottleneck is the largest pile" out loud, which is exactly the kind of crisp observation you want flowing.
- Maximum Number of Consecutive Values You Can Make (mid/senior). Sort, then extend a reachable range. Short code, a satisfying greedy invariant to state, good for rehearsing "here is why this works."
- Integer to English Words (staff). Not algorithmically deep, but it forces careful casework and clean helper functions. If your target company likes implementation-heavy questions, this warms up your structure and naming.
For pattern-specific rehearsal, Find Duplicate Subtrees is a compact way to re-fire tree traversal plus serialization, and Domino and Tromino Tiling is a one-recurrence DP you can write from memory if DP is your weak spot and you want one confidence rep.
What to avoid: hard, unfamiliar problems. Do not open Find Critical and Pseudo-Critical Edges in Minimum Spanning Tree or Number of Ways to Stay in the Same Place After Some Steps an hour before your interview. If you solve it, you burned energy; if you fail, you walk in rattled. Both outcomes are bad. Save unseen hard problems for practice days, not game day.
If you know the company, warm up with the shapes it actually asks. Our per-company breakdowns for Amazon, Google, and Meta show the recurring topics, so you can pick warm-ups that rhyme with the real thing instead of guessing.
Set up your environment before you are on camera
For a virtual on-site, treat setup as part of the warm-up:
- Close Slack, email, and every browser tab except the interview link and your editor or the coding platform.
- Test your mic, camera, and internet ahead of time, and have a phone-hotspot backup.
- Open a blank scratch file or notebook for your own notes and a place to jot the problem constraints.
- Put a glass of water and a pen and paper within reach. Paper is faster than a text box for sketching a tree or a grid.
- Silence notifications on every device, including your phone.
The standard guidance for arriving early holds even online: join a couple of minutes before start, not 15, which just adds waiting-room anxiety. For in-person rounds, plan to be in the building about 10 to 15 minutes early, which is the range recruiters generally recommend: enough buffer for security and elevators, not so early that you sit stewing.
Nail the first five minutes
Warming up pays off in a specific window: the opening of the real interview. Have a fixed opening script so you never freeze:
- Read the problem out loud, then restate it in your own words.
- Ask 2 or 3 clarifying questions (input size, ranges, duplicates, empty input).
- State a brute-force approach and its complexity before optimizing.
- Say your plan in one sentence, get a nod, then code.
This sequence buys thinking time and signals structure, and because you rehearsed it on your warm-up problems, it comes out smooth. Interviewers form an impression fast, and a calm, organized first five minutes sets the tone for everything after.
One more thing: budget your time against the format. Many companies run tight windows, so know whether you are facing one 45-minute problem or two shorter ones and pace accordingly. If you get stuck, our guide to debugging under pressure style habits applies: narrate what you are checking rather than going silent.
FAQ
Should I do a hard problem right before the interview to "prime" myself?
No. A hard problem you cannot finish will shake your confidence, and one you do finish drains focus you need later. Warm up on easy, familiar problems so you enter feeling fast and capable, not depleted.
How much coffee should I drink?
If you already drink coffee, one normal cup about 30 minutes before start is fine so the effect peaks during the interview. Do not overdo it, since too much caffeine adds jitter and makes it harder to think and speak clearly. Never introduce caffeine on interview day if it is not part of your routine.
What if I only have 15 minutes to warm up?
Do the compressed version: a 5-minute walk or some jumping jacks, then one easy problem solved out loud with full narration. Even a single rehearsal of your opening script and one clean solve meaningfully reduces first-problem rust.
Is warming up worth it for a phone screen too?
Yes, arguably more. Phone screens are short and unforgiving, so there is no time to shake off rust on the clock. Solve one easy problem out loud beforehand and confirm your audio and shared editor work.
Should I review my resume and projects before a coding round?
Briefly, if behavioral questions might be mixed in, but keep the primary warm-up on coding. Skim your two strongest project stories so they are top of mind, then return to solving and narrating a warm-up problem.