What an ATS Actually Rejects (And What It Doesn't)

Applicant tracking systems get blamed for more than they do. They are, mostly, databases with a parser on the front. The parser reads your resume, tries to work out which text is your job title and which is your employer, and files the result. When people say a resume was "rejected by the ATS", what usually happened is that it parsed badly and therefore did not match anything a recruiter searched for.

What genuinely causes problems

• Text inside images. A parser cannot read a logo, a graphic header, or a resume exported as a picture. Anything in an image is invisible.
• Multi-column layouts. Some parsers read across columns rather than down them, which interleaves two unrelated sections into nonsense.
• Text in headers and footers. Several parsers skip these regions entirely, which is a problem if your phone number lives there.
• Tables used for layout. Modern parsers handle simple tables; nested ones still produce scrambled output.
• Unusual section names. "Where I've Been" instead of "Experience" gives the parser nothing to anchor on.
• Dates in inconsistent formats. Mixing 2019-2021, Mar 2019 – May 2021 and '19–'21 makes tenure hard to compute.

What is folklore

Several widely repeated rules are either outdated or were never true. A PDF is fine — every mainstream system has parsed PDFs for years, and the advice to always send .docx is a decade old. Standard fonts are not required; readable ones are. And there is no secret score threshold that auto-rejects you: most systems rank and surface candidates for a human, they do not silently bin them.

The white-text keyword trick — pasting the job description into the resume in white on white — is worth naming because it still circulates. Parsers read it, humans see it the moment they open the file, and it reads as dishonest. It gets people removed from consideration.

The test that settles it

Open your resume, select all, copy, and paste into a plain text editor. What you see is approximately what the parser sees. If the order is wrong, if sections are interleaved, if your contact details are missing, or if entire chunks are absent because they were images — that is your problem, and it is now visible.

If the plain text version reads in the right order and contains everything, the parsing side is fine and any remaining problem is the content, not the format.

What actually moves the needle

Once the resume parses, the thing that decides whether it surfaces is whether the words in it match the words in the job description. Not stuffed — matched. If the posting says "accounts receivable" and your resume says "AR", write it out at least once. If it names a specific tool, and you have used it, name that tool rather than the category.