What an Applicant Tracking System Actually Does
An applicant tracking system is a database with a workflow attached. Its primary job is storing applications, moving candidates through stages, scheduling interviews and keeping the records an employer is required to keep.
It is not, for the most part, a robot deciding your fate. A large amount of resume advice is built on a picture of these systems that was never quite accurate and is now substantially out of date, and acting on it wastes effort that would help elsewhere.
What it does
Note where the decisions actually sit in that list: knockout questions come from a form you filled in, and search is performed by a person. The parse itself makes no judgement.
- Parses your file into structured fields — name, contact, employers, titles, dates, education, skills.
- Stores the original document alongside the parsed record.
- Lets a recruiter search the database by keyword, title, location or qualification.
- Tracks each application through stages, with notes and interview scheduling.
- Optionally applies knockout questions you answered in the application form.
- Keeps the audit trail employers need for compliance.
What it mostly does not do
It does not usually assign your resume a percentage score and bin you below a threshold. Some systems offer a match score as a sorting aid, and recruiters use it as one signal among several, but the widespread claim of automatic rejection below a set percentage is not how most implementations work.
It does not read your resume for meaning. Parsing extracts fields; it does not evaluate whether your experience is any good, which is why a beautifully argued bullet and a dull one parse identically.
It does not reject you for having two pages, for using a PDF, or for a font choice. Those claims persist because they are easy advice to give.
Where applications genuinely die
The last row is the one nobody wants to hear and is frequently the true answer. Many roles are filled before most applications are read, which is why applying early matters more than most formatting decisions.
| Cause | Mechanism |
|---|---|
| Knockout question | You answered no to a required qualification on the form |
| Unreadable file | Image-based PDF parses to nothing |
| Contact details in a header | Parser ignores that region; record has no phone |
| Multi-column layout | Text read across, producing garbled fields |
| Never searched | Recruiter searched terms your resume does not contain |
| Volume | Role filled from the first 50 applications of 800 |
The application form matters more than the resume
Where a portal makes you re-enter your history after uploading a resume, that re-entered data is what populates the searchable record. Abandoning it half-completed, or filling it carelessly, damages you more than any resume formatting choice.
Knockout questions are the one place a genuinely automatic rejection happens. Answer them accurately — a "no" to a required licence ends the application, and answering yes to something untrue ends it later and worse.
Complete every optional field that could be searched: certifications, location, willingness to relocate, availability. Recruiters filter on these, and an empty field excludes you from the filter rather than leaving you neutral.
What actually helps
- A single-column, text-based document with conventional section headings.
- Contact details in the body of the page, never in a header or footer.
- The exact job title from the posting somewhere in your resume, if it honestly describes you.
- The nouns the posting repeats — tools, systems, certifications — in the language it uses.
- A complete application form, including the fields that look optional.
- Applying early, which beats nearly everything else on this list.
What happens after the parse
Once your file is parsed, you exist in the system as a record rather than as a document — a set of fields with the original attached. Everything that follows operates on the record.
A recruiter opens a requisition and searches that database, usually by title first and then by a qualification, a location or a tool. Candidates matching are reviewed in a list view showing a handful of fields, and the resume itself is opened only for the ones worth a closer look. That list view is why a parsed record missing your most recent title is so costly: you are excluded before anything you wrote is read.
Records also persist. Applying to an employer once puts you in their database indefinitely, and recruiters routinely search their existing pool before advertising. A clean, complete record from an application that went nowhere can surface a year later for a role that suits you better — which is a reason to complete the form properly even when the specific job feels like a long shot.
Why the myths persist
Rejection with no feedback is the normal experience of applying for jobs, and an explanation involving software is more comfortable than one involving a person who preferred somebody else.
It is also commercially useful. A large amount of ATS advice is published by companies selling resume scanning, optimisation or rewriting services, and a frightening account of the software is what creates the demand.
None of that means formatting is irrelevant — the failures in the table above are real and worth avoiding. It means the effort is small, mechanical and finishable, rather than an arms race against a system that is mostly a database.
Frequently asked questions
Rarely on a score. The genuinely automatic rejections come from knockout questions you answered on the application form. Most other failures are mechanical — an unreadable file, a garbled parse — or simply a recruiter never searching your terms.
Some offer a match score as a sorting aid, used by a recruiter alongside other signals. The widely repeated claim of automatic rejection below a fixed percentage is not how most implementations actually work.
Often volume — many roles are filled from the first fraction of applications received, which is why applying early beats most formatting decisions. Check the mechanics too: selectable text, contact details in the body, single column.
More than the resume, frequently. The re-entered data is what populates the searchable record, and empty optional fields exclude you from recruiter filters rather than leaving you neutral.