DEV Community

Cover image for Does an ATS Reject Your CV Before a Human Sees It? What the Data Actually Shows
Anikó Juhász
Anikó Juhász

Posted on

Does an ATS Reject Your CV Before a Human Sees It? What the Data Actually Shows

The advice sounds urgent: "Optimise your CV for ATS or it never gets seen."

Behind it sits a statistic — "75% of CVs are automatically rejected before a human reads them" — that has been repeated in blog posts, LinkedIn courses, and resume-writing services for years.

It's not true. The number was made up.

Where the 75% stat actually came from

Researchers tracing the origin of this figure found a single source: an unverified estimate from a company called Preptel, a resume service that no longer exists. No study. No peer review. No sample size.

The stat spread because it sounded plausible and because it created demand for exactly the service Preptel was selling.

That doesn't mean ATS doesn't matter. It means the fear is disproportionate — and the advice built around it is aimed at the wrong problem.

What ATS actually does

Applicant Tracking Systems are, at their core, databases. They receive applications, parse them into structured data, and help recruiters organise and search through that data.

They don't reject. They rank and sort.

A representative survey of recruiters across tech, healthcare, finance, and manufacturing found that 92% said their ATS does not automatically reject applications based on formatting, design, or structural issues. Only 8% of systems are configured for automatic rejection at all — and those trigger on specific conditions, not on font choices or column layouts.

An application with a two-column layout and a non-standard font doesn't get rejected. It may parse poorly, which causes problems further down the line — but it sits in the database alongside every other application.

What actually causes automatic rejection

Real automatic rejections come from knockout questions — the mandatory questions applicants answer before or just after uploading their CV.

These are binary. There's no grey area.

"Are you authorised to work in the United States?" → No → Rejected immediately.

"Do you hold a valid CPA licence?" → No → Done.

"Do you have at least 5 years of experience in this role?" → No → Out.

For developers in Central and Eastern Europe, this is the filter that ends most applications — not the CV. A developer in Poland applying to a US company's "remote" role gets automatically rejected because the listing was never actually open to them. Not because the keyword "Python" appeared too few times.

This is why checking whether a role is legally accessible to you before applying matters more than any formatting decision.

The timing problem

Even when a role is genuinely accessible, timing beats formatting.

52% of recruiters review applications in order received. Most roles fill their interview shortlist — 10 to 20 candidates — within 48 to 72 hours of the listing going live. Once that shortlist exists, the review stops.

A developer who applies three days after posting, with a perfectly optimised CV, gets no response. Not because of ATS. Because the recruiter already has their candidates.

The practical implication: applying early matters more than reformatting. A solid CV submitted within the first 48 hours beats a redesigned one submitted a week later.

What's technically true about ATS formatting

Not all the ATS advice is wrong. Some formatting choices do cause real problems — not rejection, but poor parsing that buries useful information.

Multi-column layouts. Two-column CVs built in Canva or Figma look good on screen. ATS parsers read left to right, row by row. A two-column document becomes a scrambled mix — skills from the left column and job descriptions from the right run together into unreadable lines of text.

Contact information in Word headers or footers. Some ATS platforms — particularly older Workday and Taleo configurations — ignore document headers entirely when parsing. A CV with the applicant's name and email in the Word header produces a well-structured profile in the database with no contact details attached.

Image-based PDFs. A PDF exported directly from a word processor parses at around 91% accuracy. A scanned document or image-saved PDF drops to around 4% — the system sees a blank page.

Non-standard fonts. Uncommon decorative fonts can break character encoding. Arial, Calibri, Times New Roman, Helvetica — these work reliably. Custom fonts often don't.

The easiest test: copy your entire CV into Notepad (plain text editor). If the sections stay in logical order, dates are readable, and nothing disappears — the document will parse correctly in any system.

What third-generation ATS changes

ATS technology has moved fast. The newest generation — platforms using large language models as their core parsing and evaluation engine — reaches around 97% extraction accuracy. These systems understand context, synonyms, and career trajectory in ways earlier systems couldn't.

"Amazon Web Services" and "AWS" are the same thing to a 2026 ATS. "Senior Engineer" and "Tech Lead" are evaluated in context, not as separate keywords.

The older advice — include both versions of every abbreviation, never use synonyms for your job title — still applies to companies running older systems (and plenty do). But for developers applying to companies using modern hiring software, the formatting anxiety is even less warranted than it used to be.

The real filters haven't changed: work authorisation, location requirements, minimum qualifications — and the job being actually open.

What this means in practice

Before you apply:

Check the posting date. Anything older than 45 days with no update deserves scrutiny. Ghost jobs — listings kept live with no real hire intent — account for roughly 40% of all job postings. No CV optimisation fixes a job that was never going to result in a hire.

Check the authorisation requirements. If the listing doesn't mention hiring outside the US or UK, or doesn't specify a contract type (B2B, EOR, or local entity), ask before you invest time in the application. The question takes two minutes.

Apply early. If the role looks right, submit within 48 hours.

Get the basics right. Single-column layout. Contact information in the document body, not in a Word header. .docx for career portals. Text-based PDF for direct email applications.

That's the list. Everything else is noise.

At CEEhire, every listing is checked before it goes live — whether the company can legally hire you from your country, what the contract type is, and whether the role is actually active.

The formatting advice still matters at the margins. The job being real and accessible to you matters a lot more.

Browse current openings →

Poland · Hungary · Czechia · Slovakia · Romania · Bulgaria · Croatia · Slovenia

Published: 2026-05-26 | CEEhire Blog |

Top comments (1)

Some comments may only be visible to logged-in visitors. Sign in to view all comments.