10 reasons the ATS is rejecting your resume before a human sees it

Workday, Greenhouse, Lever, Taleo, iCIMS, and SmartRecruiters all do roughly the same thing: they parse your resume into structured text, score it against the job description, and rank you in the stack. Recruiters then sort by that score. If you're not in the top 25% of matches, you're effectively invisible. Here's what trips the filter.

1. Two-column layouts

Designed in Canva or Word's "modern" templates, two-column resumes look great to humans and parse like a word-salad to ATS. Sections end up interleaved, dates attach to the wrong job, and skills get dropped entirely.

Fix: Use a single column, top to bottom. Boring is fine. Parseable is the goal.

2. Text inside headers and footers

Many ATS parsers ignore anything in the document's header or footer. Put your name, contact info, or section headings there and they often vanish.

Fix: Keep all content in the body of the document.

3. Skill bars, icons, and infographics

"Photoshop ████████░░ 80%" reads to the ATS as either nothing or as garbled characters. Same for icon-only contact info and graphical pie charts of your skill mix.

Fix: Use plain text. "Photoshop — 6 years" beats any bar chart.

4. Non-standard section titles

"Where I've Made Things Happen" is cute. The ATS expects "Experience" or "Work Experience" — anything else risks the whole section being misclassified.

Fix: Use the standard labels: Summary, Experience, Education, Skills, Certifications.

5. Missing keywords from the job description

ATS scoring is essentially keyword overlap weighted by section. If the JD says "Salesforce administration" and your resume says "CRM management", the score drops even though you mean the same thing.

Fix: Mirror the exact noun phrases from the JD when they're true for you. Don't paraphrase, don't synonym-swap.

6. Skills hidden in a "skills" list only

A bulleted skills list helps, but the ATS weights skills that appear in context within your job bullets more heavily. A "Python" tag at the bottom is worth less than "Built ETL pipeline in Python processing 2M rows/day."

Fix: Embed your top 5 keywords inside actual achievement bullets, not just in a tag cloud.

7. Tables and text boxes

Same problem as columns — the parser doesn't know what order to read cells in, so your dates, titles, and companies end up scrambled.

Fix: Use simple paragraph and bullet formatting only.

8. Inconsistent or missing dates

"2022 – Present" in one job, "March '21 – Jan '22" in another, and "Summer 2020" in a third confuses the parser. Some ATS will assume the role is current; others will exclude it entirely from years-of-experience calculations.

Fix: Use one consistent format: "Mar 2022 – Present" everywhere.

9. PDFs exported from design tools

Figma, Canva, and InDesign exports often produce PDFs where the "text" is actually rendered as outlined shapes or stored in non-standard reading order. The ATS can't extract usable text.

Fix: Write the resume in Word or Google Docs and export to PDF from there. Or upload a .docx.

10. File names that scream "template"

"Resume_Template_v3_FINAL.pdf" doesn't get auto-rejected, but it's the kind of low-effort signal a tired recruiter notices. Some ATS also pre-tag known template filenames.

Fix: Name the file "FirstLast_Resume_2026.pdf".

What actually moves the score

After cleaning up the formatting issues above, the biggest single lever is keyword overlap with the specific job description — not generic "ATS-optimized" advice from a template site. Two minutes spent mirroring 8–12 real noun phrases from the JD will outperform an hour of rewording.

If you want to see your actual ATS score for a specific job rather than guess, that's the entire point of an ATS scanner — paste your resume and the JD and see the gap before you submit.