How to Rank Resumes Against a Job Description, Step by Step

To rank resumes against a job description, turn the job into a short list of must-haves and nice-to-haves, check each resume against every item, give each item a score, add the scores up and sort the list. Then read the top and a sample of the bottom yourself. Software can do the matching, but a person decides.

Why ranking beats reading in order

Most people read resumes in the order they arrive. The first ten get fresh attention, the middle thirty get tired attention and the last twenty get hurried attention. A ranked list changes that: you spend your best attention on the people most likely to fit, and you can show why they are first. It also gives you something concrete to share with a hiring manager, who can see the order, the reasons and the people you chose to check by hand, instead of being asked to trust a gut feeling or an unexplained pile.

Ranking also forces you to decide what the job really needs before you see the candidates. That single step prevents the common problem of changing your mind about requirements halfway through the pile, which treats early and late candidates differently.

This guide gives you a manual method that works with a spreadsheet and a pen, then shows how the same method is done by software that scores resumes, so you can choose either. If you want the tool side first, see /ai-resume-screening and /recruitment-software.

Step 1: turn the job description into criteria

Open the job description and sort every requirement into one of three groups: must-have, nice-to-have, and not really needed. A must-have is something the person cannot do the job without, or cannot learn in the first weeks. A nice-to-have helps but can be learned or replaced by another strength.

Keep must-haves to four to six. Anything more usually means the list is a wish list. Write each one as something you can find in a resume, not a feeling. "Strong communicator" is hard to check. "Has handled customer emails or calls as a main duty" can be checked. If your job description is long or vague, tighten it first, and see /job-description-template for a clean structure.

Then write the criteria down with the date, before reading any resumes. For more on writing them, see our guide on writing must-have criteria that a person or software can screen against.

Step 2: build a simple scoring sheet

Use one row per candidate and one column per criterion. Score each criterion with a small scale so you do not agonise: 0 for not found, 1 for partly or indirectly, 2 for clearly found. Give must-haves a higher weight than nice-to-haves.

Here is a word-for-word set of column headings you can paste into a spreadsheet: Candidate, Must-have 1, Must-have 2, Must-have 3, Must-have 4, Must-have 5, Nice-to-have 1, Nice-to-have 2, Must-have total, Nice-to-have total, Overall, Evidence notes, Questions to ask.

The "Evidence notes" column matters. Write the words from the resume that justify a score, or at least where they are. If you cannot point to the line, you probably guessed.

Step 3: choose a weighting

A simple, defensible choice is to make must-haves count for most of the score and nice-to-haves for a small part. Rezumz uses this idea: 80% of the score comes from the share of must-haves found and 20% from the share of nice-to-haves found. You can use the same split by hand.

To calculate it manually: divide the number of must-haves found by the total must-haves, multiply by 80. Divide the nice-to-haves found by the total nice-to-haves, multiply by 20. Add the two. A candidate who has all must-haves and none of the nice-to-haves gets 80. One who has half of the must-haves and all the nice-to-haves gets 40 plus 20, which is 60.

The weighting is a choice, not a law. If your job has one non-negotiable requirement, such as a licence, treat it as a gate: no licence, no further scoring. Write the gate down so you apply it to everyone.

Step 4: score every resume the same way

Work through the pile one criterion at a time rather than one resume at a time if you can. Check must-have 1 on every resume, then must-have 2. This keeps your standard steady and speeds you up, because your mind stays on one question.

Watch for three traps. First, wording: "managed a team" may be what "people management" means, so allow for different words. Second, absence: a resume that does not mention a skill has not proved the skill is missing, so mark it as not found, and put a question in the last column rather than writing the person off. Third, halo: a famous employer or school can lift every score. Cover the name and employer if you can.

If a resume cannot be read, do not give it zero silently. Mark it unreadable and deal with it separately.

Step 5: sort, then read with purpose

Sort by overall score. Do not treat the score as a decision. It is a way to decide where to look first.

Read the top group fully, say the top 15 to 20 percent or as many as you can interview. Then read a sample of the middle and a sample of the bottom, perhaps one in four. You are checking for people your criteria undervalued, for example someone whose experience uses different words. If you find two or three in the sample, adjust the criteria wording and rescore, and note why.

Finally pick your shortlist. For each person, write the reason in one line, such as "Meets all five must-haves, led a team of six, no experience with our CRM". That line is useful when a hiring manager asks why a candidate made the list.

A decision table: manual, spreadsheet or software

