What an ATS Actually Rejects (and What It Doesn't)
What really breaks resume parsing, which ATS rules are outdated folklore, where rejections actually come from, and a two-minute test to run on your resume.
ResumeOn TeamATS and screening
Most advice about applicant tracking systems is written by people who have never seen one reject a file. The result is a folklore of rules that cost candidates real formatting quality for no benefit: plain-text resumes that read badly to humans, keyword lists pasted in white font, and a fear of PDFs that has not been justified for years.
This guide separates what genuinely breaks resume parsing from what is just repeated advice, explains what an ATS actually does with your file, and gives you a two-minute test you can run on your own resume today.
What an ATS actually does with your resume
An applicant tracking system is the software a company uses to receive and manage applications. When you apply, it does three things:
- Stores your file so recruiters can open the original.
- Parses it, which means extracting your name, contact details, job titles, employers, dates, skills, and education into structured fields.
- Makes those fields searchable, so a recruiter can filter and search the candidate pool.
The parsing step is the one that matters for formatting. If your job title ends up in the wrong field, or your phone number never makes it out of the page footer, a recruiter searching the database may never see your application, even though the file is sitting there.
The system is not looking for a reason to reject you. It is looking for structured text it can index.
What genuinely breaks parsing
A handful of things reliably confuse a parser:
- Text inside images. A parser reads text, not pixels. A name rendered as a logo is a name the system never sees, and a skills chart made of icons contributes no skills at all.
- Multi-column layouts that are actually tables. Reading order comes from the document structure, not from what your eye does. A two-column layout built from a table can interleave your job titles with your skills list, so "Senior Analyst" ends up next to "Python, SQL, Tableau" instead of next to the employer.
- Headers and footers. Some parsers skip them entirely, which makes them a poor place for your phone number and email.
- Non-standard section names. "Where I have worked" is charming, but "Experience" is what gets matched. The same goes for "My toolkit" instead of "Skills".
- Scanned documents. A PDF made by scanning a printed page is an image of text. Unless the system runs text recognition on it, it holds no text at all.
- Unusual characters in key fields. Decorative bullets and symbols are usually harmless in body text, but emoji or icon fonts inside dates or contact details can come out as gibberish.
What does not matter
Plenty of the usual warnings are simply out of date:
| Claim | Reality |
|---|---|
| PDFs get rejected | Text-based PDFs parse fine and are the safest format for keeping your layout intact |
| Any use of color fails | Color is ignored by the parser |
| You need exactly one page | Length is a human preference, not a parsing constraint |
| Bold and italics confuse it | Text styling is stripped out; the words survive |
| Fancy fonts get you rejected | Standard and most modern fonts extract fine; only symbol or icon fonts cause trouble |
None of this means design is free. A cluttered page still costs you with the human who reads it next. But a clean, well-designed resume with a little color and a proper layout is not what gets people filtered out.
Where rejections really come from
When candidates say "the ATS rejected me", the rejection usually came from somewhere else:
- Screening questions. Many application forms ask knockout questions: work authorization, willingness to relocate, years of experience, a required license. A "no" to a required question can end an application automatically, whatever the resume says.
- Recruiter search and filters. If a recruiter searches for "Salesforce" and your resume says "CRM platforms", you may not appear. That is a vocabulary gap, not a formatting failure.
- Volume. A popular posting can draw hundreds of applicants. Plenty of qualified people are passed over because someone else was reviewed first.
- The human reviewer. Most final decisions are made by a person skimming for a few seconds.
Knowing this changes where you spend effort. Formatting only needs to be good enough to parse cleanly. After that, the returns come from matching the posting's language and making your results easy to see.
The practical test
Copy your resume, paste it into a plain text file, and read the result. That is roughly what a parser sees.
Check four things:
- Reading order. Does each job title still sit next to its employer and dates?
- Contact details. Are your name, email, and phone number all there, near the top?
- Section headings. Can you see Experience, Education, and Skills as clear headings?
- Nothing missing. Did any text vanish, such as a name in a header or skills shown as icons?
If the reading order still makes sense and nothing has vanished, a parser will manage. If your job titles have detached from their dates, fix the structure rather than the wording.
How to fix a resume that fails the test
- Rebuild columns as a single column, or use a template whose columns are real layout rather than a table.
- Move contact details into the main body, directly under your name.
- Rename creative headings to the standard ones.
- Replace skill graphics with a plain list, grouped if it is long.
- Export a fresh PDF from your editor or resume builder rather than printing to PDF from a scan.
Our guide to choosing a resume format covers which layouts hold up best, and the most common resume mistakes goes through the content problems that matter once the structure is sound.
Check it automatically
If you would rather not eyeball it, the free Resumeon ATS checker reads your resume the way screening software does and scores five sections: contact information, professional summary, skills, work experience, and education. It needs no account for two checks a day. A free account shows the full breakdown with a specific fix for every issue it finds.
It will not tell you what one particular employer's system does, and no honest tool can. What it will tell you is whether your resume has the structural and content problems that cause trouble across most of them.
Frequently asked questions
Do applicant tracking systems automatically reject resumes?
Rarely on formatting alone. Automatic rejections usually come from knockout screening questions, such as work authorization or a required license. Formatting problems more often make your application hard to find rather than rejected outright.
Is a PDF or a Word document better for an ATS?
A text-based PDF is safe for nearly every modern system and keeps your layout intact. Use a Word file only when the posting asks for one. Avoid scanned PDFs, which contain images rather than text.
Can an ATS read two-column resumes?
Many can, when the columns are built as real page layout. Problems come from columns built with tables or text boxes, which can scramble the reading order. The plain-text test above shows you which kind you have.
Should I remove all design from my resume?
No. A clean design with some color and good spacing is fine for parsing and helps the human reader. Remove only the elements that hide text: images, icons in place of words, and key details in headers or footers.
Does adding keywords in white text help?
No. Hidden text shows up as soon as the resume is extracted to plain text, and recruiters notice it. Use the posting's real terms for skills you genuinely have, in your skills section and bullets.