做過 300 道 LeetCode 題仍在面試中卡住？Hamza Ibrahim 認為問題在於缺乏排演
Solved 300 LeetCode Problems but Still Freeze in Interviews? It's a Rehearsal Problem
做過 300 道 LeetCode 題仍在面試中卡住，Hamza Ibrahim 將原因歸於缺少在他人注視下口述解題的排演，而非知識不足。2020 年一項由 NC State 與 Microsoft 研究人員進行、涵蓋 48 名電腦科學學生的研究發現，受注視並向面試官講解的組別表現只有獨自作答組的一半，壓力及認知負荷顯著較高；研究並未測試練習效果。
I built DevInterview.ai, a mock interview tool, so take the product part with that in mind. The rest of this is free.
If you've solved hundreds of LeetCode problems and still freeze in real interviews, you don't 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.
Why 300 problems didn't fix it
A real interview adds three things solo practice never does: someone watching, explaining while you think, and a clock you can't pause.
A 2020 study by researchers at NC State and Microsoft tested exactly this with 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. The watched group performed half as well, with significantly higher stress and cognitive load.
The study didn't test practice. But in my view, solving more problems alone won't move that number, and practicing under the watched, spoken condition will.
Four drills
- Narrate every practice problem. From the first read: restate the problem, walk an example, name the brute force and its complexity, then improve it. If talking makes you slower, good. That's the skill being trained.
- Learn a script for blanking. Freezing isn't 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's slow, or ask a clarifying question.
- Practice being watched. Full mock interviews, timed and spoken. Start them weeks before the interview, not the night before.
- Repeat until it's boring. 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, 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 with an experienced engineer | From $179 a session |
| Narrating alone | Your 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 told never to say whether you're 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, 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 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 gets you an experienced human's read. Use it to calibrate, not for volume.
Where this fits
Freezing is a problem with the practice step, not the study step. The plan I'd give a friend: learn the patterns on NeetCode, study system design on Hello Interview, practice out loud on DevInterview.ai, and, super optional, one human session on interviewing.io. With 300 problems behind you, step 1 is done. Keep a few problems a week and move most of your time to practicing out loud. The full 8-week version is here.
Prices checked on each vendor's own site on October 13 and 14, 2026. The full article, with sources, is on devinterview.ai.
來源：DEV Community · dev.to