For a long time I prepared for coding interviews by solving problems silently. I could solve medium problems on my own, then froze in real interviews. The problem was not the algorithms. It was talking while thinking.
Silent practice hides the real skill
In a live coding round, the interviewer is grading your communication as much as your code. They want to hear you clarify the problem, propose a brute-force approach, explain why it is slow and then improve it. If you have never practised narrating, the first time you do it is under pressure.
My routine now
- Read the problem aloud and restate it in my own words.
- Ask two clarifying questions, even if I think I know the answer (input size, edge cases, duplicates).
- Say the brute force first and its complexity.
- Talk through the optimisation before writing a line of code.
- Code while narrating what each block does.
- Test with one normal case and one edge case out loud.
I set a 35-minute timer for each problem.
Reviewing the session
After each run I review what I actually said. I started using ClapAssist for this, since it has a coding mode and gives a recap of the session, but a simple screen recording works too. The goal is to catch habits like going silent for two minutes or skipping complexity analysis.
What changed
Within three weeks my mock interview feedback shifted from "good solution, hard to follow" to "clear communicator." Same algorithms, very different result.
If you are grinding problems but struggling in real rounds, try practising out loud for a week. It is uncomfortable at first and then it becomes your biggest advantage.
Top comments (0)