Are ATS Rejecting My Resume? The 75% Stat Came From a 2012 Sales Pitch

You reformatted the resume. Stripped the columns, deleted the skills bar, saved it as a .docx because someone on Reddit said PDFs get eaten. You applied anyway. Three weeks, nothing.

So you go looking for the reason, and you find it everywhere: 75% of resumes are rejected by applicant tracking systems before a human ever sees them.

Are ATS rejecting my resume, then? Almost certainly not. That number is made up. Not exaggerated, not out of date — invented, by a company trying to sell you something, fourteen years ago. And the real reason nobody replied is duller, harder to fix with formatting, and worth understanding properly.

Where the 75% number actually came from

The figure traces back to a 2012 sales pitch from a startup called Preptel, which sold a service to help your resume "beat" applicant tracking systems. It was marketing copy. No study, no methodology, no dataset — a number in a pitch deck for a product whose value depended on you believing it.

Preptel went out of business in 2013.

The statistic did not. Career consultant Christine Assaf went looking for the original research some years later and found there wasn't any; the number had simply been repeated until it sounded like a finding. It is now cited by resume-writing services, LinkedIn posts, career coaches and roughly every article about ATS software, none of which link to a source, because there isn't one to link to.

It survives because it is useful. If three quarters of resumes are killed by a robot, then there is a trick, and someone can sell you the trick.

What recruiters say when you actually ask them

In late 2025, Enhancv interviewed 25 US recruiters and talent acquisition professionals across tech, healthcare, finance, manufacturing, energy, education and publishing, at companies from under 100 people to over 50,000, using more than ten different ATS platforms.

They asked a simple question: is your system configured to automatically reject resumes based on their content?

Two of the twenty-five said yes. The other twenty-three — 92% — said their ATS rejects nothing on its own. It sorts, it scores, it ranks, it tags. A recruiter still opens the pile.

That matches what the software actually does. Greenhouse, Lever, Ashby and Workable are databases with a workflow attached. They are built to organise applications for a human to work through, not to make hiring decisions. There is no "reject anyone below 60% keyword match" button waiting to be switched on, because that is not a feature companies ask for — it is a lawsuit.

So what is actually filtering you out?

Three things, none of which are the robot in the story.

Knockout questions. These are real, they are automatic, and everybody uses them. They are the questions on the application form itself: are you authorised to work in this country, do you have the required licence, can you work from this location, do you have the minimum years. Answer one of them the wrong way and you are routed to rejected without a recruiter seeing you. This is the only genuinely automatic rejection most companies run, and it has nothing to do with your resume's formatting — it is a compliance filter.

Parsing failures. This one is real but smaller than the internet thinks. Two-column layouts get read in the wrong order and come out as nonsense. Text in headers, footers, images and text boxes can vanish entirely. Skill bars convey nothing to a parser — a five-out-of-five rating on "Python" is a picture of a rectangle. Nobody rejects you for this; you just arrive in the system as an incomplete record, which is worse, because you are still in the pile but the pile now thinks you have no experience.

Volume. This is the one nobody wants to hear. According to SHRM's Talent Acquisition Benchmarking Report, the average corporate job opening attracts around 250 applicants. For a desirable role at a known company, several hundred is normal and four figures is not unusual.

A recruiter has that stack and maybe a week. They do not read to the bottom. Not because they are lazy — because somewhere around the eightieth application they have five decent candidates and a hiring manager waiting, and the marginal value of resume 240 is close to zero.

You were not rejected. You were never reached.

Why "beat the ATS" advice makes it worse

Once you believe a machine is scoring you, the advice that follows is predictable: stuff the keywords, mirror the job description, paste white text into the margins.

The keyword stuffing is visible. A human reads that resume, and "proficient in Python, Python 3, Python programming, Python development" reads exactly like what it is. The white-text trick is worse — it parses fine, then shows up as a wall of nonsense the moment anyone opens the document, and it looks like cheating because it is.

Meanwhile the actual failure modes go unaddressed. People spend an evening optimising a resume that was already fine and none of it on the thing that determines the outcome: how many other people applied, and when.

What moves the needle instead

Timing beats formatting, and it is not close.

Roles collect applications fastest in the first few days. Apply on day one and you are in the first thirty; apply on day ten and you are in the first three hundred, reading identically to everyone around you. Recruiters commonly suggest applying within 48 to 72 hours of a posting going up, and the reason is arithmetic rather than etiquette.

The problem is that finding a job on day one is harder than it sounds. A company posts a role on its own careers page first. Aggregators and boards pick it up afterwards — sometimes hours later, often days. By the time a listing reaches the place most people are looking, the queue has formed.

This is the actual reason we started reading company careers pages and ATS feeds directly rather than scraping boards; the full list we track is public at github.com/trylynceus/jobs, rebuilt every day.

After timing, the ordinary things work: fewer applications with more attention each, a resume in a single-column layout so the parser gets clean text, and answering the screening questions accurately, since those are the ones that actually auto-reject.

And accept that some silence is not about you at all. The Interview Guys' 2025 Ghosting Index found 53% of job seekers were ghosted by an employer in the past year, a three-year high. A portion of the roles you applied to were never filled by anyone — roughly one listing in five is a ghost job, posted with no current intent to hire.

FAQ

Do applicant tracking systems automatically reject resumes? Almost never on content. In Enhancv's 2025 survey of 25 recruiters, 92% said their ATS is not configured to auto-reject based on a resume's content, formatting or match score. What does auto-reject is a knockout question on the application form — work authorisation, licences, location, minimum years.

Is the 75% ATS rejection statistic true? No. It originates in 2012 marketing material from Preptel, a company that folded in 2013, and no study behind it has ever been produced.

Does my resume need to be ATS-friendly? Yes, but the bar is low and it is about parsing rather than passing. Use a single column, real text instead of images or graphics, standard section headings, and keep the important content out of headers and footers. That is most of it. You are making the document readable, not defeating a filter.

Why am I not hearing back from applications? Usually volume. The average opening draws roughly 250 applicants and recruiters stop well before the end of the list. Some of the silence is ghost jobs and abandoned searches. Very little of it is a machine deciding you are unqualified.

---

We read job listings straight from companies' own careers pages and ATS feeds instead of aggregating from boards, which is why roles tend to show up with us before they show up elsewhere. The whole index is free and public at github.com/trylynceus/jobs; the search itself is at app.trylynceus.com.