“75% of resumes are rejected by the ATS before a human sees them” is one of the most repeated statistics on the internet, and it is essentially folklore. Applicant tracking systems are not robot gatekeepers running a pass/fail exam on your formatting. They are databases with a search box. Understanding that one fact changes which formatting advice you should follow, and which you can safely ignore.
What an ATS actually does with your resume
Three things, in order:
- Parsing.The system extracts structured fields from your file: name, contact info, job titles, employers, dates, skills, education. This is the step where formatting matters: a layout the parser can't follow produces garbled or empty fields.
- Search & filtering.Recruiters query the database: “product manager” AND “SQL”, applied in the last 30 days. This is the step where keywordsmatter. You aren't rejected for lacking a keyword; you're simply not in the result set.
- Ranking & knockouts.Some systems score or order candidates against the posting; many let employers add explicit knockout questions (“Are you authorized to work in…”). Knockout answers, not parsing mishaps, are the most common cause of true auto-rejection.
Why applications die before an interview
Typical causes of a no
Hover or tap an item for detail.
The formatting rules that actually matter
| Rule | Why |
|---|---|
| One column, top to bottom | Parsers read in reading order. Two-column layouts can interleave your sidebar skills into your job history, scrambling both. |
| Standard section headings | Parsers look for “Experience,” “Education,” “Skills.” Clever headings like “Where I've made an impact” can orphan an entire section. |
| Title / Company / Dates on predictable lines | The job-history extractor pattern-matches this triplet. Keep dates in one consistent format (e.g., 'Jan 2023 – Present'). |
| Real text, not graphics | Skill meters, icons, charts, and text inside images are invisible to parsers. If information matters, it must exist as selectable text. |
| Contact info in the body, not the header/footer | Several parsers skip or mangle header/footer regions, making them the worst possible place to lose your email address. |
| PDF or .docx, normally formatted | Both parse fine in modern systems. The format matters less than what's inside it. |
And the “rules” you can ignore
- “Never use PDF.”Outdated. Modern parsers handle text-based PDFs well. (A scanned image PDF is a different story: that's a photo, not text.)
- “ATS rejects resumes over one page.”The database doesn't care about page count. Humans mildly prefer concision; that's a different argument.
- “Use white-text keywords to beat the scanner.” Systems flag this, recruiters see the raw parse, and it reads as fraud. The riskiest possible move for zero benefit.
- “Bullets/symbols break the ATS.”Standard round bullets are fine everywhere. Exotic dingbat symbols can turn into junk characters, but that's a typography choice, not an ATS one.
How to test your own resume in 60 seconds
You don't need a paid scanner. Two checks catch nearly everything:
- The copy-paste test. Select all the text in your PDF and paste it into a plain text editor. Is it in the right order? Are titles, employers, and dates intact and adjacent? If the paste looks scrambled, the parse will be too.
- The search test.Pick the three nouns the job posting repeats most. Ctrl+F your resume for each. Zero hits on a deal-breaker term means the recruiter's search won't surface you. Fix the vocabulary (honestly) before sending.