What is an ATS and how does it filter candidates?

An ATS — Applicant Tracking System — is the software that sits between your application and the person doing the hiring. It reads your résumé, extracts what it thinks matters, ranks you against the posting, and decides whether a human ever sees your name. Most large employers use one. Most candidates do not know which one, or what rules it runs on.

The result: up to 75% of résumés are rejected by ATS before a human reads them (Forbes / CareerBuilder). Not because the candidates are unqualified — because the system could not read the document, find the keywords, or parse the fields it expected. Understanding how it filters is not a hack. It is basic mechanics.

What an ATS actually is

At its core, an ATS is a database with a parser attached. When you upload a résumé, the parser tries to map your text into structured fields: name, email, work history, skills, education. The recruiter then searches that database with keywords from the job posting. The system ranks matches. The top-ranked names reach a human. The rest do not.

Up to 90% of employers now use an ATS (Skillademia). For roles posted publicly, the number is effectively 100% — at 250 résumés per corporate opening on average (Glassdoor / HR Digest), no team reads them all by hand. The ATS is the first gate, and it is automated.

75%

of résumés are rejected by ATS before a human sees them

Forbes / CareerBuilder

90%

of employers use an ATS

Skillademia

250

résumés per corporate opening on average

Glassdoor / HR Digest

The three filters

An ATS filters on three things, in roughly this order. Each one is mechanical, and each one is avoidable once you know it exists.

1. Formatting. The parser reads top to bottom, in a single column. Tables, columns, headers, footers, images, and icons break the parsing. A two-column résumé that looks clean to a human reads as scrambled fields to an ATS. The result: your experience ends up in the wrong box, or it is dropped entirely.
2. Keywords. The recruiter searches the parsed database with terms from the posting. If the role asks for "React" and your résumé says "Frontend frameworks," the ATS may not connect them. Exact-match keyword filtering is the default behavior in most systems. Synonyms, abbreviations, and clever phrasing all lose.
3. Fields. The parser expects standard sections: Experience, Education, Skills. Non-standard section names — "My Journey" instead of "Experience" — confuse the parser. So do gaps in expected fields: a missing graduation date, a job title the parser does not recognize, or a skill buried in a paragraph instead of a list.

What gets filtered out — and why

The most common reason for ATS rejection is not lack of skill. It is lack of parseability. A PDF with a custom layout, a résumé designed in Canva with color blocks, or a document saved in an unusual format — all of these can return empty or garbled fields to the parser. The system sees blank where your experience should be, and ranks you accordingly.

The second reason is keyword mismatch. In a market where applications are up roughly 45% year over year — about 11,000 a minute on LinkedIn (LinkedIn) — and 14 million-plus went completely unread in a single quarter (Greenhouse), recruiters rely on keyword search to cut the pile. If your résumé does not contain the exact terms from the posting, you are filtered out before a human learns you exist.

How to get through

The fix is not to game the system. It is to give the system what it is built to read. Five moves:

1. 1
   Use a single-column layout. ATS reads top to bottom. Two-column résumés confuse the parser and drop content. One column, standard margins, no tables.
2. 2
   Use standard fonts and no formatting tricks. Arial, Calibri, Garamond. No icons, no colors, no underlines for emphasis, no text boxes. Plain text in a standard format parses cleanly.
3. 3
   Match the posting's language exactly. If the role asks for "Python" and "AWS," use those exact words. Do not write "fluent in cloud infrastructure." The ATS does not do synonyms.
4. 4
   Submit .docx when the employer does not specify. PDFs are safer for humans, but some ATS parsers read .docx more reliably. If the application gives you a choice and does not specify, .docx is the safer bet for the machine.
5. 5
   Put the keyword in context, not a list at the bottom. A skills list is fine, but the ATS also weighs where a skill appears. "Built a Python API with Flask" in your experience section scores higher than "Python" alone in a skills list.

Where this leaves you

An ATS is not a judgment on your worth. It is a filter on your format. The candidates who get through are not necessarily the most qualified — they are the ones whose résumés the machine could read. That is a low bar, and it is yours to clear.

But clearing the ATS is only the first gate. The second gate is the six-second human scan — and the third is whether you have something checkable behind the paper. A résumé that beats the ATS but has no proof attached still dies at the human stage. The real move is to build the proof first, then format the résumé so the machine does not block it.

FAQ