How to Think Out Loud in a Coding Interview

In a coding interview, silence isn't golden — it's the interviewer slowly losing the plot of what you're doing.

Two candidates write identical code. One narrates their thinking; one works in total silence and only speaks to announce the answer. The narrator gets the offer, even if their code was slightly worse. Coding interviews aren't a typing test — they're a “show me how you think” test, and you can't show thinking you keep to yourself.

Why silence costs you

The interviewer can't follow you. If you go quiet for four minutes and emerge with code, they have no idea whether you reasoned or guessed.
They can't help you. Interviewers nudge candidates who are on the right track — but only if they can hear where you are. Silence forfeits the hints.
Partial credit vanishes. If you don't finish, your reasoning is the only thing left to score. No narration, nothing to score.

What to actually say

Restate and clarify. “So we need… can I assume the input is sorted?” Confirms you understood and buys thinking time.
Talk through approaches before coding. “Brute force is O(n²); I think I can get it to O(n) with a hash map — let me go that way.”
Narrate as you code, lightly. Flag what each part does and why. Not every keystroke — the decisions.
Say when you're stuck, and how. “I'm worried about the edge case where the list is empty” invites a hint and shows rigor.

📣 The fix for all of this is reps. Run a free voice mock interview →

The trick is splitting your brain

Thinking and talking at once feels unnatural and gets harder under nerves — most people default to silence the moment the pressure rises. It's a coordination skill, and like any coordination skill it only becomes automatic with reps. Practise by solving problems out loud to literally no one. It feels ridiculous; it works. By interview day, narrating should feel like the default, not a second task competing for the brain you need for the problem.

Practice until the real interview feels easy

Run realistic voice mock interviews, get a scored report and a model answer for every question. Free to start — no credit card.

Start practicing free

Frequently asked questions

Why is thinking out loud important in coding interviews?

Because interviewers score your reasoning, not just your final code. Narrating lets them follow you, give hints when you're close, and award partial credit if you don't finish. Silence forfeits all three.

How do I get better at talking while coding?

Practise solving problems out loud, alone, until narrating feels automatic. Thinking and talking at once is a coordination skill that breaks under nerves unless you've rehearsed it.