Screening

Matching Every Keyword Makes You Median, Not Shortlisted

On a resume, use the job posting's own words where they name something you genuinely did: a tool, a system, a certification, a task. That much still matters, because a person and a search both need the term present. Stop there. What separates two resumes that both use the right words is a specific, checkable fact attached to that word: a number, a system name, a decision you made and what happened after. A keyword list cannot fabricate that, and copying more of the posting's language will not produce it.

The takeThe advice to mirror the posting was never wrong, only incomplete, and the internet kept the first half and dropped the second. Matching vocabulary gets a resume read. It has never been the thing that got anyone hired, and now that matching costs a few seconds with any free tool, the applicants who stop at vocabulary are the median of the pile, not above it. The honest fix is not a new trick. It is finishing the sentence the old advice cut off.

Where Olive fits

Open a role and see what the work shows

No screen can tell which resume a model wrote, and Olive doesn't try: if an employer sends you an Olive assessment, it is a 40-to-60-minute assignment done openly with an AI assistant, and you receive the same six-finding report the employer does, free.

Rank your shortlist

Why Copying the Posting Stopped Setting You Apart

Keyword advice made sense when it was rare. If most applicants wrote generic resumes and one applicant echoed the posting's own terms, that resume read as a stronger match, to a filter and to a person skimming it. That gap has closed. Free tools now rewrite a resume to a posting's vocabulary in the time it takes to paste both in, so an echoed posting no longer marks the applicant who sent it as unusually careful.

A move that costs seconds separates nobody, which is what turns a differentiator into table stakes. None of this makes the posting's language worthless. A resume search and a person's first read both move faster when the word for a skill matches the word the employer used for it. The mistake is treating that match as the whole job. It gets a resume into the group that gets read. It says nothing about which resume in that group earns a call, and that second question is the one worth spending real effort on.

The posting's vocabulary and a resume that describes real work are not competing choices. A reader still benefits from the familiar term for a tool or a process; what changed is how much that term alone can carry. Treat it as the label on the box, not the contents.

What a Filter in Front of You Reads First

Software that narrows or orders the pile before a person opens a file is common enough to plan for: in the Harvard Business School Hidden Workers survey of 2,275 senior leaders across the US, UK and Germany, fielded in early 2020, 63% said they use a recruitment management system, rising to 75% among US respondents, and more than 90% of those said they use it to initially filter or rank candidates.1

Asked directly, those same employers said this costs them people who could do the job: 88% said their system vets out qualified high-skills candidates who don't match the exact criteria in the job description, a result the report files under the internal contradictions that plague the system, not a feature anyone set out to build.2

That is the honest version of the fear behind keyword advice, and it is worth reading what employers are told replaces a keyword filter: once matching stops separating anyone, the systems built to reward matching stop doing the job they were bought for.

Later, when a human recruiter searches the applicant pile, at least one major applicant tracking system runs a plain, literal keyword search over the full resume text rather than a scored match: Greenhouse's own documentation says the searched term must exactly match the term in the application.3 The machine step is not reading a skills list in isolation either. Workday states that the machine learning behind its skills suggestions considers the entire uploaded document, including the experience and description sections, not only a Skills field.4 Burying a term in a sentence about real work still counts.

Name the Term, Then Give It Something to Verify

The move that still works is finishing what keyword matching starts. Use the posting's word for a tool, a process, or a certification, because that is the true, checkable name for the thing you did. Then put a fact next to it that a keyword list cannot generate on its own: how many, how often, what the input was, what changed because of the decision you made.

"Managed stakeholder communication" matches a posting's phrase and proves nothing. "Ran the weekly status update for three product teams after the prior process missed two launch dates" uses the same vocabulary and carries a fact a reader can picture, and if it matters to them, ask about later.

This is also where tailoring a resume for every application earns its time or wastes it. Tailoring the vocabulary on a resume you send to fifty postings a week is cheap and mostly pointless past the first pass. Tailoring which two or three specific, true facts you lead with for a given posting is the version worth the extra ten minutes, because that is the part a generic resume, however well it matches, cannot do for you.

The same rule applies to a cover letter or a screening-questionnaire answer: pick the one fact from your background that most directly answers what the posting is actually worried about, and lead with it, instead of restating the requirements list back at the reader in slightly different words.

