Most advice about applicant tracking systems treats them as a robot that reads your resume and decides whether you are good enough. That is not what they are, and believing it leads people to do things that actively hurt them, like pasting keywords in white text or stripping their resume of anything that looks designed.
This guide explains what an ATS actually does to your file, step by step, where the most famous statistic about it came from, and what really causes a good resume to disappear.
What is an applicant tracking system?
An applicant tracking system is the software an employer uses to collect, store and organise job applications. When you apply through a company careers page or a job board that forwards applications, your resume almost always lands in one.
Think of it as three things stacked together:
- A parser that reads your file and pulls out the text.
- A database that stores each applicant as a record with fields: contact details, work history, education, skills.
- A search and workflow tool that recruiters use to find, filter, rate and move candidates through stages.
The part people worry about, a machine judging their resume, is a much smaller piece of this than the internet suggests.
What happens to your resume after you click apply
1. The file is converted to text
The first thing the system does is extract the text layer from your PDF or Word document. It does not look at your resume the way you do. Colours, columns, icons and layout are thrown away, and what remains is a stream of characters in the order they are stored in the file.
This is the step where the most damage happens, and it is invisible to you. If your PDF is a picture of a page rather than real text, there is nothing to extract. If your contact details sit inside a graphic, they do not exist as far as the system is concerned.
2. The text is split into sections
Next, the parser looks for headings it recognises, such as Experience, Work History, Education and Skills, and uses them to divide the text into sections. Creative headings like "Where I've made a dent" break this step, because the parser has no idea what belongs underneath them.
3. Fields are filled in
Within each section, the parser tries to identify the pieces of each entry: employer, job title, start and end dates, location, degree, school. The result becomes your candidate record. When recruiters search, they search these fields and the extracted text, not your layout.
A role without dates cannot be placed on a timeline. A job title the parser mistook for a company name ends up in the wrong field. Neither error is visible to you, and both make you harder to find.
4. A person searches, filters and reads
Finally, a recruiter works with the records. They search by keyword, filter by location, title or years of experience, and open the resumes that look promising. From this point on the reading is human, and it is fast. In an eye-tracking study by Ladders, 30 professional recruiters spent an average of about 7.4 seconds on an initial resume scan, looking first at current title and employer, then dates, then education (reported by HR Dive). It is a small study by a company in the jobs market, so treat the exact figure loosely; the pattern of a fast first skim is the useful part.
Do ATS systems automatically reject resumes?
You have almost certainly seen the claim that "75% of resumes are rejected by an ATS before a human ever sees them." It is one of the most repeated numbers in career advice, and it has no evidence behind it.
The figure traces back to a 2012 sales pitch from Preptel, a company selling resume optimisation, which went out of business in 2013 and never published a methodology. It was then quoted, re-quoted and cited back to itself until it looked like established fact. JobCannon has traced the claim to its source, as have several recruiting writers.
What does exist is narrower and set by the employer, not invented by the software:
- Knockout questions. "Are you authorised to work in this country?" "Do you hold this licence?" "Can you work on site in this city?" Answer no to a required question and the application may be filtered out automatically. This is the employer's rule, applied consistently, and it has nothing to do with how your resume is written.
- Ranking or matching features. Some systems score how closely a resume matches a posting and sort candidates by that score. A low match does not delete you, but it can push you down a list that a busy recruiter will not scroll to the end of.
So the realistic risk is not that a robot rejects you. It is that you are filed badly, found late or skimmed past.
What actually causes a resume to be missed
These are the failures that happen in practice, roughly in the order they occur.
- Text that is not really text. Scanned resumes, PDFs exported as images and resumes built as graphics produce little or no extractable text. This is the single most damaging problem because it silently empties your record.
- Contact details in the page header or footer. Some parsers skip header and footer areas. Put your name, email and phone in the body of the page.
- Layouts that scramble reading order. Tables, text boxes and some multi-column designs store text in an order that does not match what you see. The parser reads the stored order, so a job title can end up attached to the wrong employer.
- Headings the parser does not recognise. Use the plain names: Experience, Education, Skills, Projects, Certifications.
- Missing or inconsistent dates. Give every role a start and end date in the same format.
- Not using the words in the posting. Recruiters search for the skills and titles they need. If the posting says "project management" and your resume only says "delivery lead", you may not appear in the search, even though you have the experience.
- Nothing that stops a skimming reader. Once you do surface, a recruiter decides in seconds. Bullets that describe duties rather than results give them no reason to keep reading.
How to check what a parser will see
You do not need special software to catch the worst problems.
- The copy and paste test. Open your PDF, select all the text and paste it into a plain text editor such as Notepad or TextEdit. If words are missing, the order is scrambled or you cannot select anything at all, a parser will see the same mess.
- The search test. Press Ctrl+F (or Cmd+F) in the PDF and search for your own name and a skill. If the viewer cannot find them, neither can a parser.
- The job site test. Many job sites fill in an application form from your uploaded resume. The fields they get wrong are a preview of what an ATS will get wrong.
- A rule-based check. The ATS check in this builder scores your resume against 12 published rules, such as whether every role has dates and whether your contact details are complete. It measures the problems above rather than imitating any one vendor's parser, and it tells you which rule you failed.
What this means for how you write your resume
Write for the parser first, so you are filed correctly, then for the human, so you are chosen. In practice that means a clean, single-column layout with standard headings, followed by bullets that start with what you did and end with what happened as a result. Our ATS-friendly resume checklist covers the formatting side in detail, and the guide to quantifying your bullet points covers the part the human reads.
Frequently asked questions
Does every company use an applicant tracking system?
Most medium and large employers do, and many small ones use one indirectly through a job board or HR platform. Very small businesses may simply read applications from an email inbox. It is safest to assume a system will read your file first.
Can an ATS read a PDF resume?
Yes, as long as the PDF contains real text. Modern systems handle text-based PDFs well. The problem is PDFs that are images of a page, such as scanned documents, which contain nothing to read. Our guide to choosing between PDF and Word explains how to tell the difference.
Should I hide keywords in white text to beat the ATS?
No. Parsers extract white text like any other text, so it appears in your candidate record where a recruiter can see it, and it reads as an attempt to game the system. Put real keywords in real sentences instead.
Is the "75% of resumes are rejected by ATS" statistic true?
There is no evidence for it. The figure comes from a 2012 sales pitch by a company called Preptel, which closed in 2013 and never published how it was calculated. Resumes are far more often missed because they were parsed badly or skimmed past by a person.
Does resume formatting still matter if a person reads it anyway?
Yes, twice. Formatting decides whether the parser files your details correctly, which decides whether you are found. Then it decides whether a recruiter can scan your resume in the few seconds they give it.