How to take interview notes without losing the candidate

The way to take interview notes without losing the candidate is to write less during the conversation and more straight after it: a few words of evidence while they talk, then the structure and the judgement in the ten minutes after they leave. Typing through an interview on Google Meet or Microsoft Teams costs you eye contact, follow-up questions and the candidate's best answers, and it quietly biases the notes towards whatever was easiest to type. This guide is for interviewers, hiring managers and recruiters, including those who interview for several companies at once.

Why does typing during an interview hurt?

It hurts twice.

It hurts the conversation. Candidates hear the keys and see your eyes drop to the screen, and they do what anyone does when the listener stops listening: they shorten the answer. The follow-up question you would have asked, the one that separates "I worked on the payments service" from "I designed the retry logic after the outage", never gets asked because you were finishing a sentence.

It hurts the assessment. Live notes record what was easy to capture, which means the candidate who speaks in tidy bullet points looks better on paper than the one who thinks out loud and gets to a better answer. You also miss what is not said: the pause before the answer about why they left, the change of tone when the topic turns to the team they managed. Those are evidence too, and they do not survive being typed.

There is a third cost that shows up later. Notes written live are a mixture of what was said and what you concluded in the moment, and by the debrief you can no longer tell the two apart.

Use a structure you can hold in your head

You need something light enough to carry while you listen. Two columns and three headings are enough.

The two columns are evidence and impression. Evidence is what the candidate said or did: a number, a name, a short phrase in their words. Impression is what you thought about it. Keep them apart on the page, and keep the second column short. If it starts to fill faster than the first, you have stopped listening.

The three headings are for afterwards: strengths, concerns and gaps. Gaps are the things you meant to test and did not get to, and they matter as much as the other two, because a gap in your interview is not a weakness in the candidate.

Before the call, write the questions down the left of the page with a blank line under each. During the call, put a word or two in each blank. After the call, expand the words into sentences while you still remember what they stood for.

Write what was said, not what you concluded

The single most useful habit: record the thing, not your verdict on the thing.

What you heard	Write this	Not this
"I built the payment service on my own over about four months, in Go"	Built payment service alone, about four months, Go	Strong backend engineer
"We had a bad outage and I was the one who wrote the post-mortem"	Wrote post-mortem after outage; asked to see it; owned the follow-up	Takes ownership
A long pause, then "it wasn't a good fit", about the last role	Paused on the leaving question; said "wasn't a good fit"; did not elaborate	Evasive

The right-hand column is not useless. It is just not evidence, and it belongs in the debrief, not the notes. When a phrase carries weight, quote it. "I would rather ship something I can maintain" is worth more than any adjective you can attach to it.

Defer the verdict to the debrief

Block ten minutes straight after the call, before the next meeting, and use them to fill in strengths, concerns and gaps from the evidence column. Write the recommendation then, in your own words, and date it. A recommendation written during the interview is a first impression with a heading.

If several people interviewed, each writes their notes before reading anyone else's. The point of a panel is to get separate views; the first person to share a verdict in the group chat removes that point.

Handle salary and notice period honestly

Only record figures that were actually stated, as they were stated. "Around six thousand" is what was said; "six to seven" is your inference, and by the offer stage nobody will remember which it was. If the candidate said nothing about salary, write "not discussed". If you did not ask about notice period, write "not asked". Never fill the gap from the CV, from the recruiter's email, or from what similar candidates usually say.

The same applies to start dates, location and anything else that turns into a term of the offer. The notes are the record of what the candidate told you. Keep them that way and the offer conversation is short.

Tell the candidate a notetaker is present

If a notetaker bot joins the call, say so in the invitation and again in the first minute: what it is, what it produces, who will read the notes and when they are deleted. Offer to remove it. A candidate who says no has told you nothing about their suitability, and you take notes by hand instead.

Do not record first and mention it later. It is the fastest way to lose a candidate you wanted, and the one thing they will tell their friends about your process. Recording norms differ by country and by company, so check what applies where you and the candidate are, and follow the stricter one.

Keep candidates for different companies apart

Recruiters, fractional hiring leads and consultants often interview for several companies in the same week. The risks are the ones any multi-client work has: one notebook, one search box, one AI assistant that has read everything. A candidate's notes from one company's process must not surface in another's, and one company's compensation bands must not leak into a rival's interview.

Keep one workspace, folder or notebook per hiring company. Name files by company code and role, then candidate, so a search for a common first name does not return two companies' pipelines. Delete a company's interview notes when the search closes or when the retention period you agreed with them ends. The general discipline is the same as for any client's notes, and it is covered in how to keep client meeting notes separate.

How TrackHeros does it

TrackHeros has an Interview summary profile alongside the Project meeting one. It extracts the candidate, the role and the interviewers; an assessment written as strengths, concerns and gaps; the salary expectation and notice period only if a figure was actually said aloud; the recommendation in the interviewers' own words, never the model's; and the agreed next step. Any meeting can be summarised as an interview with one click, and a client's minutes template can make it the default for that client. Speaker attribution is never guessed: a line that cannot be attributed is labelled "Unknown" rather than assigned to the most likely person.

The result is a minutes document you can export as PDF or copy into an email. Each hiring company can be its own client workspace, with its own sealed set of interviews, and the bot joins Google Meet and Microsoft Teams calls under a visible name you can set per client. Pushing notes to an applicant tracking system and scorecards are not yet available. The interviewer's use case is at /for/interviewers/, the document at /features/meeting-minutes/, and the bot's behaviour in a Meet call at /features/google-meet-notetaker/.