Does Perfect Matching Ever Actually Cost You?

Rarely, and the software is not the reason. A study that sent more than 83,000 fictitious applications for entry-level jobs at 108 of the biggest US employers measured how contact rates differed by the race a name signaled, and found that which application-system vendor a company used explained almost none of the variation in those gaps between firms.5 The authors concluded the differences lived inside the employers, not the screening software they bought.

That is one measured setting, not every setting, but it is worth knowing before spending another evening rewording a resume against an imagined algorithm: in the one place anyone has measured it at this scale, the differences that mattered sat inside the employers, not the software.

What perfect matching costs is time you could spend elsewhere. An hour spent inserting every synonym from a posting is an hour not spent writing the one paragraph that describes a real result in enough detail that someone believes it. Match the words that are true. Spend the rest of the hour on the part a match score cannot fake.

The exception is narrow: a requirement that a machine can verify without a person, such as a license number, a clearance, or work authorization. Those are worth stating exactly as the posting asks, because a mismatch there can end a review before anyone reads the rest of the page. Everything past that short list is judgment, and judgment is what the specific fact in the paragraph above is for.

See a sample report

Common questions

Should I still use the exact words from the job posting?

Yes, for anything that's true. If the posting says a tool, a certification, or a task you genuinely have, use its exact name rather than a synonym, because both a search and a person read that term literally. Skip words for things you have not done; the risk is a follow-up question you can't answer.

Does stuffing extra keywords into a skills list help?

Not by itself. At least one major system reads the full resume, not only a skills section, when it suggests or matches skills, and a recruiter's later keyword search runs over the whole document too. A list of terms with no supporting detail elsewhere on the page reads as thin either way.

How do I know if a company's ATS is filtering me out unfairly?

You mostly can't know from outside, and the honest answer is that employers themselves report their own filters losing qualified people. That is a reason to make requirements-matching easy to see rather than a reason to assume any one rejection was the filter's fault.

Is it worth rewriting my resume for every single application?

Rewriting the vocabulary for each posting has a small, fast payoff and a low ceiling. Rewriting which specific, checkable facts you lead with for a given role has a real payoff and is worth the extra few minutes, especially for the roles you actually want.

What actually separates two resumes that both match the posting well?

A specific fact attached to the match: a number, a named system, a decision and its outcome. Two resumes can use identical vocabulary and read completely differently once one of them backs its claims and the other doesn't.

References

  1. 1. Hidden Workers: Untapped Talent - How leaders can improve hiring practices to uncover missed talent pools, close skills gaps, and improve diversity Harvard Business School Project on Managing the Future of Work and Accenture (Joseph B. Fuller, Manjari Raman, Eva Sage-Gavin, Kristen Hines), 2021. hbs.edu Supports the share of employers running filtering/ranking software before a person opens a resume.
  2. 2. Hidden Workers: Untapped Talent - How leaders can improve hiring practices to uncover missed talent pools, close skills gaps, and improve diversity Harvard Business School Project on Managing the Future of Work and Accenture (Joseph B. Fuller, Manjari Raman, Eva Sage-Gavin, Kristen Hines), 2021. hbs.edu Supports the claim that employers themselves say exact-match filtering loses qualified candidates.
  3. 3. Talent Filtering (Greenhouse Support - Recruiting) Greenhouse Software, Inc., 2026. support.greenhouse.io Supports the description of a recruiter's exact-match keyword search over full resume text.
  4. 4. Setup Considerations: Skills in Recruiting (Workday Administrator Guide) Workday, Inc., 2024. doc.workday.com Supports the claim that resume-parsing reads the whole document, not only a skills section.
  5. 5. Systemic Discrimination Among Large U.S. Employers (NBER Working Paper No. 29053, revised May 2022) National Bureau of Economic Research (Patrick M. Kline, Evan K. Rose, Christopher R. Walters), 2022. nber.org Supports the claim that which ATS vendor a company uses explains very little of who gets contacted.

5 sources, numbered by first appearance. How Olive sources claims

General guidance for hiring teams. What works at one company and one volume may not transfer to yours.

Olive assesses how a person works with AI. It does not detect AI-written documents, and it never produces a score, a ranking, or a match percentage for a person. Candidates read the same report the employer reads.

Back to answers

Open your first role Ten attempts a month against a live item bank, with a human-written report on every one.