Read the last rejection email your team sent a finalist. If it could have gone to anyone, the candidate noticed, and so will the people they describe the process to.

The candidate experience best practices below share one habit: carry each candidate’s own words into every later conversation with them. I think that habit is the cheapest way to personalize at scale, because it asks for a few lines of notes per candidate and no extra hours from the team.

The ten follow the candidate from the first reply to the weeks after a no.

What candidates judge between rounds.

Between interviews, a candidate has little to go on except how your team treats them, so they read the process as a preview of the job. A slow reply suggests a team that’s stretched thin, and a question they answered last week suggests colleagues who don’t talk to each other.

It’s tempting to read every candidate complaint as a complaint about speed and cut a round. Speed helps, and it’s one of the ten below. But a fast process that forgets what the candidate said still reads as a template, and I’d expect a candidate weighing two offers to notice which company remembered them.

Personalizing at scale sounds expensive because it gets pictured as more time per candidate. Most of the material already sits in the notes from the first call: what the candidate wants from the move and what worries them about it. The work is to reuse the first-call notes with whoever speaks to the candidate next.

Ten candidate experience best practices, in the order candidates meet them.

These ten follow the candidate through your process, and each one says what goes wrong without it. The early ones feed the later ones: practice 3 supplies most of what practices 8 and 9 need.

1. Reply to every applicant, including the ones you turn down.

Silence is the failure every applicant can see, and the cheapest one to fix. An application that gets no answer leaves the candidate checking their inbox for weeks and deciding for themselves what the silence means.

Send a short, honest no as soon as the decision is made, and tell the applicants still in review when they’ll hear. For people you never interviewed, two or three plain sentences are enough. Keep the specifics for the later stages, where you have something specific to say.

2. Walk through the whole process on the first call, then send it in writing.

On the recruiter screen, go through the process with the candidate, then send the same plan in an email they can come back to:

• the stages, in order
• who they’ll meet at each stage
• what each round looks at
• when you expect to make a decision

A candidate who knows the plan can wait a week without wondering whether they’ve been dropped. Without it, every day with no news reads as bad news, and the candidate starts saying yes to other processes while they wait.

3. Write down what the candidate tells you, in their words.

Candidates tell the recruiter on the first call why they’re moving and what would stop them saying yes. Write both down verbatim, under headings of their own, so anyone who speaks to the candidate later finds them in seconds.

Practices 8 and 9 can only be personal if these notes say something personal. A screen note reading “solid background, keen on the role” leaves the close and the rejection with nothing to quote.

4. Brief each interviewer before their round.

Before every interview, send the interviewer what the candidate has said on earlier calls, in their words, and the competencies this interviewer owns. An interviewer who starts from the resume alone tends to ask what the last one asked, and the candidate spends the loop repeating themselves.

With the brief, the second interviewer can open where the first left off: “You mentioned the migration project in your first interview. What went wrong with it?” If the candidate told the recruiter they were uneasy about something, say the on-call rota, the interviewer who knows that area can raise it before the candidate has to.

5. Give each interviewer different ground to cover.

Split the competencies the role needs across the panel so each one has a single owner, and have every interviewer score against a shared rubric. Each interviewer then asks about something the candidate hasn’t covered yet, and the candidate leaves having shown four sides of their work.

A separate piece on writing interview rubrics covers how to tie each score level to evidence.

6. Leave room for questions from the candidate in every round.

Tell the candidate why you’re asking a question when the reason won’t be obvious to them, and stop for their questions halfway through the interview as well as at the end. A candidate who only gets five minutes at the close to ask about the job has spent the rest of the hour being assessed.

Write down what candidates ask and what you answered, so the next interviewer gives them the same answer.

7. Keep the gaps between rounds short, and tell candidates when to expect news.

Book the debrief before the first interview happens, and ask interviewers to submit written feedback within a day of their round, so the decision never sits waiting on one person’s notes.

Then look at each stage and ask whether it changed a recent decision. If a round didn’t move the call on any of your last ten decisions, merge it into another round or cut it. When a delay can’t be avoided, write to the candidate before the date you gave them passes, and say why.

8. Close on what the candidate told you they wanted.

Before the offer call, reread the screen notes. Open with the reason the candidate gave for moving, as close to their own words as you can, and answer the worry they raised on the first call, whether that was the commute or the size of the team they’d join.

