Candidate screening
Candidate screening software that shows you the evidence.
Candidate screening is deciding who deserves a closer look, measured against what the role actually requires. Hirevo reads every resume, evaluates every candidate against the same role requirements, ranks the results, and shows recruiters why the order looks the way it does. One standard for every candidate. The decision stays yours.
Screening resumes rather than a shortlist? See AI resume screening software.
| Rank | Candidate | Fit | Evidence | Gaps | Why this rank |
|---|---|---|---|---|---|
| 01 | Candidate A | Strong | 4 supporting signals | 1 gap | Owned the core requirement in production, at the level the role needs |
| 02 | Candidate B | Strong | 3 supporting signals | 2 gaps | Full stack match; leadership evidence thinner than the role asks for |
| 03 | Candidate C | Moderate | 2 supporting signals | 2 gaps | Adjacent domain; the scale requirement is not supported by the resume |
| 04 | Candidate D | Moderate | 2 supporting signals | 3 gaps | Right level; one core requirement is implied rather than stated |
| 05 | Candidate E | Weak | 1 supporting signal | 3 gaps | A core requirement is absent and nothing adjacent covers it |
- 01Candidate AStrong4 supporting signals1 gap
Owned the core requirement in production, at the level the role needs
- 02Candidate BStrong3 supporting signals2 gaps
Full stack match; leadership evidence thinner than the role asks for
- 03Candidate CModerate2 supporting signals2 gaps
Adjacent domain; the scale requirement is not supported by the resume
- 04Candidate DModerate2 supporting signals3 gaps
Right level; one core requirement is implied rather than stated
- 05Candidate EWeak1 supporting signal3 gaps
A core requirement is absent and nothing adjacent covers it
The definition
What is candidate screening?
Candidate screening is the process of evaluating applicants against the requirements of a role to decide who should move forward for closer consideration. Its purpose is to find the candidates who deserve deeper attention, and to be able to say why. Good screening applies the same role-specific criteria to every candidate, records the evidence for and against each one, and produces a shortlist a recruiter can explain. Hirevo makes that process systematic: it reads every resume against the job description, surfaces evidence and gaps, ranks the result, and leaves the decision with the recruiter.
- Input
- A role and its candidate pool — the resumes for it, uploaded directly.
- Standard
- The job description. Every candidate is evaluated against the same requirements.
- Output
- A ranked view of role fit, with strengths, gaps and supporting evidence for each candidate.
- Decision
- The recruiter’s. Hirevo recommends; a person decides who gets a closer look.
The screening problem
Why candidate screening breaks down.
None of these is a failure of effort. They are what happens when a consistent judgement has to be made hundreds of times, by hand, under time pressure, with the evidence scattered across documents written to be scanned.
- 01
The pool outgrows the attention
A role that draws a few hundred applicants cannot be read by one person with the same care from first to last. Somewhere in the middle, evaluation turns into skimming.
- 02
Candidates are reviewed on different days
The resume read on Monday morning is judged against a different mood, memory of the role and set of comparisons than the one read on Thursday night. Same criteria on paper; different evaluation.
- 03
Keywords stand in for evidence
A filter that matches on terms rewards the applicant who used the posting’s vocabulary, not the one who did the work. The strongest person in the pool may never have used the magic word.
- 04
The evidence is buried
The line that proves a candidate can do the job is on page two, inside a project, under a title that does not match the role. Read at speed it is missed; read at all, it is recorded nowhere.
- 05
The shortlist cannot be explained
Asked why one candidate was shortlisted over another, the honest answer is often a feeling. It may be right, but it cannot be checked, defended, or handed to a colleague.
- 06
Ranking becomes an opinion
Without criteria that stay fixed across every candidate, an order is a sequence of impressions. Two recruiters produce two rankings, and nothing says which is closer to the role.
How it works
How Hirevo screens candidates.
Understand, read, match, identify, rank, review: how a pool of applicants becomes a shortlist in Hirevo, with one standard applied to everyone and the reasoning kept at every step. The sections below open each step.
The same six steps, done by hand, are in our practical guide to screening resumes against a job description.
- 01
Understand the role
You create a role and give Hirevo the job description every candidate will be evaluated against, so the requirements are fixed before the first applicant is read.
- 02
Read every resume
Every candidate’s resume is read in full — experience, skills, projects, education — with no keyword pre-filter deciding who gets looked at.
- 03
Match evidence to requirements
Each candidate is evaluated against the role’s requirements: which the resume supports, which it does not, and how relevant the experience is at this level.
- 04
Identify strengths and gaps
The evaluation is written out as a recruiter would want it: strengths for this role, the gaps worth knowing before an interview, and the recommendation with its explanation.
- 05
Rank candidates
Every candidate receives a job match score and a match category against the same role, and the pool is ranked from those results.
- 06
The recruiter reviews the result
Hirevo recommends; a person decides who moves forward. The decision is recorded with who made it and on what basis, reversible for 30 days. Nothing is rejected automatically.
Step 01Understand the role
A role becomes a standard.
Screening starts from the job description, not from the resumes. Hirevo reads the posting for what the role actually requires — the stack, the level, the scale, the responsibilities — and that set of requirements is what every candidate in the pool is measured against. It is fixed before the first resume is read and does not move as the pool is worked through.
A missing core requirement is the first thing triage reports about a candidate, so the standard is visible in the result, not only in the setup.
Job description
Senior Backend Engineer
Requirements · applied to all 12
- Go in productioncore
- Distributed systemscore
- Owned a production system at scalecore
- Senior level: led design decisionscore
- Kuberneteslisted
- Mentoring engineerslisted
Step 02 – 03Read every resume, match it to the role
Every candidate, read in full, against the same requirements.
Each resume in the pool is parsed and read in full — experience, skills, projects, education — with no keyword pre-filter deciding who gets looked at. Then each candidate is evaluated against the role’s requirements: which the resume supports, which it does not, and how relevant the experience is at this level. The first applicant and the three-hundredth get the same reading.
- Candidate AStrong4/4 core
- Candidate BStrong3/4 core
- Candidate CModerate3/4 core
- Candidate DModerate3/4 core
- Candidate EWeak2/4 core
- Candidate FWeak1/4 core
- Candidate GModerate2/4 core
- Candidate HWeak1/4 core
Beyond keywords
Candidate screening is not a vocabulary test.
A keyword filter answers “does this resume contain the right words?” A recruiter needs “does this person’s experience meet what the role requires?” answered, and that takes evidence. Hirevo evaluates the relationship between the role’s requirements and the candidate’s experience, skills and projects — what the resume supports, what it leaves open, and the context around each claim. It does not claim to understand a resume perfectly. It shows its reading, so a recruiter can check it.
A keyword can signal a match. Evidence lets a recruiter investigate whether the match is meaningful.
- The role’s stack appears in the resume
- Where it appears — a job held, a project built, or a list at the bottom — and at what level of ownership.
- The years of experience add up
- What those years contained: the scale of the systems, the scope of the responsibility, whether the level the role needs was reached.
- A required skill is absent
- Whether it is a gap or a wording problem: adjacent experience that covers it, a project that used it under another name, or a genuine absence worth an interview question.
Step 04Identify strengths and gaps
Compare candidates on the same rows.
A shortlist of two to five candidates can be put side by side. The comparison ranks them and writes out the reasoning — who leads, who is the runner-up, how confident the comparison is, and what each candidate’s strengths and gaps contribute — so the question becomes “why this person over that one?” rather than “who scored highest?”
The same four rows for every candidate. A gap is listed with its context, for a person to weigh.
| 01Candidate A | 02Candidate B | 03Candidate C | |
|---|---|---|---|
| Role fit | StrongOwned the core requirement in production at the level the role needs | StrongFull stack match; leadership evidence thinner than the role asks for | ModerateAdjacent domain; the scale requirement is not supported by the resume |
| Strengths |
|
|
|
| Gaps |
|
|
|
| Evidence | 4 supporting signals · checkable in the resume | 3 supporting signals · checkable in the resume | 2 supporting signals · checkable in the resume |
01Candidate A
- Role fit
- StrongOwned the core requirement in production at the level the role needs
- Strengths
- Built and ran the kind of system the role owns
- Required stack in held roles, not only a skills list
- Gaps
- Team leadership described once, without scope
- Evidence
- 4 supporting signals · checkable in the resume
02Candidate B
- Role fit
- StrongFull stack match; leadership evidence thinner than the role asks for
- Strengths
- Every listed technology appears in a held role
- Recent, relevant project work
- Gaps
- No ownership of a production system stated
- Level implied by title, not by scope
- Evidence
- 3 supporting signals · checkable in the resume
03Candidate C
- Role fit
- ModerateAdjacent domain; the scale requirement is not supported by the resume
- Strengths
- Strong distributed-systems background
- Clear design ownership
- Gaps
- Scale of systems not stated
- Stack partly adjacent to the role’s
- Evidence
- 2 supporting signals · checkable in the resume
Step 04 · detailOpen one claim
The evidence behind the recommendation.
A ranking is more useful when a recruiter can investigate why. In Hirevo every position in the ranked view can be walked back to the strengths and gaps that produced it, and from there to the related lines of the resume, matched by wording — so a recommendation can be checked, defended, or overruled before anyone acts on it.
- Requirementfrom the job description
Owned a production system at scale — core
- Related resume linematched by wording, not cited
“Ran the ingestion service for the payments platform; on call for it for two years.” — Candidate A · experience
- Interpretationwhat the analysis made of it
Supports the requirement at the level the role needs: ownership stated, duration stated, scale implied rather than quantified.
- Gapwhat it leaves open
Scale is implied, not stated — worth an interview question rather than a deduction.
Evidence supporting a match
Every strength and risk is shown beside the roles, projects and skills in the resume that relate to it, matched by wording. A strength is a claim you can check, not an adjective.
Gaps and missing signals
Required skills the resume does not support are listed as missing, and the gaps worth an interview question are written out. Absence is reported, not smoothed over.
Doubt is shown, not rounded up
Where the reading is uncertain, the uncertainty is visible. A low-confidence read is presented as one, so a recruiter knows where to look harder.
Step 05Rank candidates
Rank candidates against the same standard.
Hirevo evaluates every candidate against the same role requirements and produces a ranked view of role fit, so a recruiter can see which candidates appear strongest for the specific role — and then investigate whether the order holds up.
- Job match score
- 0 – 100, against this role
- Match category
- Excellent · Strong · Moderate · Weak
- Recommendation
- Strong Hire · Hire · Maybe · Reject, with its explanation
On consistency, plainly: the requirements come from the job description alone, and the rule-based checks give the same result every run. The parts that come from the model’s reading — matched skills, relevant projects, the written strengths and gaps — can vary between runs, so a job match score can move. A match the resume itself supports is always counted.
One standard, applied to everyone
Every candidate in a role is evaluated against the same job description, so the ranked view reflects fit to the job rather than to whichever resumes happened to be read nearby.
A ranked view, not a verdict
The order is a set of signals arranged so the candidates who appear strongest for this role are easiest to find. Recruiter review starts there; it does not end there.
Close calls get a comparison
When two candidates sit near each other, comparison puts them side by side and writes out the reasoning: who leads, who is the runner-up, and why.
Step 06The recruiter reviews the result
From the pool to a shortlist you can explain.
Triage brings the candidates who meet the bar to the front. A recruiter takes the closer look — opening claims against the parsed resume, comparing the close calls — and decides who moves forward. Hirevo recommends; a person decides. The decision is recorded with who made it and on what basis, and it stays reversible for 30 days. Nothing is rejected automatically, and the candidates who did not advance keep their reasons.
- Pool12
- A
- B
- C
- D
- E
- F
- G
- H
- I
- J
- K
- L
Every resume read in full and ranked. Those not carried forward keep the reason.
- Closer look5
- A
- B
- C
- D
- G
Claims opened against the resume; the close calls compared side by side.
- Shortlist3
- A
- B
- D
Decided by a person, with the evidence attached and the decision logged.
Two kinds of screening
Keyword filtering and evidence-backed screening.
Both reduce a pool. Only one of them tells you what it did to each candidate, and why.
- Candidate APass · 6 of 6 terms
- Candidate CFail · “Kubernetes” not found
- Candidate FPass · 6 of 6 terms
- Candidate AStrongOwned the core requirement in production
- Candidate CModerateRequirement listed as a gap, with context, for a person to weigh
- Candidate FWeakTerms present in a skills list; no held role supports them
- What it looks at
- Keyword filteringWhether the resume contains the terms in the posting.
- Evidence-backed screeningWhether the candidate’s experience, skills and projects support each requirement of the role.
- How candidates are compared
- Keyword filteringBy how many terms matched, which favours the resume written for the filter.
- Evidence-backed screeningAgainst the same role requirements, with a job match score and category for each and a ranked view of the pool.
- What recruiters see
- Keyword filteringA pass or a fail, sometimes a count.
- Evidence-backed screeningStrengths, gaps, matched and missing requirements, the recommendation, and the related resume lines.
- How gaps are handled
- Keyword filteringA missing term is a missing candidate. Adjacent experience does not count.
- Evidence-backed screeningA missing requirement is listed as a gap, with the context around it, for a person to weigh.
- Decision transparency
- Keyword filteringThe rule is visible; why a particular person was excluded is not.
- Evidence-backed screeningEvery recommendation carries its explanation, and every decision is recorded with who made it and on what basis.
Hirevo and your ATS
Candidate screening is not the same as an ATS.
An applicant tracking system manages the recruiting workflow: applications, candidate records, stages, correspondence. Candidate screening is the evaluation that happens inside that workflow, and it is the part Hirevo does. An ATS remembers candidates. Hirevo helps you choose one.
Hirevo currently operates as a decision layer alongside your existing tools. Resumes are uploaded directly; there are no ATS integrations yet. They are on the roadmap and are not something you have today.
- What an ATS is for
- Holding the pipeline of record: who applied, where they are, what has been sent and logged. Hirevo does not try to be it.
- What Hirevo is for
- The decision layer: screening each candidate against the role, ranking the pool, and showing the reasoning so a person can decide between them and explain the choice.
Responsible use
AI assists. Recruiters decide.
Candidate screening is a decision about people, and the person making it should be able to see, question and overrule what the software suggests. That is how Hirevo is built, not a disclaimer attached to it.
- Hirevo provides analysis and recommendations. It does not make the final hiring decision, and it does not reject a candidate on its own.
- Recruiters remain responsible for reviewing candidates. Our terms require a human to review any decision that materially affects a candidate.
- A recommendation can be investigated before it is acted on: the explanation, the strengths and gaps, and the related lines from the resume.
- Every decision is recorded with who made it and on what basis, and stays reversible for 30 days.
On bias, honestly: we have not completed a formal bias audit, and we will not claim one until we have. What we do today is structural — every score can be traced to the analysis behind it, low confidence is shown rather than hidden, and nothing is auto-rejected. If you are subject to an audit requirement such as NYC Local Law 144, talk to us before you deploy rather than after.
Who it is for
Built for the people who own the shortlist.
Recruiting teams
A shared organization where every recruiter screens against the same role standard, sees the same evidence, and can hand a shortlist to a colleague with the reasoning attached.
Hiring managers
A ranked shortlist you can interrogate rather than a list to trust — who is on it, why, what the gaps are — and interview packs grounded in what each candidate actually claims.
Teams screening at volume
When a role draws hundreds of applicants, evaluating every one consistently is the whole problem. That is the case Hirevo was built for, and the one the free analyses let you test.
Teams that need to explain the shortlist
Anyone who has to say why one candidate advanced and another did not — to a hiring manager, a client, or a candidate — and wants the answer on record rather than in memory.
FAQ
Candidate screening, answered plainly.
What is candidate screening?
Candidate screening is the process of evaluating applicants against the requirements of a role to decide who should move forward for closer consideration. Done well, it applies the same role-specific criteria to every candidate, records the evidence for and against each one, and produces a shortlist a recruiter can explain. It comes before interviewing: it is how you decide who to interview.
How does AI candidate screening work?
Software reads each application and evaluates it against a role, instead of relying on keyword filters or manual skimming. In Hirevo, you create a role with its job description and upload the resumes. Each resume is read in full, matched against the role’s requirements, given a job match score and category, and ranked with the others, with its strengths, gaps and evidence attached. A recruiter reviews the result before anything happens to the candidate.
What does Hirevo look for when screening candidates?
The relationship between the candidate and the role. For each resume Hirevo identifies the required skills that are present and the ones that are missing, how relevant the experience is, which projects support the requirements, the candidate’s strengths, the gaps a recruiter should know about, and a hiring recommendation with its explanation. A structural ATS score for the resume itself is reported separately.
Can Hirevo screen candidates against a job description?
Yes. Every screening in Hirevo is run for a specific role, and the job description is what each candidate is evaluated against; there is no mode that scores a candidate in the abstract. The output is expressed in the role’s terms — which requirements the candidate meets, which they do not, and how their experience lines up — so the whole pipeline is measured against one standard.
How does Hirevo rank candidates for a role?
Every candidate in the role is analysed against the same job description and given a job match score from 0 to 100 and a match category, and the pipeline is ranked from those results. The ranking is a view of role fit, not a verdict: a recruiter can open any candidate to see the matched and missing skills, the strengths and gaps, and the related resume lines, or compare two to five candidates side by side.
Is candidate screening the same as using an ATS?
No. An applicant tracking system manages applications and the workflow around them: records, stages, correspondence. Candidate screening is the evaluation that happens inside that workflow, and it is what Hirevo does: analysing the candidates in a role, ranking them, and showing the evidence so a person can decide. Hirevo is not an ATS and does not replace one. Resumes are uploaded directly; there are no ATS integrations yet, and they are not something you have today.
Does Hirevo reject candidates on its own?
No. Hirevo ranks and recommends; it never rejects a candidate automatically. A person makes every decision about who moves forward. Our terms require a human to review any decision that materially affects a candidate, and the product records who made each call and on what basis. Decisions are logged and stay reversible for 30 days.
Does Hirevo replace recruiters?
No. It does the reading a recruiter cannot do consistently across a large pile, and attaches evidence to every claim it makes, but the judgement stays with the person: a recruiter reviews the analysis, investigates the ranking, and decides. Every new organization gets 2 full analyses free, without a card, to see how that division of labour feels on your own resumes.
Screen the next role against one standard, with the evidence attached.
Add a role, upload the candidates’ resumes, and read the ranked view Hirevo makes of them. Every new organization gets 2 full analyses free, without a card.
Want the resume-first view first? See how Hirevo screens resumes or talk to a person.