The right method depends on volume and how much you need to explain.

These ranges are rules of thumb, not measured thresholds. Your time and your tolerance for repetitive work matter more.

Worked example with example numbers

These numbers are examples only. A job needs five must-haves: reporting in Excel, vendor emails, invoice checks, a finance qualification and two years in a similar role. Nice-to-haves are experience with a named accounting package and a second language. Three candidates:

B edges A on the score, but the one must-have B lacks is the finance qualification, which the team decided is a gate, so B is moved to a "check" list while A goes first. This shows why a number alone is not enough. The recruiter reads both resumes, finds that B holds a foreign qualification described in different words, asks B a question, and both go to interview. C is read next because the sample check finds strong invoice experience under a different title, and C is rescored to 4 must-haves, which makes 64 plus 10 equals 74.

How Rezumz scoring does the same thing

The scoring in Rezumz follows the manual method. You paste the job description, Rezumz lists the must-have and nice-to-have skills it found, and you check and edit that list, because the score depends on it. Each resume is then compared with the list. The score is calculated from the skills found in the resume text: 80% from the share of must-haves and 20% from the share of nice-to-haves. The AI also reads for extra signals, such as certifications and leadership, and shows them alongside the score.

For each candidate you see the matched and missing requirements with the resume lines quoted, so the evidence notes column writes itself. You can add a note on any line and tag it as a strength, a concern or something to ask next. Move people to Shortlisted and compare two to four side by side. Applications through the apply page are scored in the same way without AI. Scoring itself does not need AI, and the score never rejects, emails or moves anyone on its own.

Like the manual method, a resume that does not mention a skill scores as lacking it, so read the resume before rejecting anyone. If scores look wrong, the usual cause is the skills list: correct the must-haves and add the resumes again.

Common mistakes

Mistake one: writing criteria after seeing the resumes. Mistake two: more than six must-haves, so almost everyone fails something. Mistake three: vague criteria such as "team player". Mistake four: trusting the top score and never reading the sample below it. Mistake five: treating a missing skill as proof the person lacks it. Mistake six: scoring tired, in a hurry, with changing standards. Mistake seven: rejecting from the score alone with no reason recorded. Mistake eight: forgetting to record why the shortlist was chosen.

Ties, gates and borderline resumes

Ranking always produces awkward cases, so decide how to handle them before they appear.

Ties: when two candidates have the same score, do not pick by gut feeling. Use a tie-break you wrote down in advance, such as the number of must-haves with clear evidence, then the most recent relevant experience, then the nice-to-haves. Applying the same tie-break to everyone keeps the process fair and easy to explain.

Gates: if a requirement is a legal or safety need, such as a licence, treat it as a gate and check it first. Someone without it does not progress to scoring, but make sure the gate is genuinely required and applied to every candidate, including those who arrive late.

Borderline resumes: a resume that scores just under your cut line is where mistakes hide. Read these in full. Ask whether the missing items are truly missing or only worded differently, and whether the person has related strengths that would make up the gap. If you cannot decide, put the person on a short "check" list and send one or two clear questions. A quick reply often settles the matter.

Unreadable files and gaps in the data: put these in a separate pile and resolve them, so nobody is ranked last simply because a file would not open. Record each decision in the evidence notes so you can answer a hiring manager's question later without trying to remember.

Fairness: rules on automated decisions and on what you may filter on differ by country, and some places have specific laws, so check local law. Keep a person making every decision, avoid scoring on school names or employer fame, and look at the bottom of the list on each batch to see whether capable people are being undervalued. If you find a pattern, change the criteria wording and rescore everyone, not just the people you noticed.

Where Rezumz fits, and who it is not for

Rezumz is an AI hiring workspace for small and mid-size hiring teams. Beyond scoring, it covers the apply page with up to five screening questions, shortlisting and a review page for hiring managers, interview scorecards and feedback, offers and the hire package. People make every decision.

It does not suit large enterprises needing deep HRIS or payroll connections, and it does not offer one-click multiposting to job boards. If you hire a few people a year and read each resume yourself, the manual sheet above, or the options at /free-applicant-tracking-system, may be all you need. The Team plan is meant for four or more recruiters.

Prices: a free plan with 2 free candidate analyses; $29 a month, $199 a year, or $499 lifetime (limited); Team is $79 a month or $699 a year for up to 10 teammates. See /pricing, try the live demo at /demo and compare options at /compare. For the wider system, see /applicant-tracking-system.