You have probably read that applicant tracking systems automatically reject 75% of resumes before a human sees them. It gets repeated everywhere, on career sites, on LinkedIn, in the resume tools trying to sell you a fix.
There is no study behind it. The number traces back to a sales pitch from a company called Preptel, which shut down in 2013 without publishing any methodology. It got quoted by one outlet, then another quoted that one, and a decade later it shows up as fact in articles and chatbot answers. No peer-reviewed research supports it.
So why does your resume still vanish into the void? The honest answer is more useful than the myth, and it changes what you should actually do.
What an ATS really does to your resume
An applicant tracking system is mostly a database. It stores applications, lets recruiters search them, and ranks them against a job posting. Around 98.8% of Fortune 500 companies run one, according to Jobscan's 2025 ATS usage report, so if you are applying to mid-size or large employers, your resume is going into one of these systems regardless.
Here is the part that matters: most of them do not silently auto-reject you on keywords. What they do is rank and sort. Your resume lands somewhere in a stack, and a recruiter juggling 20 to 40 open roles decides how far down that stack they bother to read.
That said, the systems do filter qualified people out, just not the way the myth claims. Harvard Business School and Accenture surveyed 2,250 employers for their 2021 report Hidden Workers: Untapped Talent. They found that 88% of employers agreed their own automated systems screen out qualified, high-skilled candidates, and they estimated 27 million Americans are stuck as "hidden workers" because of it. The filtering is real. It just happens through hard knockout rules (a missing degree, a years-of-experience minimum, a location mismatch) and through low ranking, not a keyword bot throwing three out of four resumes in the trash.
Sources: Jobscan (2025), The Ladders eye-tracking study (2018), Glassdoor hiring benchmarks.
Once you clear the automated sorting, a human gives you about 7.4 seconds. That is the median time recruiters spent on an initial resume scan in The Ladders' eye-tracking study, and it is not laziness, it is triage. The average corporate posting pulls roughly 250 applications for 4 to 6 interview slots.
So the real goal is not "trick the bot." It is two things at once: rank high enough to land in the handful of resumes a recruiter actually opens, and survive a 7.4-second human skim once you are there. The ten tactics below do both.
1. Mirror the job description's exact words
ATS keyword matching is usually literal, not semantic. If the posting says "REST APIs" and your resume says "web services," many parsers will not connect the two. You know they are the same thing. The software does not.
Read the posting, pull out the exact phrases used for the required skills, and use those phrases, not your preferred synonyms. If it says "microservices architecture," write microservices architecture. You can mention "distributed systems" too, but the literal string from the posting has to be on the page somewhere.
2. Prove skills in your bullets, not just in a skills list
A comma-separated skills section is fine, and parsers read it. But a skill shows up far stronger when it is attached to something you actually did. "Python" sitting in a list is a weak signal. "Built Python microservices handling 10,000 requests per second" is the same keyword plus evidence a human will stop on.
A reliable shape for a bullet: action verb, the tool or skill, what you built, and the result. Keep the skills section for breadth, but carry your most important keywords up into the experience section where they carry weight.
3. Open every bullet with a real action verb
Phrases like "responsible for," "helped with," and "worked on" are filler. They describe proximity to work, not work. Swap them for verbs that name what you did:
- Instead of "Responsible for maintaining the API," write "Maintained a REST API serving 50,000 daily active users."
- Instead of "Helped with the database migration," write "Migrated a PostgreSQL database to a new cluster with zero downtime."
The verb gets you started. What follows it, the scope and the outcome, is what actually lands.
4. Put numbers in roughly half your bullets
Quantified bullets read as more credible to both the ranking algorithm and the human skimming for impact. You do not need a number on every line, but aim for about half. Useful things to count:
- People affected: users, customers, stakeholders, team size
- Money: revenue influenced, cost saved, budget owned
- Performance: latency, throughput, error rate, uptime
- Time: hours saved, cycle time cut, deadlines hit
"Improved application performance" says nothing. "Cut API response time from 800ms to 120ms, lifting retention 15%" says everything. Approximate figures are fine when you do not have exact ones: "around 50,000 users," "nearly 40% faster."
5. Use section headings the parser expects
An ATS finds your content by recognizing standard headings. Get clever with them and the parser may not know where your experience section begins.
| Use this | Not this |
|---|---|
| Experience / Work Experience | My Journey |
| Education | What I've Learned |
| Skills | Things I'm Good At |
| Projects | Stuff I've Built |
Save the personality for the writing inside each section. The labels should be boring on purpose.
6. Keep the layout single-column and plain
This is the one genuine formatting trap. Many parsers flatten your resume into text, and when they hit a two-column layout, a table, or a text box, the reading order scrambles. Skills get dropped. Jobscan's formatting research found that a multi-column layout cut skills-section parsing accuracy to about 46%, down from 65% for a single column. Nearly half your skills, gone, before anyone reads a word.
Stick to a single column, standard fonts (Arial, Calibri, Times New Roman), ordinary bullet points, and clear section breaks. Skip the infographic templates, skill-rating bars, headshots, and sidebars. Quick test: copy your resume, paste it into a plain text editor, and read it top to bottom. If the order still makes sense and nothing important disappeared, a parser will handle it.
Which system you are submitting to changes how strict this is:
| ATS platform | Common at | What to watch |
|---|---|---|
| Workday | Large enterprise, finance, healthcare | Strict parsing; single-column plain text strongly preferred |
| SAP SuccessFactors | Manufacturing, global enterprise | Avoid tables and graphics; keyword placement matters |
| Oracle Taleo | Legacy enterprise, government contractors | Older parser; plain text often beats PDF |
| Greenhouse / Lever | Tech companies, startups | More recruiter-friendly; a weak summary will not be rescued by keywords |
Workday and SuccessFactors alone cover more than half of Fortune 500 employers, and both punish fancy layouts. When in doubt, assume the strict case.
7. Match the required qualifications head-on
Postings usually split "required" from "preferred," and the required list is what gates you. Go through every required item and make sure it appears, in the posting's own words, somewhere on your resume.
If you are missing one, do not hide it and hope. Name the closest real experience you have. A posting asks for "5+ years of Python" and you have three? Write "3 years of Python development" plainly. A recruiter can decide whether three is close enough. A parser that finds nothing scores you a clean zero.
8. Spell out abbreviations once
Literal matching cuts both ways with acronyms. "CI/CD" and "Continuous Integration / Continuous Deployment" can register as two different keywords, and a posting might use either. Give both forms once:
- CI/CD (Continuous Integration / Continuous Deployment)
- AWS (Amazon Web Services)
- REST (Representational State Transfer)
After the first mention, the short form is fine. The parser only needs to see each version a single time to log the match.
9. Keep it to one or two pages
Some systems truncate long resumes, and recruiters reward brevity because saying more with less is itself a signal. A rough guide:
- 0 to 2 years of experience: one page, and that is expected
- 3 to 7 years: one or two pages, driven by relevance
- 8+ years: two pages maximum, weighted toward recent work
Every line should earn its spot. If a bullet does not show a skill or an outcome that matters for the roles you are chasing, cut it.
10. Test against the actual posting before you apply
The single highest-leverage move is checking your resume against the specific job before you hit submit, not after a month of silence. You are looking for a few things:
- Do the required skills appear, in the posting's wording?
- Does every bullet start with an action verb?
- Do about half your bullets carry a number?
- Is the layout single-column and parser-safe?
This is the loop PassTheBot runs for you: paste the job description, upload your resume, and get a score with specific gaps to close rather than a vague "looks good." Closing those gaps is usually the difference between landing in the first 20 resumes a recruiter opens and sitting in the 230 they never reach.
Key takeaways
- The "75% auto-rejected" stat is a myth from a defunct vendor. ATS mostly ranks and sorts; it does not bulk-delete on keywords.
- Real filtering happens through knockout rules and low ranking. 88% of employers admit their systems screen out qualified people (Harvard / Accenture, 2021).
- Two goals: rank high enough to get opened, then survive a 7.4-second human scan.
- Mirror exact keywords, prove skills inside quantified bullets, and keep the layout single-column. A multi-column design can lose half your skills section in parsing.
- Tailor to the specific posting every time. Generic resumes rank generically.
FAQ
Do applicant tracking systems automatically reject resumes?
Mostly no. The common claim that ATS auto-reject 75% of resumes is not backed by any study. Most systems rank and sort applications for a recruiter to review. The real filtering happens through employer-set knockout rules (such as a required degree or minimum years of experience) and through your resume ranking too low for anyone to open it.
What is the most important thing for passing an ATS?
Matching the language of the specific job description. ATS keyword matching is literal, so the exact phrases from the posting need to appear on your resume, ideally inside your experience bullets rather than only in a skills list. Tailoring to each posting matters more than any formatting trick.
Does resume formatting actually affect ATS parsing?
Yes, but less than people assume. Single-column layouts parse reliably. Multi-column layouts, tables, text boxes, and graphics can scramble the reading order, and one analysis found multi-column designs cut skills-section parsing accuracy to roughly 46%. Use a single column with standard headings and you have solved the formatting problem.
How long should my resume be to pass an ATS?
One page for early-career candidates, one to two pages for mid-level, and two pages maximum for senior roles. Some systems truncate very long resumes, and recruiters spend a median of 7.4 seconds on a first scan, so brevity helps you on both fronts.
Are PDF or Word resumes better for an ATS?
Most modern systems parse both well, but a few older platforms like Oracle Taleo read plain text or Word more reliably than PDF. If a posting names a format, follow it. If not, a simple single-column PDF is safe for most systems, and a Word document is the safest choice when you know the employer uses legacy software.
Want to see how your resume ranks against a specific posting before you apply? Run it through PassTheBot's free ATS check and get the exact keyword and formatting gaps to fix. For a blunter read on what is holding your resume back, the Resume Roast goes past keywords into what a recruiter actually thinks in those first 7 seconds.