The comparison layer
Talent_Matcher replaces keyword overlap with layered judgement — a sequence of narrow reads that each answer one question and hand the answer on as evidence. It produces the shortlist a senior hiring manager would produce after actually reading the posting and the resume, with the citation behind every verdict.
Where matching fails
It has been the industry default for two decades, and it is the source of nearly every complaint recruiters, hiring managers and candidates have about automated shortlisting. Underneath all three is one structural problem: a single arithmetic pass discards everything a human reviewer actually weighs.
Candidates and agencies paste the posting's language straight into a summary paragraph. A matcher reading for overlap cannot tell that apart from someone who has actually done the work — so the better copy-editor wins.
What that looks like
A candidate whose summary echoes the job description ranks above one whose project bullets prove they can do the job.
Adjacent specialists share terminology with the target role without sharing its shape. Overlap treats them as equivalent because, on vocabulary alone, they are.
What that looks like
A chief architect is rated below a data-migration specialist, because the specialist happens to carry “enterprise architecture” in their title.
Ten years owning a small workstream and ten years inside a large programme list the same technologies. Nothing in a keyword pass distinguishes them.
What that looks like
A nurse practitioner with fifteen years in intensive care is filtered out for writing “ICU” where the posting said “critical care unit”.
How it reads
Asked to judge everything at once, any reader — human or otherwise — does it worse than the same reader asked one bounded question at a time. So the reading happens in stages, each with a single question to answer and no licence to wander into the next.
What does this role actually require?
Before any candidate is looked at, the posting stops being prose and becomes something that can be tested against. Ambiguity gets resolved here rather than inherited by everything downstream, and nothing in the posting is quietly dropped on the way.
Have we understood it the way you meant it?
What we drew from the posting goes back to the recruiter or hiring manager before a single candidate is evaluated. Anything we read wrongly gets corrected, anything missing gets added, anything that does not belong comes out. Then it is locked, and every candidate is measured against that same definition.
Is this the right kind of person at all?
The shape of a career is read against the shape of the role — what someone has actually been, at what altitude, on what sort of problem, rather than what their title says. A candidate in the wrong lane cannot be rescued by vocabulary overlap, and one clearly in the right lane is not punished for a missing peripheral term.
For each requirement, what is the evidence?
Each requirement is settled on its own — found by name, demonstrated by the work described, or not found. Anything other than “not found” must carry the exact resume text that supports it. Because every requirement is judged on its own, a peripheral item never quietly steals attention from a central one.
Running through all four
Judgement is reserved for what is genuinely a matter of judgement — does this piece of work demonstrate this capability? Anything with a defined answer is computed rather than re-decided, so it comes out the same way every time. Whether twelve years satisfies a requirement for ten is not an opinion, and it is not treated as one.
In practice
Not searches that returned too little. Searches that returned a confident, plausible, wrong answer — the failure that costs the most, because nobody goes back to check it.
SAP Project Manager
SAP PM and Scrum Master resumes came back more than 95% similar on keywords. On vocabulary alone the two roles are almost indistinguishable.
What happened
The Scrum Master profiles were excluded and the genuine SAP PM candidates surfaced — avoiding a false positive that typically costs a recruiter two to three days of wasted screening.
Senior Java Backend
A product company's pipeline flooded with profiles tagged “Full-Stack Java”, which matched the posting on every term that mattered to a keyword pass.
What happened
Full-stack generalists were separated from engineers with genuinely backend-heavy delivery history. The hiring manager's shortlist-to-interview ratio doubled.
Site Reliability Engineering
The mandate was written as DevOps but was actually SRE. Keyword search returned an identical shortlist for both, because on paper they are the same role.
What happened
Reading the role context — SLO ownership, on-call, error budgets — put true SRE candidates first and filtered out the generalist DevOps profiles that would have been rejected at interview anyway.
What you receive
To the hiring manager who wants to know why. To the candidate who asks what was missing. To an auditor, a year later. Every element of it has visible evidence underneath.
The numbers
Prioritisation time scales sub-linearly with the size of the batch, which is what makes reading every resume properly affordable at volume rather than only in principle.
20+ resumes
Under 2 minutes
60–90 minutes by hand, for one traditional recruiter
100+ resumes
Under 5 minutes
500+ resumes
Under 20 minutes
And what the shortlist is worth
CognityHire delivery metrics from recent enterprise engagements, against typical traditional agency ranges.
Design commitments
Straight answers
Yes, and that step is deliberate. What was drawn from your posting is shown to you first, and you correct anything that is wrong before a single candidate is looked at. Once you lock it, every candidate is measured against that same definition — so two identical candidates cannot get different answers because the criteria drifted between runs.
Requirement by requirement. Each one shows whether it was found in the candidate's own words, demonstrated by the work they describe, or not found at all — and anything other than “not found” carries the exact resume text behind it. The shortlist is meant to be defensible to a hiring manager, to the candidate, and to an auditor.
Project evidence outranks prose. Bullets under a named role at a named employer carry more weight than a summary paragraph, and where a summary claims more than the projects underneath it support, that gap is reported rather than rewarded.
Yes. The reasoning is domain-invariant — all the vocabulary comes from your posting and the candidate's resume, and no taxonomy is encoded for any particular field. The failure it was built to fix shows up just as often in clinical, legal and finance hiring as in engineering.
No. Protected characteristics are never extracted, referenced or acted on — not down-weighted, not read. And nothing is retained after a run: there is no growing store of candidate data behind this.
Most searches never find out. The candidates filtered out at the keyword stage are the ones nobody reviews, because nobody knows they were there.