Shortlisting candidates means choosing, from everyone who applied, the few people you’ll interview. Do it by writing down what the role needs before you read a single application, then deciding on each applicant from the evidence their application gives you against that list. Then go back and check some of the applicants you passed over.
The usual shortcut is to interview the strongest resumes. But a resume can look strong for reasons that have little to do with the job, such as a well-known employer or polished writing. It can also look weak because it leaves out something the applicant could show you in a short conversation. The people you set aside never get an interview, so you never find out whether they’d have done well in one. That’s why my advice is to shortlist on evidence, then check the pile you passed over.
This guide is for recruiters and hiring managers who decide which applicants to interview. It shows you how to set your criteria, read a resume for evidence, and decide who makes the shortlist. Then it covers how to check the applicants you passed over, and what to change when the check turns something up.
Write down your criteria before you start shortlisting candidates.
Criteria you write after reading a few resumes tend to describe those resumes rather than the job. Before you open the first application, agree two lists with the hiring manager:
- the must-haves: the requirements someone has to meet to do the job at all, such as a license the role legally needs
- what makes a strong applicant: the experience and skills that make someone likely to do the work well, with the most important first
For each item on both lists, write down what an application would have to show to meet it. “Experience managing a budget” is hard to check on paper. “Has owned the budget for a team or a project, and says what it covered” tells every reader what to look for.
Keep the must-haves short. Every must-have sets people aside, so keep only the requirements the job can’t be done without, and move anything you’d merely like to the second list.
You can’t check some criteria on paper at all, such as how someone explains a hard decision. Leave those to the interview. For help sorting your criteria between the application and the interview, read the guide to deciding what to screen for and what to leave to the interview.
Read each resume for the evidence it gives you.
A resume shows some things well and others badly. It’s good at showing where someone has worked and what they say they owned there. It’s poor at showing what the person did themselves and how they think. Read each application against your criteria with that in mind, and use the table below for the parts of a resume that most often mislead:
| What you see on the resume | What it tells you | What it doesn’t, so leave it to the interview |
|---|---|---|
| A well-known employer or a familiar job title | That the applicant worked there, with that title | What they did in the role, and whether it matches the work in yours |
| A result they claim, such as a project delivered or a target hit | That the applicant was close to the result | What they did themselves, and where things stood when they started |
| Polished, confident descriptions of the work | That the resume was written well, by the applicant or with help | Whether the work behind the words matches them |
| A gap, a career change, or an unusual path | That the career didn’t run in a straight line | Anything about ability on its own; ask about it only if it bears on a criterion |
When an application meets a criterion only in a vague phrase, such as “owned the migration,” count it as a partial match rather than a full one or a miss. Note the question you’d ask about it, and carry that question into the interview if the applicant makes the shortlist.
Decide who makes the shortlist.
Once your criteria are written down and you know what to look for in a resume, you can decide who to interview. Take these five steps for each role:
- Read every application against the same criteria, whatever order it arrived in. If you stop once you have enough applicants who look good, everyone who applied later gets a weaker chance, however well they fit.
- Set aside anyone who clearly fails a must-have, and write down which one.
- Sort the rest into strong, possible, and weak against your second list.
- Work out how many people you can interview from the first-round slots you and the hiring manager have, and fill the shortlist from the strong group first. Where the slots run out, draw the line between the applicants you’ll interview and the ones you set aside.
- Write one line for each applicant you shortlist and each one you set aside, saying why. A line such as “no evidence of owning a budget” lets someone else check your call later.
Close calls need different handling. When an applicant looks strong but the application doesn’t say whether they meet a must-have, ask before you reject. One written question or a short screening call settles it, and a wrong guess can cost you a strong applicant.
Where Metaview fits.
A shortlist is only as easy to check as the reasons written down behind it. When the reason for each call lives only in a reviewer’s head, a second reviewer can’t test it later. Checking is easier when every application keeps its reasoning next to it.
Metaview is the Agentic Recruiting Platform, and Application Review is the part of it that reads applications. It drafts an Ideal Candidate Profile from the job description and the context you give it, and that profile plays the part of your written criteria. Your team reviews, edits, and approves it before any application is read against it. Application Review then reads every application against that profile. It puts each one in a fit group, from Great down to Poor, and shows the reasoning behind it.
The reasoning stays with each application. Once a second reviewer has made their own read of an application, they can compare it with the reasoning for its fit group and see where the two differ.
When a second reviewer’s disagreement shows a criterion needs to change, your team updates the profile, and Application Review reads every application again against the new version.
When an application leaves a must-have unclear, you’ll often settle it with a short screening call. Where consent has been given, that screening call is captured by the Metaview Notetaker, which records and transcribes it, then turns the conversation into structured notes. The recording captures every spoken word, so the applicant’s answer about the must-have is there in their own words when you decide.
Metaview never rejects an applicant. A recruiter makes every call to progress or reject. A fit group is a first read of the application against your profile, not a prediction of how the applicant will do in an interview or in the job.
No read of an application is a prediction either, whether a person or artificial intelligence (AI) does the reading. Siadhal Magos, Metaview’s co-founder and chief executive officer, has described why a resume can’t carry the decision on its own:
A resume was never a complete representation of a person. Now that AI can help anyone create an immaculate application, the resume is becoming an even weaker signal when it stands on its own.”
That’s why the last part of this guide is about the applicants you set aside on paper: they’re the ones you know least about.
Check who your shortlist passed over.
Your process won’t tell you how the applicants you set aside would have done, so you have to look on purpose. Once a role’s first interviews are done, run these three checks:
- Ask a second reviewer to read a handful of shortlisted and set-aside applications against the same criteria, without seeing your decisions or your reasons. Where the two of you disagree, look at the criterion behind it. It’s usually vague, has no agreed evidence, or measures something the job doesn’t need.
- Set your one-line reasons beside how each shortlisted applicant did in the first interview. Look for patterns, such as applicants you rated strong on one criterion who keep falling short on it in the interview, or close calls who keep doing well.
- For the next batch of applicants to the same role, decide before you start reading that a few applicants just below the line will get a first interview. Choose people who meet every must-have, give them the same interview as everyone else, and if they do well, give them the same chance to move forward.
The first check tells you whether your criteria are applied the same way each time, but not whether they pick the right people, because two reviewers can apply the same poor criterion perfectly. Only the third check shows you some of the people your shortlist would have missed.
When the checks turn something up, change the criteria rather than only moving the line:
- If two reviewers read a criterion differently, rewrite it with the evidence that counts.
- If applicants you set aside on one criterion keep doing well in the interview, loosen that criterion, or drop it if the job doesn’t need it.
- If a strength on paper keeps falling short in the interview, give it less weight when you shortlist and test it in the interview instead.
- If a must-have is a real requirement of the job, keep it, even when it sets aside applicants who look strong in every other way.
Run the checks one role at a time, or across a few closely related roles, because each role has its own criteria.
If an AI tool reads your applications before you do, run the same checks on its ratings. The guide to AI resume screening covers how to sample the applications it rated lowest.
You’ll know your shortlisting works when the checks stop surprising you: a second reader agrees with your calls, and the applicants just below the line confirm where you drew it.
Check the reasoning behind every fit group.
See how Application Review shows why each applicant landed in their fit group, so you can check the people you passed over against your own criteria.
Frequently asked.
Does the strongest resume win the interview?
Not reliably. A resume and an interview show different evidence. The resume shows where someone has worked and what they say they did, and the interview shows what they did themselves and how they think. Use the resume to decide who to interview, and the interview to decide who moves forward.
How many candidates should you shortlist?
As many as you can interview well. Start from the first-round slots you and the hiring manager have, and fill them from your strong group. If the strong group is bigger than your slots, shortlist the applicants with the most evidence against your most important criteria. If it’s smaller, check whether a must-have is too strict before you fill the rest from your possible group.
What criteria should you use to shortlist candidates?
Two lists, agreed with the hiring manager before you read any applications: the must-haves the job needs, and the experience and skills that make someone likely to do the work well. Next to each one, write what an application would need to show.
Should you shortlist candidates who don’t meet every requirement?
Yes, when what’s missing is a preference rather than a must-have. Set aside applicants who clearly fail a true must-have, and weigh the rest of your criteria instead of treating them as boxes every applicant has to tick.
How do you make shortlisting fair?
Hold every applicant to the same written criteria, read every application whatever order it arrived in, and write a reason for every call. Have a second reader check a sample of your decisions, and ask your legal or compliance team to review the process for each market where you hire.