The ATS Keyword Myth: What Recruiters Actually Search For

If you've spent any time on r/jobs you've seen the advice: "stuff the job description keywords into your CV". It's half right, in the wrong way.

The reason it's half right: recruiters do search inside their ATS, and your CV does need to contain the words they're searching for. The reason it's wrong: most candidates stuff in the wrong words, in the wrong places, in the wrong format.

Here's how recruiters actually use the search bar inside Workday, Greenhouse, Lever and the others — and what to do about it.

How recruiters actually search

I've watched dozens of recruiters work. The pattern is almost always the same:

1. Open the requisition.
2. Type 2–4 words in the search bar.
3. Skim the first 20 names.
4. Refine the search.

Those 2–4 words are usually:

• A job title ("product manager")
• A specific tool ("Salesforce", "Kubernetes", "Figma")
• A domain ("fintech", "B2B SaaS")
• Sometimes a metric or seniority ("senior", "lead", "VP")

That's it. They're not searching for "passionate self-starter with strong communication skills".

The seven phrases that actually matter

Based on the patterns we see across thousands of CV–JD pairs:

1. Exact job title from the ad. If the role is "Senior Product Manager", that exact phrase should appear at least once in your CV — ideally as a current or recent role title.

2. Tools by name. "Salesforce", not "CRM software". "PostgreSQL", not "relational databases".

3. Methodology names. "Agile", "Scrum", "OKRs", "MEDDIC" — recruiters search for these.

4. Industry vertical. "B2B SaaS", "fintech", "marketplace" — narrows the candidate pool fast.

5. Seniority signals. "Senior", "Lead", "Principal", "Director" — but only if you actually held the level.

6. Team-size or scope numbers. "Managed a team of 8", "Owned $4M budget" — searched as "team of", "managed team", "budget of".

7. Certifications spelled exactly. "PMP", "AWS Solutions Architect", "CFA Level II" — exact strings, no abbreviations recruiters won't recognize.

Where to put them

This is where most candidates blow it.

Putting keywords in a "Skills" section at the bottom is the weakest possible placement. ATS search ranking — and recruiter eyes — both weight in-context mentions far higher than list items.

Best placements, in order:

1. **Job title line** — "Senior Product Manager · Stripe · 2022–present"
2. **Inside a bullet** — "Owned the pricing experimentation roadmap (A/B testing in Optimizely, attribution in Looker)"
3. **In your summary** — "Senior product manager focused on B2B SaaS pricing and packaging"
4. **Skills section** — last resort, only for things that don't fit elsewhere

Synonyms recruiters actually expand

A few common ones to be aware of, because the recruiter's search will catch either:

• "JS" / "JavaScript"
• "ML" / "machine learning"
• "PM" / "product manager" / "project manager" (context disambiguates)
• "BD" / "business development"
• "CS" / "customer success" / "computer science"

Spell out the long form at least once — that's how you cover both searches.

What not to do

• **Don't repeat the same keyword 8 times.** ATS systems and recruiters both notice. Two or three contextual mentions is plenty.
• **Don't paste keywords in white text.** Every modern ATS catches this; so do recruiters once they open the file.
• **Don't keyword-stuff a generic skills list.** "Excel, Word, PowerPoint, Python, SQL, Tableau, Looker, Mixpanel, Amplitude, GA, GA4, Adobe Analytics, HubSpot, Marketo" tells the recruiter nothing.

The shortcut

The fastest way to get this right: paste the job description into [ResumAI](/), run the optimizer, and let it pull the actual phrases the recruiter will search for. The output shows you exactly which terms are missing and where to add them — so you stop guessing and start matching.