How to Shortlist Job Applicants When There Are Too Many

The pile problem

You posted the job on Monday. By Wednesday you have 214 applications and a business to run. You open the first ten, get a headache, and start doing the thing everyone does when they're overwhelmed: reading fast, judging on gut feel, and stopping when you hit "good enough."

The problem isn't that you can't find good people in there. It's that you're trying to evaluate 200 applications with a process built for eight. That doesn't scale, and it quietly punishes the candidates who applied last, because by then you're tired and skimming.

Here's a system that holds up whether you have 20 applications or 500.

Decide the disqualifiers before you open a single CV

Write down two or three things a candidate must have, not things that would be nice. Do this before you look at any application, while you're still thinking clearly about the job rather than reacting to a person.

Examples that actually work as filters:
- Must be legally able to work in the country, no sponsorship
- Must have used the specific software or done the specific task (not "experience with tools like this")
- Must be within commuting distance, or explicitly open to remote

Write these down somewhere you'll actually check them against, not just in your head. "Good vibes" is not a disqualifier and shouldn't be doing this job.

Add one knockout question to the application form

If your job posting or application form lets you ask a short question, use it. One well-aimed question does more sorting than an hour of CV reading, because it catches the people who didn't read the ad at all.

Good knockout questions are specific and answerable in one line:
- "This role requires working Saturdays. Can you commit to that?"
- "What's the name of the tool you'd use to build a monthly report in Excel?"
- "This is based in [city]. Are you currently able to work from there?"

Anyone who skips the question, or answers something that shows they didn't read the posting, goes to the bottom of the pile without you having to open their CV at all.

Batch, don't trickle

It's tempting to review applications as they land, especially the first few because you're excited about the role. Resist it. If you screen the first 20 candidates on Monday and the next 180 on Thursday, you're not comparing them fairly — you're comparing Monday-you against Thursday-you, and Thursday-you is tired.

Set a deadline, let applications collect, and review them all in one or two sittings. It's less satisfying but it's fairer, and fairer usually means better hires.

Time-box the first pass

Give yourself something close to 90 seconds per CV on the first read. You're not deciding who to hire — you're sorting into three piles: yes, no, and maybe. Don't argue with yourself about the maybe pile yet. That's what the second pass is for.

The discipline of a strict time limit does something useful: it forces you to look for the two or three things you actually said mattered, instead of getting pulled into a long, well-formatted CV that says nothing concrete.

For high-volume or entry-level roles, test before you talk

If you're hiring for a role where dozens of people are plausible on paper — a call centre agent, a data entry role, a junior sales position — CV screening alone won't separate them. Everyone has the same three bullet points.

In that situation it's worth putting a short task or skills check in front of the phone screen rather than after it. It costs the candidate ten or fifteen minutes and does the sorting the CV can't. This is one of the few places where a tool genuinely earns its place instead of adding a layer of process for its own sake — something like AssessFit lets you send a short test to everyone who clears the knockout question, and only the people who actually do well get a slot in your calendar. Worth knowing the CV itself is capped at 30% of the final score in that kind of system, and it's free for the candidate either way, so you're not asking people to pay for the privilege of applying.

If a tool isn't in the budget or the role doesn't need one, a homemade version works too: a two-question written task, a five-minute call where you ask them to walk through something specific, anything that makes them do a small piece of the actual job instead of describing it.

Notice the shortcuts that become bias

Under time pressure, your brain reaches for shortcuts, and some of them quietly become discrimination. Sorting by university name. Skipping anyone with a gap in their timeline without reading why. Giving extra warmth to a name that sounds familiar. None of this is usually deliberate — it's what happens when you're moving fast.

This is a genuine judgement call and there's no clean fix. The best defence is the disqualifier list from step one: if it's not on that list, it shouldn't be sorting anyone in or out, no matter how tempting it is in the moment.

How many should make the shortlist

The shortlist should be the size of your actual interview capacity, not "everyone who looks decent." If you have five interview slots, shortlist five to eight people, not forty.

If you're finding forty genuinely strong candidates, that's not a shortlisting problem — it's a sign the job posting was too broad, the pay is unusually attractive for the role, or the market is flooded for that skill right now. Worth revisiting the ad before you drown in the next round too.

Shortlisting well isn't about finding the best five people in the pile. It's about not spending three hours doing it, and not accidentally throwing out someone good along the way.