"Rejected by the ATS" is a convenient story, and it is rarely the full one. Most systems store and rank applications for a person to review. Even so, there are specific ways an application never reaches a human, and others where a human passes. The reasons below come up most often in recruiter and resume-industry guides, grouped by where the problem happens.
When a person may never see your application
You failed a knockout question
Recruiters can add questions about work authorisation, location, minimum experience or required certifications. An answer that does not meet the requirement can end the application. Fix: read each question carefully and answer truthfully. If the requirement is not met, no formatting change will help.
Your file did not parse cleanly
Tables, text boxes, multi-column designs, page headers and footers, graphics and scanned pages can leave details missing or in the wrong place. Fix: use a single column and a text-based file, then run the plain-text test described in our best practices guide.
The parser did not recognise your headings
A heading like "My Journey" instead of "Experience" can stop the system from sorting your jobs into the right fields. Fix: use Summary, Experience, Education and Skills.
Dates, titles or locations are missing or inconsistent
Formats such as "Jan '21", dates with no month, or a missing job title make it harder to build an accurate profile. Fix: give every job a title, employer, location and dates in one consistent format.
Your resume lacks the terms recruiters search for
Recruiters often search their database for specific tools, skills and titles. If your resume says "spreadsheets" and they search "Microsoft Excel", you may not appear. Fix: use the exact terms from the job post wherever they are true.
When a person sees you and passes
The resume is not tailored to the role
A generic resume makes the reader work to see why you fit. Fix: adjust your summary, top skills and first few bullets to the job post.
Keyword stuffing
A block of keywords, or terms repeated without context, gets you past nothing and costs you the human read. Fix: work the terms into bullets that show what you did.
Duties instead of results
"Responsible for reports" tells a reader little. "Built weekly sales reports used by six managers" tells them more. Fix: start with the action and add a number where you have one.
Too long or hard to scan
Recruiters read quickly. Fix: aim for one to two pages, put your strongest and most relevant information first, and cut older roles that do not help.
Typos and inconsistent formatting
Small errors make careful work look careless. Fix: proofread, and ask someone else to read it.
Sheer volume
Popular jobs attract many applicants, and a recruiter can only review so many. Applying early and matching the job post closely helps you stand out. This is the one cause you cannot fully fix.
About the 75% figure
You will see "75% of resumes are rejected by ATS" in many articles on this topic. Several reviews could not trace it to an original source, so we do not use it. Read more in What is an ATS resume?
What to fix first
Work through these in order, because each one only matters if the one before it is right:
- Check that your answers to screening questions are accurate.
- Make sure the file is a single column and text-based, and that the plain-text test reads in the right order.
- Switch to standard headings.
- Add the terms from the job post that honestly describe you.
- Rewrite weak bullets so each one shows a result.
Common questions
Does a two-column resume get rejected automatically?
Will adding keywords get me an interview?
How can I tell if my resume parsed correctly?
Sources
- Huntr: how applicant tracking systems work
- BetaNews: study on the auto-rejection claim (Enhancv survey)
- Jobscan: common resume formatting mistakes
- ATS Verification: ATS resume myths debunked
- RecruitBPM: resume columns and ATS compatibility in 2026
- ResumeGeni: why parsing fails
- Hiration: does an ATS automatically reject your resume?