Interview Notes Template for Hiring Teams
By the time you're on the fourth interview of the week, the first three have blurred together. The candidate was "great," but great how? What did they actually say?
If you can't answer that from your notes, you weren't taking notes. You were taking impressions.
Impressions don't survive a debrief. When five people interviewed the same candidate and you have to agree on hire or no-hire, "seemed senior" and "felt like a fit" collapse the moment someone asks for an example. A template fixes that by forcing you to write down what happened, not what you felt about it.
Why interview notes matter
You're comparing people across days, sometimes weeks. Memory is not a comparison tool. Three things break without decent notes:
- Fair comparison. One candidate gets three paragraphs, another gets one line. That's not a comparison; it's a coin toss.
- A faster debrief. Panels argue opinions. Evidence ends arguments.
- A defensible decision. If a hire is ever questioned, "they had good energy" doesn't hold up. "They walked through the exact migration they led, with the numbers" does.
This template is built around one rule: capture evidence, not adjectives.
The template
Copy these fields into whatever you take notes in, a doc, a notebook, your notetaker.
Header
- Candidate, role, date
- Interviewers and stage: screening, technical, behavioral, final, or panel
Evidence: what they said. One line per question: the question, then the answer in their words. "Good with people" is an impression. "I ran new-hire onboarding for a 40-person team through two rounds of layoffs" is evidence.
Signals. Red flags, follow-up questions, anything you want to verify with a reference.
Recommendation. Hire, no-hire, or another round, plus a one-line reason that quotes the evidence.
That's the whole shape. The rest is discipline: write while it's happening, or immediately after. Never from memory the next day.
Three stage-specific formats
| Stage | What to capture | Example line |
|---|---|---|
| Screening | Years of relevant experience, key skills confirmed, salary and availability, first red flags | "7 years in SRE; notice period is 4 weeks" |
| Behavioral (STAR) | One row per competency: Situation, Task, Action, Result, plus a 1-5 score with a reason | "Conflict: handled the customer escalation end to end, kept the account" |
| Panel or final | The same rubric across every interviewer, evidence per competency, so the debrief compares notes not gut feel | "Three interviewers cite the same example for ownership" |
Build the template before the interview, not during it. A blank page in the middle of a conversation is how notes turn into a scramble.
What to write, what to skip
Write down what they said and did. Skip the adjectives.
- Write: verbatim answers, examples they gave, questions they asked, skills they demonstrated, numbers they quoted.
- Skip: how confident or nervous they seemed, how "senior" they felt. That's bias, not data.
- Never write: protected characteristics like age, family status, health, or religion, anything unrelated to the role. Keep notes about the work.
One habit that pays off: share the template with every interviewer before the loop starts. When everyone uses the same fields, the debrief compares the same things.
The mistakes that sink interview notes
- Uneven notes. Three paragraphs for one candidate, one line for the next. Same template, same effort, every time.
- Tone instead of content. "Great communicator" tells you nothing about what they said. Quote them.
- Notes lost in an inbox. They need to live where the whole hiring team can find them, not in one interviewer's personal folder.
- Skipping the write-up because "it went fine." An unremarkable interview is exactly the kind that gets confused with another one two weeks later. Write it down anyway.
Let the notetaker handle the typing
Typing while interviewing pulls your attention off the candidate, and if you're the interviewer you can't afford that. A meeting notetaker that records the call and turns it into a transcript means your notes come with the quote, the speaker, and the timestamp attached, so every point is grounded in what was actually said. No more "I think they mentioned something about..."
Meetbook records the meeting tab with no bot joining the call, then hands you a summary and action items where every point carries the quote it came from. For interviews, that's the difference between writing "strong on systems design" and pasting the actual answer. One rule before you hit record: tell the candidate you're recording and get their go-ahead first.
If you're recording interviews, here's the full guide. For the bigger picture on what these tools do and how to pick one, start here, and if you want a plain meeting minutes template for everything else, we have that too.