Most applicant tracking systems call themselves intelligent. Almost none of them are. What they do is measure the overlap between the words in a job description and the words in a resume. That measurement is called keyword matching, and it has long been sold as hiring intelligence. It is not the same thing.

The distinction matters because the cost of confusing the two shows up on every hiring team. You pay for a system that promises to find the best candidates. You receive a system that finds the candidates who describe themselves in the vocabulary your job description uses. Those are not the same population.

What Keyword Matching Measures

A keyword-based screening engine does three things. It parses the resume into text. It compares that text to a list of target terms drawn from the job description. It assigns a score based on how many of those terms are present, how often they appear, and in some cases where on the resume they appear.

That is the entire algorithm. Everything sold as "AI-powered ATS" on top of that core usually means one of two additions: a synonym expansion table, or a ranking heuristic that weights seniority terms heavier than skill terms. Both are improvements on raw string matching. Neither is intelligence.

The core failure: Keyword matching measures vocabulary overlap between a resume and a job description. Hiring requires measuring capability overlap between a candidate and a role. The two are related but not the same, and the gap between them is where qualified candidates disappear.

Three Places Keyword Matching Breaks

If keyword matching worked well, the hidden-workers problem would likely be smaller. Harvard Business School research estimated that more than 27 million people in the United States were hidden workers in 2020 (Joseph B. Fuller, Harvard Business School Working Knowledge, November 5, 2021). Rigid keyword screening is one plausible contributor, and the three failure modes below show how it can happen.

1. Transferable skills written in the wrong vocabulary

In a hypothetical example, a warehouse operations supervisor who managed a 40-person shift has direct transferable skills to a restaurant general manager role. Both require scheduling, inventory, training, conflict resolution, and performance management. But the resume will say "pallet throughput targets" and the job description will say "covers, average check, labor percentage." Little keyword overlap. The candidate may be able to do the job with little ramp-up. The system may never surface the match.

This is the same structural failure that traps military veterans. A squad leader who kept equipment mission-ready on a deployment has the exact operational discipline most civilian employers need. The military vocabulary often does not appear in civilian job descriptions. Fuller's article names veterans among the people behind the hidden-worker statistics, together with caregivers, older workers, and previously incarcerated people (Harvard Business School Working Knowledge, November 5, 2021). More on that in Why ATS Systems Fail Veterans.

2. Non-linear career paths

In a hypothetical example, a software engineer who took two years off for caregiving and now has certifications in a different stack than her last employer used has strong, current, verifiable skills. A keyword system may see a gap, an old tech stack, and a set of new certifications it has no weight for. The system may downgrade the resume. A human reviewer might not. The Hidden Workers report found that almost half of the companies surveyed weeded out resumes that show a work gap.

Career changers fall into the same trap. A project manager moving from construction into software delivery has budgeting, scheduling, stakeholder management, and cross-functional leadership. These skills appear in many project management job descriptions. But the resume uses construction vocabulary. The skills are present. The words are not.

3. Job descriptions that are out of date or inflated

This is a failure mode that gets less attention. Recruiters sometimes copy job descriptions from previous hires, inflate the requirements to seem serious, or paste in language from a competitor. The keyword list the ATS uses is generated from that description. So the system is filtering candidates against a vocabulary that was never accurate in the first place.

88%
of employers agree that qualified high-skills candidates are vetted out of the process because they do not match the exact criteria established by the job description (Hidden Workers report, Harvard Business School and Accenture, as reported by The Register, September 8, 2021)

What Hiring Intelligence Requires

A scoring engine that deserves to be called hiring intelligence has to do four things that keyword matching cannot.

1. Normalize across vocabularies

"Team lead," "squad leader," "shift supervisor," "crew chief," and "unit manager" describe the same job function in different industries. A real intelligence layer recognizes them as equivalent. It does not require the resume and the job description to use the same words to recognize the same skill.

This is not a synonym table. Synonym tables are brittle and have to be maintained per industry. Real normalization is semantic: it understands what the work is, not just what it is called.

2. Evaluate transferable skills against the actual role

Given a role description, a real scoring engine should identify the underlying competencies the role requires and evaluate whether the candidate has demonstrated those competencies anywhere, regardless of job title, industry, or era. A nurse who ran a 24-bed unit during a staffing crisis has demonstrated crisis leadership and resource allocation under pressure. Those are exactly the competencies most operations director roles require. A keyword system cannot see the match. A real intelligence layer can.

3. Explain its scores

This is the dividing line between intelligence and a black box. If the system says a candidate scored 72 out of 100, a human reviewer has to be able to ask why, and the system has to answer in complete sentences. "Matched 8 of 12 keywords" is not an explanation. It is a summary of the algorithm, not a summary of the candidate.

Every score from TrueScan HR comes with a readable explanation: which competencies the candidate demonstrated, where the evidence came from, and what the gaps are. That transparency is not a feature. It is a requirement. If a system cannot explain itself, it cannot be audited, and if it cannot be audited, it may be hard to defend if a rejection is ever challenged under California ADS regulations or an EEOC inquiry. California's automated-decision regulations, effective October 1, 2025, extend record retention to four years and treat evidence of anti-bias testing as relevant to discrimination claims and defenses (Paul Hastings, August 12, 2025).

4. Distinguish signal from vocabulary

A resume that uses the exact phrases in the job description is either a great match or a great fraud. A real intelligence layer treats exact phrasing as one input, not the final answer. It weighs context: does the candidate describe how they applied the skill, what the outcome was, whether the claimed experience is consistent across the rest of the resume. Keyword systems cannot make any of those judgments. They only count.

How to Tell Which One You Have

There is a simple test. Take the top five rejected resumes from your last open role and read them. If you can look at any of them and say "this person could do this job," your screening may be relying on keyword matching. Hiring intelligence would likely have flagged that resume for review. Keyword matching may have sent it to the reject pile because the words did not line up.

Many hiring teams that run this test may find at least one candidate they would have wanted to interview. When that happens, it points to a common failure mode of vocabulary-based screening.

Joseph B. Fuller, Harvard Business School: "In filtering out all but those candidates who match exacting and expanding requirements, companies reject many experienced, reliable, and creative individuals." Rigid filters can end up screening out good candidates who described themselves in the wrong language.

The Practical Path Forward

The answer is not to throw out automation. The answer is to stop confusing automation with intelligence. A hiring workflow that pairs keyword-based parsing with a real scoring engine gives you the best of both. The parser normalizes the data. The scoring engine evaluates whether the person in the data can do the job, measured against the competencies the role requires, explained in language a hiring manager can defend.

TrueScan HR was built on that split. The parsing handles structure. The scoring does the work of evaluation. Every score is transparent, every rejection is explainable, and every candidate is measured against the capability the role needs, not the vocabulary the posting happened to use.

If your current system cannot do those four things, it is not hiring intelligence. It is keyword matching with a newer interface. The qualified candidates are still being filtered out. You just cannot see them.

The Filters Behind Keyword Matching

Keyword matching is one of several filters worth auditing:

Sources:

Thabiti Adams is a CISSP-certified cybersecurity professional and founder of Adams Cloud & Cybersecurity, the firm that builds and operates TrueScan HR.