If you have solved hundreds of LeetCode problems and still freeze in real interviews, you do not have a knowledge problem. You have a rehearsal problem: you practiced solving alone and in silence, and the interview tests solving out loud while someone watches. In a randomized study by researchers at NC State and Microsoft, being watched by an interviewer cut performance in half. In our view, the fix is to rehearse that exact condition until it stops feeling new: talk through every problem, learn what to say when your mind goes blank, and do full spoken mock interviews. DevInterview.AI runs unlimited live voice mock interviews for $19.99 a month, with the first one free.
Disclosure: we build DevInterview.AI, one of the options below. Prices come from each vendor's own pages, checked between October 13 and October 14, 2026, with sources at the bottom.
Why 300 problems did not fix it
Solving a problem alone trains recall: you read it, you work it out, the tests pass. A real interview adds three things that solo practice never does: someone watching, the need to explain while you think, and a clock you cannot pause. The NC State study tested 48 computer science students. Half solved a problem on a whiteboard while explaining it to an interviewer who looked on; the other half solved it alone in a private room, with no one watching and nothing to explain. The watched group performed half as well, and its stress and cognitive load were significantly higher. The study did not test practice, but in our view solving more problems alone will not move that number, and practicing under the watched, spoken condition will.
The fix: four drills
- Narrate every practice problem. From the first read, say it out loud: restate the problem, walk an example, name the brute force and its complexity, then improve it. If talking makes you slower, good: that is the skill being trained.
- Learn a script for blanking. Freezing is not the failure; silence is. When your mind goes blank, say what you know: restate the input and output, work a tiny example by hand, state the brute force even if it is slow, or ask a clarifying question. Each one buys time and shows your thinking.
- Practice being watched. Full mock interviews, timed and spoken, are the closest thing to the real room. Start them weeks before the interview, not the night before.
- Repeat until it is boring. In our view, a full spoken mock most days in the final two to three weeks, ten or more in total, until the format stops feeling new.
Where to get the reps
| Option | What you get | Price as billed |
|---|---|---|
| DevInterview.AI | Unlimited live voice mock interviews: coding with code that runs, system design and behavioral, each with a scored report | First interview free; $19.99/mo, $49.99/qtr, $99.99/yr |
| Aced (formerly Exponent) peer mocks | A live mock with another candidate, where you interview each other | Free, 5 a month |
| interviewing.io | An anonymous mock interview with an experienced engineer | From $179 a session |
| Narrating alone | Your own voice, a timer and a recording to listen back to | Free |
DevInterview.AI gives you a voice interviewer on demand: a 30-minute coding round set to your target company and level, in an editor that runs your code. The interviewer asks follow-ups and is instructed never to tell you whether you are right and never to hand you the solution, so you practice working through being stuck instead of being rescued. Each interview ends with a scored report and a hire verdict, so you can see whether the freezing is fading.
Peer mocks on Aced (formerly Exponent) put a real person across from you, which is good practice for live nerves. Free accounts get 5 a month; every session needs scheduling, and part of it goes to interviewing your partner.
One interviewing.io session near the onsite gives you an experienced human's read, from $179 a session per its FAQ. Use it to calibrate, not for volume.
Where this fits in a full plan
Freezing is a problem with step 3 of our 8-week study plan: learn the patterns on NeetCode, study system design on Hello Interview, practice out loud on DevInterview.AI, and optionally book one human session. With 300 problems behind you, step 1 is done. Keep a few problems a week to stay sharp and move most of your time to practicing out loud.
Which should you try first?
- You freeze but know the material: take DevInterview.AI's free interview this week, set to your target company and level, then do a spoken mock most days. Every rating we have ever received is public on our reviews page.
- You want human nerves in the mix: add peer mocks on Aced (formerly Exponent), 5 free a month.
- Your onsite is next week: a mock every day, plus one interviewing.io session if budget allows.
How we evaluated
The study figures come from NC State's published summary of "Does Stress Impact Technical Interview Performance?", a 2020 study by researchers at NC State and Microsoft. Prices come from each vendor's own pages, checked between October 13 and October 14, 2026. The drills and the number of mocks are our view, not a study's. We build DevInterview.AI, so we also listed the free options.
FAQ
Why do I freeze in coding interviews when I can solve the problems at home?
Because the interview changes the conditions: someone is watching, you have to explain while you think, and the clock does not stop. In a randomized study by researchers at NC State and Microsoft, students who solved a problem in front of an interviewer performed half as well as students who solved it alone in private. In our view, solving more problems alone does not train that; rehearsing out loud while being watched does.
How do I stop going silent in a technical interview?
Keep talking with a script: restate the problem, work a small example by hand, state the brute force and its complexity, or ask a clarifying question. Silence reads as stuck, while narrated thinking reads as problem solving, even before you have found the answer.
How many mock interviews does it take to stop freezing?
In our view, ten or more full spoken mock interviews, most days in the final two to three weeks, until the format feels boring. One or two are never enough, because the first few are spent getting used to being watched. DevInterview.AI's unlimited plan, $19.99 a month with the first interview free, is built for that volume.
Is it normal to blank out in a coding interview?
Yes. Being watched measurably lowers performance: in a 2020 randomized study by researchers at NC State and Microsoft, it cut performance in half and raised stress. In our view, the candidates who recover are the ones who have practiced blanking out loud and know what to say next.