Going blank in a technical interview isn’t a skills problem. It’s a format problem, and the room scores it like it’s the same thing.
Quick answer: If you go blank in a technical interview, say so out loud, restate the problem in your own words, then solve the smallest piece you can. The freeze comes from the format, not your skills. So the real fix is to rehearse the format: an unseen problem, a running clock, and talking while you work.
I’ve hired for tech teams for two decades, and I’ve watched strong engineers lock up in the first five minutes. At work, they get their tools, their team, and time to think. In the interview, they get a stranger, a shared screen, and a clock. That’s a different skill, yet interviewers read the freeze as “can’t do the job.”
Why does going blank happen in a technical interview?
Going blank happens because being watched changes how your brain works, not because you forgot how to code. In a 2020 study from NC State and Microsoft, 48 computer science students solved the same problem either in private or in front of an observer. The students who were observed performed half as well as the ones who worked alone. The researchers noted the sample was small, but the pattern matches what I see in coaching.
In other words, the same person with the same knowledge gets a worse result once someone is watching. That’s why more studying rarely fixes it. If nerves are the bigger issue for you, interview anxiety is a prep problem, not a personality trait.
What should you do in the moment when you go blank?
Don’t sit in silence and hope the answer shows up. Use a short script instead, because a script is easier to run than a clear head. Here are the five moves I teach:
- Say it plainly. “Give me a second to think this through.” It sounds calm, and it buys you ten seconds.
- Restate the problem. Repeat it back in your own words. Rephrasing it gives your brain a second route into the problem.
- Ask a clarifying question. Ask about input size, edge cases, or an example. Interviewers expect this, and it gives your brain something small to chew on.
- Solve a smaller version first. Start with the brute-force approach or a tiny input. A working slow answer beats a perfect one you never write.
- Narrate as you go. Say what you’re trying and why. Even a wrong path shows the interviewer how you think, which is what they’re scoring.
Notice that none of these require the answer. They only require you to keep moving. As a result, the interviewer sees a candidate working a problem instead of a candidate who stopped.
Does going blank mean you’ve failed the interview?
No. A calm recovery tells an interviewer how you’ll act when production breaks. Production breaks, specs change, and nobody on the team has seen the problem before. So how you act when you’re stuck is a fair preview of how you’ll act on the job.
The freeze only turns into a rejection when you go quiet and stay quiet. That’s the same mechanism behind a brainteaser question, where the answer isn’t the point. The room is scoring your process, so keep showing it.
How do you practice so you don’t go blank again?
Rehearse the format, because the format is the one thing you can rehearse. Here’s the exercise I give clients:
- Pick one problem you haven’t seen. Not one you’ve solved before. Surprise is the whole point.
- Set a 45-minute timer. Make the clock real, because the clock is half of what freezes you.
- Solve it out loud. Yes, even to an empty room. Talking while you think is a skill, and it feels awkward until you’ve done it a dozen times.
- Do it once with another person watching. A friend, a peer, or a coach. The observer is the variable that hurt performance in that study, so you need reps with one.
One caution: don’t memorize solutions. Candidates who memorize sound canned and freeze harder when the problem shifts, which is why rehearsed answers cost offers. Practice the process, not the answer.
FAQ
What should you do if you go blank in a technical interview?
Say you need a moment, restate the problem in your own words, and ask a clarifying question. Then solve the smallest version you can and narrate your thinking as you go.
Is going blank in an interview normal?
Yes. Being observed under a clock makes most people perform worse, even when they know the material. It’s a format effect, so rehearsing the format helps more than studying more content.
How do you stop freezing in coding interviews?
Practice with unseen problems, a real timer, and out-loud narration, and do at least a few reps in front of another person. Familiarity with the format lowers the freeze.
What to do next
If you want to know what a slow search is actually costing you, run the job search cost assessment. It takes 90 seconds and gives you a monthly dollar figure.
If finding people to practice with is the sticking point, read How to Get Interview Practice When You Barely Get Reps next.
If you’d rather have someone run a mock interview with you and tell you exactly what to fix first, book a free strategy call.