Name one or two things the panel saw in this person, and tie each one to something they told you they want from the role, because an offer call that covers only pay and the start date could have been made to anyone.

9. Give finalists a specific reason when you say no.

A candidate who reached the last round has given you hours of their time, and a no that names nothing they did tells them those hours went unread. Write two things: a strength the panel saw, and the gap that decided it, both in terms of the role and of what they told you they were looking for.

Check the wording with whoever owns your legal guidance, and keep the substance through that review.

A piece on giving recruitment feedback that helps covers how to turn interview notes into feedback a candidate can act on.

10. Stay in touch with the finalists you nearly hired.

The finalist you turn down this quarter may be the right hire for the next opening, or the person who refers one. When you send the no, ask whether they’d like to hear about future roles. If they say yes, write down what they’d want next in their own words, and get in touch when a role fits it.

A check-in that quotes back what the candidate told you a year ago is practice 3 paying off a second time.

Keeping past candidates warm between roles is the subject of a guide to building a talent community.

Where Metaview fits in candidate experience.

Most of the ten are habits your recruiters and interviewers keep, and the interview itself stays their work. For these practices, Metaview’s part is the record: what each candidate said, kept where the next person can find it, so practices 3, 4, 8, and 9 stop depending on someone’s memory.

Application Review helps with the decision behind practice 1 by sorting the role’s applications into fit buckets against the ideal candidate profile, with its reasoning attached to each one. A recruiter still decides on each application, progress or reject, before the reply goes out.

Keep what each candidate said with the Notetaker.

Metaview’s Notetaker records each interview and keeps a transcript, with structured notes the next person can read. Each record captures every spoken word, and that lets the finalist rejection in practice 9 name what they were after in the job, using the terms they used.

At Brex, Senior Go-to-Market Recruiter Pooja Chand said of using Metaview across interviews and recruiter calls: “It allows me to be a more credible recruiter. We can be more present in conversations.” I read that as practice 6 made easier, since an interviewer with attention to spare can stop for the candidate’s questions.

A notes template for the recruiter screen can carry one heading for the reason they’re leaving their current job and another for what would stop them. Those two headings are the first thing I’d reread before an offer call or a finalist no.

1

2

3

1. 1An overview of the candidate’s background opens the screening call notes.
2. 2A heading of its own keeps the candidate’s pay expectations and what motivates them, ready for the close.
3. 3Templates are set per kind of conversation, down to debrief calls after a technical assessment.

For practice 4, multi-source notes combine several interviews and documents, such as the resume, into one notes document the next interviewer can read before their round.

Compare talk time and punctuality across the team in Reports.

Metaview Reports tracks candidate talk time and punctuality across interviewers and roles, using the interviews captured in your workspace. The screen below shows the team average for each, and the split by interviewer is where I’d look for anyone who talks through most of the hour or joins late.

Across many candidates, Metaview Reports also surfaces why they’re looking to move and what gives them pause about joining. That tells you what the close in practice 8 should answer before the candidate raises it.

1

2

3

1. 1The “Talk time” report tracks average candidate talk time across interviewers.
2. 2The “Punctuality” report tracks average punctuality across interviewers.
3. 3Each cell counts the questions one interview spent on one competency.

Check your process against what candidates told you.

Pick a role you’ve hired for recently and read your own paperwork for it the way a candidate would. Each check below ties back to one of the ten.

• Reread the rejections your last five finalists received. Any that could have gone to a different candidate unchanged sends you back to practice 9, and to the screen notes it should have drawn on.
• Take three recent offer calls and set each one against the worry its candidate raised on the first call. If no call answered that worry, practice 8 is the one to work on.
• After each round, ask the candidate whether the interviewer seemed to know what they’d already told the team. Several no answers mean the brief in practice 4 isn’t reaching the panel.
• Count the applicants for that role who have heard nothing at all. Anyone on that list is a practice 1 problem.
• Set each wait between rounds against the date you gave the candidate. A wait that ran past its date belongs to practice 7.

Whatever the checks turn up, I’d begin with practice 3. Writing down each candidate’s words takes a recruiter a few minutes per screen, and those notes let the close and the rejection sound personal for every candidate the team sees.