The 10 ATS-killing mistakes that auto-reject your CV before a human sees it. Fix each one with a 1-line change and pass the keyword + format scan.
Most CVs are rejected by software, not by humans. The Applicant Tracking System (ATS) parses your file before any recruiter sees it, and a single formatting error can drop a strong candidate to zero. The good news: every common ATS mistake has a one-line fix.
This guide lists the 10 most frequent ATS killers seen in 2026 hiring pipelines, with the exact change to make. Test your own CV against [our free ATS scanner](/cv-builder) — paste the job description and see what passes, what fails, and which keywords are missing.
Why ATS-killing mistakes are different from "design" mistakes
Design mistakes annoy a human but rarely block them. ATS mistakes are binary: the parser either reads your section or skips it. Skipped sections do not exist for the recruiter. That is why a beautiful CV with a header in a text box can score 0 on contact details, even when the email is right there for the eye to see.
The 10 mistakes ranked by impact
- Header in a text box / image — the parser misses your name, email, phone. Fix: put contact details in plain text at the top of the page.
- Photo in countries that ban it — France, UK, USA flag CVs with photos as compliance risk. Fix: hide the photo for these markets (our [CV Builder](/cv-builder) toggles per country).
- Tables for layout — multi-column tables get parsed in zigzag order. Fix: single-column flow, or a true two-column template that the ATS understands.
- Custom fonts not embedded — uncommon fonts render as squares or get substituted, breaking ligatures and spacing. Fix: stick to system fonts (Arial, Calibri, Georgia, Inter).
- Date formats inconsistent — "Mar 2024", "03/2024", "March 24" mixed in the same CV confuses date extraction. Fix: pick one (we recommend MM/YYYY) and stay consistent.
- Skills in a graphic — bar charts and dots are stripped. The text "Python ●●●●○" becomes "Python". Fix: write the skill name + one short qualifier ("Python — 5 years").
- Experience without bullets — paragraphs of prose are scanned for keywords but rarely parsed into achievements. Fix: 3–5 short bullets per role, each starting with an action verb.
- Missing the job title in the headline — the ATS often weights the top of the document. Fix: put the target role under your name (e.g. "Senior Backend Engineer").
- Headers named in your language only — if you submit to a multinational, "Experiência Profissional" may not match the ATS's keyword list. Fix: use the standard headers in the local language of the role.
- Special characters in file name — accents, spaces, or symbols break some parsers. Fix: name your file "FirstName-LastName-CV.pdf".
What to optimise first
- Run a keyword match against the job description. Aim for 60–80% coverage of the technical terms.
- Reduce your CV to one or two pages, with the strongest experience on top.
- Check that your name, email, and phone appear in the first 200 characters of the document.
- Export as PDF (preferred) or .docx — never as a screenshot or scan.
Before and after
Before: Two-column CV with photo on top-left, contact in a text box, skills as bar charts, experience as paragraphs. ATS score: 38/100.
After: Single-column or ATS-optimised two-column with photo hidden for FR/UK, contact in plain text under the name, skills as a bullet list with qualifiers, experience as 3–4 short bullets per role. ATS score: 87/100.
Mistakes that look harmless but cost interviews
- Using "I" or "We" — most ATS prefer implicit subject ("Led a team of 6")
- Hiding dates ("from 2018") — the parser may classify the role as "current" and stale
- Repeating the same verb ("led, led, led") — the keyword density loses signal
- Putting the most relevant skills below an unrelated section
Quality checklist before submission
- Plain-text contact in the first paragraph
- Standard section headers in the role's language
- One column OR a verified ATS-friendly two-column template
- System font, consistent date format, no bar charts for skills
- File name with no special characters
FAQ
Does PDF or DOCX score better with ATS?
In 2026, most ATS handle both equally well — but PDF is safer for layout consistency. The exception is older versions of Workday and SuccessFactors where DOCX still parses cleaner. If you do not know, send PDF.
Should I hide skills in white text to "trick" the ATS?
No. Modern ATS (Greenhouse, Lever, Workday) flag this as keyword stuffing and most recruiters can see it on copy-paste. The risk-reward is terrible.
How do I test my CV against an ATS without applying?
Use our free [ATS keyword scanner](/cv-builder) — paste the JD and your CV, get coverage % + missing keywords + format flags. No signup, no credit card.
Final takeaway
The ATS is not your enemy — it is a checklist with a deadline. Fix the 10 mistakes above and you go from "auto-reject" to "human reads it" overnight. Then the recruiter decides on content, not on formatting.