Why you freeze in interviews, and what actually helps
Interview performance and job competence are different skills. Here is what the research says about the gap, and the handful of things that close it.
You have written the thing they are asking about. You have shipped it, debugged it at 2am, explained it to a new hire. And in the interview your mind goes flat and you produce three sentences of mush.
This is extremely common and it is not a knowledge problem.
What is actually happening
Working memory is finite, and evaluation anxiety consumes a chunk of it. The part of your attention that would normally be retrieving a specific example is instead running a background process about how you are being perceived. You have less capacity available for the actual task.
This is why the freeze feels so specific: you can still talk, you can still reason, but the fast retrieval you rely on every day is gone.
What does not help
- "Just be confident." Confidence is an output, not an input.
- Memorising answers. Under pressure a memorised script fails at the first unexpected follow-up, and the failure is worse than not having one.
- More technical study. If you already know the material, more study addresses a problem you do not have.
What does help
1. Externalise the structure
The thing you lose under pressure is organisation, not knowledge. Having a structure in front of you — STAR for behavioral, a component list for design — offloads the organising work so your remaining capacity goes to content.
2. Narrate before you solve
Saying "let me make sure I understand the constraints" buys you eight seconds and moves you from retrieval mode into conversation mode, which is far less load-bearing on working memory.
3. Prepare stories, not answers
Six well-known stories from your own work will cover most behavioral questions, because most behavioral questions are the same four questions rephrased. Stories survive follow-ups; scripts do not.
4. Reduce the number of unknowns
Test your audio. Know the platform. Have water. Every logistical unknown you eliminate is capacity returned to the actual interview.
The candidates who interview well are rarely the ones who know the most. They are the ones whose preparation freed up enough attention to think in the room.
On using AI assistance
There is an honest version of this and a dishonest one, and the difference matters.
The honest version: you have a structure available so the organising load comes off your working memory, and you say the content in your own words. You leave the interview having demonstrated what you can actually do.
The dishonest version is reading a script aloud. It is also, practically speaking, obvious — the cadence of someone reading is different from the cadence of someone thinking, and interviewers hear it.