TL;DR: If you can solve mediums on LeetCode alone but your mind goes empty the second an interviewer is watching you type, you don't have a knowledge gap. You have a pressure gap. Solving alone and solving while someone judges you in real time are two different skills that live in two different states of your nervous system, and you have thousands of reps at the first and almost none at the second. The fix is to rehearse the watched, talking-out-loud version of the interview before you are in it, so your working memory has a groove to fall into instead of going white. That is mental rehearsal, and it is what people who perform under pressure actually train.
I'm Peter, the founder of UpSpiral. The coding interview is one of the cleanest examples of a pattern I see across every high-pressure field: the ability is real, the state it has to run in is untrained. You are not being tested on whether you can write a two-pointer solution. You are being tested on whether you can write it while a stranger watches, while you narrate your thinking, while a clock runs, while your whole job outcome sits on the table. That is a different task. Let's break it down.
Why does my mind go blank the moment someone watches me code?
Because being evaluated triggers a stress response, and the stress response steals the exact resource that coding depends on: working memory.
When your brain flags a situation as socially threatening, and a live-judged interview absolutely qualifies, it dumps adrenaline and cortisol and narrows your attention to deal with the "danger." The problem is that solving an algorithm is a working-memory heavy task. You are holding the input, the constraints, the half-built approach, and the edge cases in your head all at once. Under threat, that mental workspace shrinks. So the approach you would have seen instantly at home is suddenly out of reach, and the blank you feel is not you forgetting how to code. It is your working memory getting squeezed by a stress response that thinks it is protecting you.
This is the same wiring behind why people knew the material and still blanked on the exam. The information is intact. The retrieval system is jammed.
Is blanking a sign I'm actually not good enough?
No, and this is the belief that makes it worse. A real skill gap shows up everywhere, including when you practice alone. Interview blanking shows up only when you are watched.
If you can consistently solve the problem class on your own and it collapses specifically when someone is observing, that is the tell. The competence is trained. The performing-it-under-observation is not. And the two fixes are opposite. A skill gap gets closed by grinding more problems. Blanking gets worse when you grind more, because the problem was never information. Piling on more LeetCode at the same anxiety just gives the anxious mind a bigger pile to freeze around, and then you read the freeze as proof you are behind, which raises the stakes on the next one. It is a loop, and the loop is the actual opponent.
The specific things that go wrong in a technical interview
Naming the failure points makes them trainable instead of terrifying:
- Talking and thinking at the same time. Alone you solve silently. In the interview you have to narrate your reasoning out loud, which is a second cognitive load stacked on top of the first, and most people have never practiced it.
- The silent stretch. You hit a point where you do not immediately know the next step, and the silence feels like it is screaming that you are failing. Untrained, people panic-abandon a good approach in that silence.
- The interviewer's face. A neutral or unreadable expression gets read as disapproval by an anxious brain, which spikes the stress further.
- The first thirty seconds. If the opening move does not come instantly, the "I'm blanking" story starts, and once that story starts it eats the rest of your working memory.
How to mentally rehearse the interview, not just the problems
Grinding problems is more reps at the coding. Mental rehearsal is reps at the interview. The interview is what you are short on, so that is what to train.
Here is a rehearsal rep. Close your eyes and put yourself in the call. See the shared editor. Hear yourself read the prompt out loud. Feel the nerves rise, the heart rate, the urge to rush, and instead of fighting it, rehearse the response: one slow exhale, then say out loud "let me restate the problem to make sure I have it," which is a calm, competent opening move that buys your working memory a moment to come back online. Then rehearse the hard part specifically. Rehearse hitting a point where you do not know the next step, and instead of panicking, saying "let me think about the brute force first and then optimize," and working forward from there. Rehearse the interviewer being silent and you staying level anyway. Rehearse catching a bug in your own code, saying so plainly, and fixing it, because that reads as strong, not weak.
You are not visualizing a fantasy where you are suddenly a 10x engineer who never gets stuck. That builds nothing. You are rehearsing the realistic version, getting stuck included, and rehearsing your composure inside it. Imagined action activates much of the same circuitry as the real thing, which is why a rehearsed interview feels familiar when it arrives, and familiar is the opposite of blank. It is the same reason rehearsing a high-pressure moment beats just knowing the material.
What to do in the sixty seconds before the call
Rehearsal is the long game. Right before the interview, the lever is your breath and your opening line.
Do a few long exhales before you join. In for about four, out for about six or seven, several times. The long exhale is the fastest way to take the top off a racing nervous system and it pulls a little working memory back. Have a scripted, calm first move ready, restate the problem, ask one clarifying question, so you never start from a cold blank. And reframe the silence in advance: silence while you think is not you failing, it is you working, and the best interviewers know that.
Where UpSpiral fits
This is the exact problem I built UpSpiral for. It generates a short personalized meditation that says your name and walks you through the specific moment you freeze in, in this case sitting down in the interview, feeling watched, and staying clear and level while you talk through the problem, so you can take that pressure rep the night before or the hour before instead of live for the first time. You rehearse the hard version in a calm body enough times that your body stops flooding you at the worst moment. If you have an interview coming up, you can try UpSpiral free.
Blanking in a coding interview does not mean you cannot code. It means your working memory got squeezed by a stress response in a moment you never trained for. Train the moment, breathe out before you start, and give the silence permission to exist. The code was never the hard part.