All articles

Interview prep, 5 min, October 17, 2026

How to think out loud in a coding interview

Silence is the quiet killer of coding interviews. Here is how to narrate your thinking so the interviewer can follow — and help — you.

A speech bubble over a keyboard, representing narrating your work

A coding interview is as much a communication test as a coding test. Two candidates with the same solution get very different outcomes based on whether the interviewer could follow their thinking.

A script that always works

  • Restate the problem in your own words and confirm it.
  • Call out the inputs, outputs, and edge cases.
  • Describe a brute-force idea first, with its complexity.
  • Say how you would improve it, and why.
  • Only then start coding — narrating as you go.

Narrate decisions, not keystrokes

You do not need to read every line aloud. Explain the choices: “I will use a hash map here so lookups are constant time.” That is what shows the interviewer how you reason.

“The interviewer cannot give you a hint if they cannot tell where you are stuck. Thinking out loud is how you let them help.”

Practising the skill

Record yourself solving a problem and play it back. It feels awkward, but it is the fastest way to notice long silences and vague explanations. Mock interviews with a friend do the same job.

Try it on your next question

Reptor reads a question on your screen and answers it with the model you choose — plus a short explanation so it sticks.

Download Reptor