Blog

How to review hundreds of resumes with requirements first and scoring second

Published on

When hundreds of resumes arrive there are two ways to go wrong: reading them all by hand until you run out of energy, or letting a tool discard by keywords. The order that works better is different: first apply the requirements that can be verified, and only then rank by fit.

RequirementTypeWhat to do
Country where they can workVerifiableApply first; if the resume does not say, ask
Work mode (onsite, hybrid, remote)VerifiableApply first using the city of the offer
Language the role demandsVerifiable with nuanceAsk the level; separate written from spoken
Years of experienceInterpretiveUse for ranking, not for rejection
Tools and technologiesInterpretiveRead the context, not just the word
Soft skillsInterpretiveSee them in the interview

Why reading faster no longer solves volume

According to Korn Ferry, applications on LinkedIn rose more than 45% in a year and the platform logs an average of 11,000 applications per minute. With more applications per vacancy, the bottleneck stopped being finding candidates and became deciding who deserves a conversation.

Reading each resume in two minutes does not scale either: one hundred resumes is over three hours straight, and attention in hour three is not what it was in hour one. The last ones in the pile get less than the first, and nobody decided that.

There is a less visible consequence: when volume forces quick decisions, the temptation is to use shortcuts such as the name of the last employer or the university. They are easy signals to read that, on their own, do not say whether the person can do the job. With requirements written in advance, the same rule applies to the first resume and to number two hundred.

The risk of discarding wrongly

A discarded candidate is invisible: they appear on no list and nobody knows they existed. That is why a wrong rejection costs more than an extra review. In a Harvard Business School and Accenture survey cited by HR Dive, 88% of employers said qualified, high-skilled candidates were rejected outright for not matching the vacancy criteria exactly.

It is an opinion survey of employers, not a measure of how many are lost. Even so, it points at what usually fails: rigidly written criteria, such as exact years of experience or a specific degree, that shut out people who could do the job.

The five-step method

This order avoids both failures, fatigue and rigidity. Each step can be done in a spreadsheet; an ATS just does it faster and keeps the record.

  • Separate must-haves from nice-to-haves. A must-have is what makes hiring impossible if missing: being allowed to work in the country, the work mode of the offer, the language the role demands. Everything else is a nice-to-have. If you have more than five must-haves, some probably are not.
  • Apply only the requirements you can verify. Country, work mode and language are verified with a resume field or a form question. “Good communicator” cannot be verified.
  • Doubtful ones move on. If the resume does not say whether the person can work in the country, do not discard them: ask. Discarding only what can be proven is the rule that saves the most good candidates.
  • Rank by fit those who passed. Only now do you compare experience, similar tasks and nice-to-haves, to decide whom to call first.
  • Review the rejections once a week. Look at ten at random. If you find one that should not be there, the requirement is badly written.

What can be verified and what has to be read

The difference between a verifiable requirement and an interpretive one decides what gets automated and what a person reads. The table above sorts common examples.

What a tool should show you

If you use software for this, demand three things: that it says which requirement left someone out, that it distinguishes between “does not meet” and “could not be verified”, and that it lets you recover any rejected candidate. A score with no reason is an opinion you cannot review.

In Akitalent each requirement states whether it could be verified, the fit ranking shows its reason and every rejection is recorded. The free plan includes 1 open role and 10 trial analyses, without automations or profile recommendations from our network. Opening costs USD 39 per month (USD 390 per year), Team USD 179 per month and Enterprise USD 399 per month.

Frequently asked questions

What if the tool rejects someone good?
That is why only what is verifiable gets rejected and doubtful cases move on. Every rejection should also show its reason and be recoverable.
How many must-have requirements should I set?
Few, three to five. Each extra must-have shrinks the candidate pool and raises the chance of leaving out someone who could do the job.
Does a spreadsheet work for this?
Yes, for tens of resumes. From a few hundred on, an ATS is better: it applies the requirements in the same order and keeps a record of each decision.

Sources

Keep reading