foundation
Thinking out loud
Narrate assumptions, options, checks, and uncertainty so interviewers can evaluate reasoning, not only the final answer.
Thinking out loud lets interviewers follow your reasoning: state the problem in your words, list assumptions, outline options, verbalize checks, and admit uncertainty. Silence forces interviewers to guess—or assume you cannot communicate under pressure.
"I'll assume read-heavy feed, 10M DAU, p95 < 200ms.
First I'd clarify write rate and consistency needs.
Options: cache-aside vs push fanout vs hybrid...
I'll start with cache-aside because..."
| Do | Avoid | |----|-------| | Periodic summaries | Long silent coding | | "I'm checking X because..." | Jumping to final answer | | Ask clarifying questions | Pretending certainty |
On interviews: practice a 30-second opening before touching the whiteboard or editor.
Common pitfalls: treating the interview as a performance test only; not inviting hints; rambling without structure.
The trade-off is slower initial progress versus higher signal on how you collaborate in real teams.
Checklist:
- Restate problem and assumptions.
- Narrate option exploration.
- Say what you would verify next.
- Invite feedback at decision points.