Why Interviewers Want to Hear You Think

The plain-language idea

Imagine watching two people assemble furniture. One works in total silence and hands you a finished chair. The other talks the whole way through — "this screw looks like it goes here, let me check the diagram, actually I had that backwards" — and hands you a chair that's slightly wobbly.

Which one would you trust to assemble a harder one next, without instructions? Probably the person who talked. You watched them catch their own mistake. You have no idea how the silent person got their result — skill, luck, or memorizing this exact chair before.

An interview isn't a test of whether you can produce a correct answer. It's a test of whether you can think, in a way another engineer can watch and trust. A silent correct answer gives almost no signal — just a coin flip's worth of evidence you're good at this one problem. A narrated attempt, even incomplete, shows exactly how you reason and recover from a wrong turn. That's what they're actually hiring for.

See it in a real thing: two ways to say the same thing

// SILENT approach: interviewer sees this appear on the screen with
// no explanation, and has to guess how you got here.
function hasPair(nums, target) {
  const seen = new Set();
  for (const n of nums) {
    if (seen.has(target - n)) return true;
    seen.add(n);
  }
  return false;
}

// NARRATED approach — same code, but said out loud first:
// "I'll brute-force this first: check every pair, that's O(n^2).
//  But I notice I keep re-checking numbers I've already seen — what
//  if I remember them instead? A Set gives me instant lookup, so as
//  I scan once, I can ask 'have I seen the number that would pair
//  with this one?' That gets me to one pass, O(n) time."
function hasPair(nums, target) {
  const seen = new Set();
  for (const n of nums) {
    if (seen.has(target - n)) return true; // "the complement I need"
    seen.add(n);                           // "remember this one too"
  }
  return false;
}

The code is identical. The second version gives the interviewer a window into why it works, which is the entire point of the exercise.

What people usually miss

Watch out

• Believing narration makes you look less confident. It's the opposite. Interviewers have sat through many silent candidates who froze completely — a narrated struggle reads as composure, not weakness.
• Only narrating once you've already figured it out. The value is in narrating the figuring-out itself — the dead ends, the "wait, that won't work because," the moment the idea clicks. That's the part a silent candidate hides entirely.
• Thinking a partially-solved, well-narrated problem scores worse than a fully-solved silent one. Often the reverse is true. A narrated partial solution proves you can reason under pressure — which is the actual job.

The genealogy: this pairs with the framework

The six-step framework from earlier in this track gives you something concrete to narrate — "restating the problem," "trying a small example," "starting with brute force" are all natural things to say out loud, in order, as you work through them.