Candidates in a contested search often say early what would make them choose you, and they say it to the recruiter: the other processes they are in and how close each one is to an offer, and what it would take for them to leave. By the hiring manager’s interview, the applicant tracking system (ATS) holds one line about it. By the closing call it lives in one recruiter’s head.

An interview intelligence platform earns its place when what a candidate says in one conversation changes the next one. A recording that sits unopened until the debrief leaves a team no further ahead than one that never recorded the call, so the method below is about turning each conversation into instructions for the ones after it.

That is where I’d look for an edge in a contested hire. I think a candidate weighing two offers notices which company put the person they asked to meet on the panel, and which closing call answered the worry they raised in the first week. Both happen only if someone on your side read the earlier call and did something about it, which is a habit more than a headcount question.

Choose the conversations your interview intelligence platform records.

Start with a list of every conversation a candidate has with your team in a typical search, and mark the ones that come with a scorecard. The scored interviews are the obvious ones to record, because that is where the evaluation happens. I’d record the unscored calls before adding anything else.

These four carry no form, and they are where a candidate tends to talk about what they want:

• The recruiter screen, often the first place a candidate mentions other processes and why they want to move.
• The hiring manager’s informal call before the formal loop.
• A check-in while the candidate waits between rounds.
• The closing call, where someone sells the job and hears the objections.

Without a record of these, the scored interviews tell you how the candidate did and leave you guessing at what they are deciding. Recording them needs the candidate’s agreement like any other call, under your team’s own consent process. Say at the screen which calls will be recorded and who on the team reads them, so the later reading never comes as a surprise to the candidate.

Turn what the candidate said into instructions for later calls.

A recorded call helps you win the candidate only when it changes what your team does next. So when a conversation ends, the person who ran it writes down what the candidate said that should alter a later conversation, and names who it is for. For a typical loop I’d start from a short list like this one and add to it per role.

Leave the list unwritten and the information still exists somewhere in the notes, where it changes nothing. The panel goes ahead on the original date, and the closing call runs the same pitch the recruiter gives everyone.

I’d put each instruction in the invite for the conversation it changes, with a link to the notes it came from, because the invite is what its owner opens in the minutes before they join. How an interviewer writes up their own call for the people after them, with two templates, is covered in interview summary best practices.

Keep one running note on what would win the candidate.

The instructions each cover one later call. The person who closes needs the whole picture in one place: what would make this candidate say yes, and what is pulling the other way? Keep that as one note per candidate, added to after every conversation.

The note holds the other processes and where each one stands. It also holds the reasons the candidate has given for moving and the worry they keep coming back to, in their own words wherever you have them.

I’d give the note one owner, the recruiter, because a document everyone can edit is one where each person assumes someone else added the last call. The closer reads it the day before the closing call and again an hour before it.

Some of what goes in this note is a warning that a counter-offer is coming, and the phrases that tend to give that away are listed in the counter-offer signals candidates say out loud.

Bring what candidates asked into the next intake.

When a search closes, hire or no hire, the recruiter has heard more about how the role lands with candidates than anyone else on the team, and that knowledge usually stays with the recruiter. Hand it to the hiring manager at the intake for the next similar role.

Bring the questions candidates asked most often about the role, and the concerns that came up in more than one conversation. If finalists who withdrew told you where they went or why, bring that too, in their words.

The hiring manager can then change something before the next search starts, such as the pitch the screen opens with, or an interview that keeps repeating another one. I’d hand questions back after hires as well, because the questions candidates asked are the cheapest research a hiring manager will get on how the role sounds from outside.

Where Metaview fits in interview intelligence.

Each part of the method is a habit your team keeps, and Metaview supplies the record it runs on, plus a quick way into that record for someone with a few minutes before a call.

Every call your consent process has cleared for recording can be captured, informal ones included. The Metaview Notetaker joins as a visible participant and records and transcribes, then writes the conversation up as structured notes. The running note can carry the candidate’s own phrasing, instead of the recruiter’s memory of it, because the Notetaker on those calls captures every spoken word.

Templates can be set for a team or a whole workspace, so every recruiter screen comes back with the same sections, the candidate’s motivations among them. A recorded call can also be switched to a different template after it ends, which is the picker shown here.

1

2

3

1. 1“Recruiter Screen,” an eight-section template whose sections include the candidate’s motivations and logistics.
2. 2“Role Alignment,” described on its card as mapping the candidate against the job description’s requirements.
3. 3“Use Recruiter Screen,” which applies the chosen template to this call.

I’d still set the screen template for the whole team before a search opens, so switching after the call stays the exception and every screen carries the motivations section the running note draws on.

For the running note itself, multi-source notes turn the calls and files you attach, the resume and job description included, into one notes document, so the recruiter preparing the close starts from a single page. They cover only the calls and files attached to them, which is one more reason to record the unscored calls.

I’d treat the close as the call that most needs the record, because it is the last chance to answer what the candidate raised earlier. In a post on the habits of strong interviewers, Metaview’s co-founder and technology chief put the stakes of a missed close in one line:

He wrote it about interviewers, and it applies with more force to the recruiter on the closing call, which is why the running note goes to them first.

Brandon Miles, Head of Executive Recruiting at Brex, describes the calls his team uses it on: “Whether it’s doing a catch-up call with a candidate, super informal, checking in with a hiring manager, or trying to close a candidate, we’re using Metaview.” Two of the calls he lists, the catch-up and the close, are candidate conversations with no scorecard attached. If your recording stops at the scored loop, those two are where I’d extend it.

For the intake, ask the Metaview Assistant a question in plain language, such as what candidates for the role asked about the team, and it answers from your own captured interviews, recalling specific details across the pipeline. It reads only what Metaview captured, and it leaves the conclusions to the people in the intake.

Ask the closer where their first line came from.

The next time a candidate in another process reaches the closing call, ask the recruiter running it one question beforehand: what will you open with, and where did it come from?

An answer that traces to something the candidate said, in the running note or in an instruction passed on from an earlier call, means the method is working on that search. If it comes from the usual pitch for the role instead, the record exists and no one acted on it. The gap then sits upstream of the close, at whichever call heard the thing and passed it to no one.

In the next search, that question becomes part of preparing every contested close. Recruiters start writing the running note expecting to be asked, and the hiring manager starts hearing, before the offer goes out, which of the candidate’s own reasons the close will lean on.