How ATS Really Works (And Why You’re Invisible, Not Rejected)

You’re probably invisible — not rejected

The popular “75% auto-rejection” stat is misleading. Many recruiters report their ATS does not auto-reject on content alone — the scarier pattern is that strong candidates never surface in search.

Recruiters query the ATS like a database: keywords, titles, experience bands. If your résumé does not match what they type, you simply do not appear. You are not getting a “no” — you are invisible.

The single biggest lever: exact job title in the header

In systematic parsing tests across platforms like Workday, Greenhouse, Lever, iCIMS, and Taleo, the strongest signal was blunt: use the exact job title from the posting in your header or summary — not a synonym.

If the posting says “Senior Product Manager,” write “Senior Product Manager,” not “Product Lead” or “Head of Product Strategy.” ATS keyword matching is still largely literal, and most recruiters filter by exact phrases.

This takes seconds per application and is one of the highest-ROI edits you can make.

The “pretty résumé” tax

Design-forward layouts often score worse — not because candidates are less qualified, but because parsers cannot read the file cleanly.

Two-column layouts scramble reading order (column A job titles merge with column B skills). Icons and emojis become blank or garbage characters. Creative section names (“My Journey,” “Toolkit”) land in miscellaneous fields recruiters never search. Contact details trapped in PDF headers/footers are frequently ignored entirely.

Keyword band: about 25–35 literal terms

Résumés that matched roughly 25–35 relevant, role-specific terms from the posting tended to align best with high ATS match scores in our tests. Below that band, you miss recruiter searches; far above it, stuffing detectors and AI-assisted screening may penalize you.

Use the exact words from the posting where truthful — “Adobe Creative Cloud” and “Adobe Creative Suite” are different strings to a parser. Hidden white text and synonym swaps are risky; natural use inside accomplishment bullets works.

Dates and file format

Mixed date formats (“Jan 2019,” “2019-01,” “January ’19”) caused systems to miscalculate tenure. Pick one format everywhere — “Month Year” (e.g. Jan 2020 – Mar 2023) parsed most reliably.

Text-based PDFs from a word processor are usually fine, but .docx remained the most consistent upload in cross-platform tests. Keep a master Word file; use PDF only when the employer requires it.

The bar is lower than you think

Interview rates are tough market-wide, but a large share of applicants are filtered for fixable technical reasons: formatting, missing keywords, invisible contact info, non-standard headers.

You do not have to be the best candidate on paper — you have to be visible to the systems and searches recruiters actually use.

TL;DR — quick-fix checklist

• Match the exact job title from the posting in your header or summary (not a synonym).
• Use a single-column layout — no tables, text boxes, or multi-column designer templates.
• Use standard section headers: “Work Experience,” “Education,” “Skills.”
• Keep name, email, and phone in the document body — not only in PDF headers/footers.
• Aim for about 25–35 relevant terms from the posting, woven naturally into bullets (not stuffed).
• Use one date format everywhere (e.g. Jan 2020 – Mar 2023).
• Prefer .docx when the employer allows Word uploads; use text-based PDF when they require PDF.
• Skip icons, emojis, and decorative graphics that replace plain text.
• Do not hide keywords or repeat terms unnaturally — AI-assisted screening flags stuffing.

Run an ATS check in Resunova after tailoring — the ATS best practices panel scores many of these items automatically from your PDF text.