There's a comforting story candidates tell themselves after a rejection: "the ATS filtered me out". It's comforting because it makes the rejection feel mechanical, not personal. The harder truth is that modern ATS rarely auto-rejects on its own. What it does is rank, parse, and surface — and a CV that gets ranked low or parsed badly ends up at the bottom of a stack a recruiter never finishes reading. The effect is the same as a rejection. The cause is rarely the one the internet warns you about.
If you want to understand why your CV keeps disappearing, the question isn't "is my CV ATS-friendly?". It's "which of these nine specific things is happening to my CV when it lands in the system?".
1. The job title on your CV doesn't match the one in the listing
This is the single most common reason a strong candidate gets ranked low. The ATS scores resumes against the job description; if the job is "Backend Engineer" and your CV reads "Software Developer", the title-match field is empty. The recruiter sees a low score and skips the file.
The fix is uncomfortable but cheap: rewrite your current job title (or your headline) to match the role you're applying to, when it's defensible. "Software Developer (Backend Focus)" is honest if your work was mostly backend. "Backend Engineer" alone is a stretch if you spent 60% of your time on the frontend. The line to hold is truthful, not literal.
2. The exact keywords from the job description aren't anywhere on your CV
ATS keyword matching is still mostly literal in 2026. If the job description says "Postgres" five times and your CV says "PostgreSQL" twice, the match score takes a hit even though they're the same database. Same with "K8s" vs "Kubernetes", "GCP" vs "Google Cloud Platform", "customer success" vs "customer support".
The fix isn't keyword stuffing. It's mirroring the job description's exact phrasing once, somewhere natural in your CV — typically in the skills section or a bullet that already describes the relevant work. If the listing uses both "Postgres" and "PostgreSQL", use both yourself.
3. The skills section is buried below page two
Most ATS parsers weight content in the first 30% of the document more heavily, on the assumption that's where the candidate puts their strongest material. A skills section on page three of a long CV gets discounted regardless of what's in it.
The fix: a compact skills block in the top quarter of page one. Five to ten primary items, no fluff. Detailed skill demonstrations stay where they belong, in the experience bullets.
4. Dates use a format the parser can't read
An ATS that misreads your dates ends up with gaps that aren't really there, or worse, decides you're still at a job you left in 2022. Either way, your CV ends up filtered into a category you don't belong in ("3 years of experience" instead of "7").
Use the formats parsers handle reliably:
- Jan 2023 – Present
- January 2023 – April 2025
- 01/2023 – 04/2025
Avoid:
- Jan '23 (the apostrophe trips parsers).
- Q1 2023 – Q2 2024 (quarters aren't a standard date format).
- A two-line date stacked vertically ("Jan 2023" on one line, "Present" on the next).
Keep the date on a single line, right after the job title and company.
5. Section headings are creative instead of standard
The parser looks for headings it recognizes: Experience, Education, Skills, Certifications, Projects. When you replace "Experience" with "My Journey So Far" or "Where I've Built Things", the parser doesn't know what to do with the section. The content gets dumped into a generic bucket or lost entirely.
Keep headings literal. Save the creative voice for the summary and the bullets.
6. The file is a scan, image, or a CV inside a PDF that's actually an image
This kills you silently. A PDF made from Word or Google Docs is text-based and parses fine. A PDF made by scanning a printed CV, or by exporting a designer's mockup as an image-PDF, is just a picture to the ATS. The parser extracts no text, which means no skills, no experience, no name — your CV becomes a blank record.
The one-second test: open your CV PDF, try to select and copy a sentence with your mouse. If text gets selected, you're fine. If the cursor turns into a crosshair and nothing selects, your CV is an image. Re-export from the original source as a text-based PDF.
7. Tables and multi-column layouts scramble the content order
Many ATS still struggle with multi-column layouts. A common pattern in design-heavy CV templates is a left sidebar with skills and contact info, plus a right main column with experience. The parser reads left-to-right across the page, mixing your address into the middle of a job description.
The safe layout is single-column, top-to-bottom. If you love your two-column template, run it through this experiment: open the PDF, select all (Ctrl/Cmd + A), copy, and paste into a plain text editor. The order you see in the text editor is the order the ATS sees. If your skills are interleaved with random sentences from your job history, the layout is the problem.
8. The contact block is in the header or as an image
Some templates put the name, email, and phone number inside the document header (the special Word region that repeats on every page). Many ATS parsers skip headers entirely. Your CV gets uploaded, parsed, and indexed with no contact details. The recruiter loves it, can't find a phone number, and moves on.
Same failure mode when the contact info is rendered as a designed graphic block — an icon followed by text inside an image. The text isn't actually text to the parser.
Fix: name, email, phone, city, and (optional) LinkedIn URL as plain text at the very top of page one, inside the document body, not the header.
9. You're applying to a role that doesn't exist for your profile
The least technical reason and the most painful. Sometimes the ATS isn't rejecting you — the role was already filled internally before posting, or the budget closed, or the job exists at a level you can't credibly fill. No CV change wins those.
The signal that this is what's happening: rejection within two hours of submitting, multiple roles at the same company, all silent. ATS scoring runs in seconds; getting auto-deprioritized happens fast. Move on. Spend the energy on the next five roles where the fit is real.
How to actually check your CV against an ATS
Three practical checks before any application:
- The copy-paste test. Open the CV PDF, select all, paste into a plain text file. Read it top to bottom. If it reads coherently, parses will work. If sections are jumbled, fix the layout.
- The job description overlay. Paste the job description and your CV into the same document. Highlight every word in the job description that appears in your CV. The CV should hit the primary keywords at least once, ideally in the exact phrasing.
- The free ATS scanner. Several free tools (Jobscan, Resume Worded, Skillsyncer) score your CV against a job description. Don't aim for 100% — that's keyword stuffing — but anything under 60% means a real gap to close.
If you're starting from a LinkedIn export or using something like Postulit to generate your CV, the output is almost always ATS-safe out of the box (single column, standard headings, text-based PDF). What still falls on you is the tailoring per role — the title rewrite, the keyword mirroring, the skills block ordering. The template is the easy part. The fit signal is the work.