Active Listening & Note-Taking
Your notes are the evidence. If you don't capture what the candidate actually said, the debrief becomes a game of telephone. This section teaches you to record the facts, not your feelings — and to pick the right follow-up in real time.
Two jobs at once
During an interview, you're doing two things simultaneously:
- Listening — following the candidate's story, tracking which principles are surfacing, spotting places to probe
- Recording — writing notes that capture what was said, not what you think about what was said
Most interviewers get the second part wrong. They write verdicts instead of evidence.
Record the session, not the sentiment
| Don't write this | Write this instead |
|---|---|
| "Great answer about ownership" | "Took on migration project outside her team's scope, rewrote data layer over weekend, got other team's lead to review Monday" |
| "Seemed nervous, not confident" | "Paused 10-15 sec before answering, asked to come back to this question later" |
| "Strong collaboration skills" | "Reached out to 3 teams, set up joint design review, proposed API contract compromise that split work by team strengths" |
| "Didn't demonstrate depth" | "Described the outcome but couldn't explain why they chose approach A over B when asked" |
| "Culture fit" | (Never write this — it's not evidence) |
Why this matters
Your notes serve two audiences:
- Future you — in 30 minutes, during the debrief, you'll need to recall specific details from a 45-minute conversation. Your memory will fail you. Your notes won't.
- The debrief panel — other interviewers will rely on your notes to understand what you heard. If your notes say "strong answer," they learn nothing. If your notes say what the candidate actually said and did, the panel can evaluate independently.
The note-taking framework
Keep it simple. For each question, capture:
- S/T — the situation and task in 1-2 phrases (enough to set context)
- A — the specific actions the candidate took (this is where most signal lives)
- R — the result, ideally with metrics
- Flags — anything that needs follow-up:
? follow up,need more info,look this up later
Abbreviations are fine. Misspellings don't matter. Speed matters. You can clean up your notes in the 5 minutes between the interview ending and the debrief starting. The goal is to capture enough that you can reconstruct the answer later.
Active listening while note-taking
The biggest mistake: writing with your head down and missing what the candidate is saying.
Strategies that work:
- Shorthand over sentences — write "took on migration, rewrote data layer, weekend, other team's lead reviewed Mon" not complete sentences
- Listen for the Action — the Situation and Task are context; the Action is where the signal is. If you have to choose what to capture, capture the actions
- Note your probing instinct — when something catches your ear, jot a
?in the margin. Come back to it after the candidate finishes the current answer - Separate facts from flags — use a simple marker (like
→for facts and?for things to probe) to keep observation and evaluation apart
Picking the right follow-up
While you're listening, you should be preparing follow-up questions in advance. Then, as the candidate speaks, match their answer to your prepared follow-ups:
- Did they use "we" a lot? → follow up on individual contribution
- Did they mention a decision but not the reasoning? → follow up on tradeoffs
- Did the story sound too clean? → follow up on what went wrong
- Did they skip the result? → follow up on measurable outcomes
The best follow-up is the one that generates the most new signal — signal you don't already have from their initial answer.
Scenario 1: Priya — Ownership
The Candidate: Priya is a senior software engineer with 6 years of experience. She's been at her current company for 3 years, working on the payments platform. She's interviewing for a senior role on your infrastructure team.
Your Question: "Tell me about a time you took on something important that wasn't part of your job description."
Step 1: Listen and take notes
Listen to Priya's answer. While you listen (or read), take notes as if you were the actual interviewer. Remember: capture facts and data points, not your verdict.
Take notes on Priya's answer as if you were the interviewer.
Your job is to capture the STAR components: Situation, Task, Action, Result. Record key data points, specific actions, and measurements. Abbreviations and shorthand are fine. Flag missing STAR components or things you'd follow up on.
This exercise supports AI-powered coaching via Claude. Enter your access code to enable it, or use the offline feedback below.
Step 2: Compare your notes
Click through these three note-taking styles. How do yours compare?
Step 3: Pick your follow-up
Now review your notes through the STAR lens. Which component is weakest or missing? The best follow-up targets the gap.
In Priya's answer, the Situation is clear (payment failures, no monitoring), the Action is detailed (error log analysis, proposal, building alerts), and the Result has metrics (MTTD 45min → <5min). But what about the Task? She said it "wasn't my team's responsibility" — so what made her take it on? The Task is implicit, and probing it would reveal her decision-making process.
Based on what you heard, which follow-up would generate the most new signal?
Scenario 2: Marcus — Collaboration
The Candidate: Marcus is a product manager with 4 years of experience, currently at a mid-size fintech company. He's interviewing for a senior PM role where he'd work across engineering, design, and data science teams.
Your Question: "Tell me about a time you needed to get buy-in from people who didn't report to you."
Step 1: Listen and take notes
Take notes on Marcus's answer as if you were the interviewer.
Capture the STAR components: Situation, Task, Action, Result. Record data points, specific actions, and measurements. Flag any missing STAR components or areas to probe.
This exercise supports AI-powered coaching via Claude. Enter your access code to enable it, or use the offline feedback below.
Step 2: Compare your notes
Step 3: Pick your follow-up
Review your notes through the STAR lens again. Marcus's Situation is clear (3 teams, own roadmap priorities, DS skepticism). The Result has metrics (6 weeks, 23% conversion). But look at the Action — he describes his strategy at a high level ("set up working sessions," "synthesized their input") without specifics on what happened when constraints conflicted. The Action needs more depth.
Based on what you heard, which follow-up would generate the most new signal?
During the debrief, you look at your notes and they say: 'Impressive answer, clearly a strong owner, would hire.' What's wrong with these notes?
A candidate gives a 3-minute answer and you're still writing notes from the previous question. What should you do?
A candidate's answer has a clear Situation, detailed Actions, but their Result was simply 'it was successful.' What is the best follow-up?