Why does the ATS reject my resume?

What an ATS actually does with your file

An applicant tracking system is not reading your resume the way a person does. It runs your file through a parser that tries to break the document into structured fields — name, contact details, employment history with start and end dates, education, skills — and writes those fields into a database row. Everything a recruiter later searches or filters on comes from that row, not from your original document.

This matters more than any advice about wording. If the parser misreads your file, the recruiter is filtering against a corrupted record. You can have exactly the right experience and still never appear in the result set, because the fields the search touches were never populated correctly.

So the first question is never "is my resume good?" It's "does my resume survive being turned into data?"

1. The file has no text layer

This is the most complete failure mode and the hardest to notice. A PDF can contain either real, selectable text or a picture of text. If you exported your resume from a design tool that rasterised it, or generated it with a browser-based builder that rendered the page to a canvas image, the parser extracts nothing at all. The document looks flawless to you and arrives as a blank record.

Test it in five seconds: open your PDF and try to select a line of text with your cursor. If you can't highlight individual words — if the whole page selects as one block, or nothing selects — the file has no text layer and an ATS cannot read a word of it.

2. Multi-column layouts scramble the reading order

A two-column resume looks organised to a human eye, which reads left column then right column. A parser reads in the document's internal order, which is frequently left-to-right across the whole page. The result is interleaved nonsense: your job title from the main column welded to a skill from the sidebar, dates attached to the wrong employer.

Sidebars containing contact details are a particularly common casualty. The parser picks up the body text fine and loses your email address entirely, which is an unrecoverable outcome no matter how strong the rest of the document is.

3. Tables, text boxes and headers hide content

Tables are the classic trap. Many parsers read table cells in an order that has nothing to do with the visual grid, so a skills matrix becomes a jumbled word list. Text boxes are worse: in some document formats they sit outside the main content flow entirely and are skipped.

Putting your name and contact details in the document's header or footer region causes the same problem. Several parsers ignore those regions by design, because in most documents they contain page numbers rather than content.

Layout elements that routinely cost you content:

• Tables and grids — cell reading order is unpredictable
• Text boxes — often outside the parsed content flow
• Headers and footers — frequently skipped entirely
• Columns and sidebars — reading order interleaves
• Graphics, icons and skill-rating bars — carry no extractable text

4. You described the work but never used the word

Parsers and recruiter searches match strings, not meaning. A recruiter filtering for "test automation" is running a text search. If your resume says "built and maintained the Selenium and Cypress suites" and never contains the phrase "test automation", you do not appear in that search — despite being an obvious match.

This is the single most common reason genuinely qualified people get filtered out, and it's the easiest to fix. The category a tool belongs to, the fundamentals implied by your degree, the standard tooling of your role: these are things you plainly did but never wrote down, because they felt too obvious to state.

The fix is not keyword stuffing. It's making sure the vocabulary the search uses appears somewhere your real experience supports it.

5. Dates and titles in a format the parser can't read

Employment history is the field recruiters filter on most aggressively — years of experience, current versus past role, gaps. Parsers expect recognisable date patterns. Creative formats break them: "Summer '23 – Present", a date range expressed only as a graphical timeline, or a job title merged into the same line as the company with an unusual separator.

Keep it dull and conventional: month and year, a standard dash, employer and title as clearly separated text. "Mar 2021 – Present" parses everywhere. "03.21–now" does not.

6. Knockout questions you answered wrong

Not every rejection is a parsing problem. Most application forms include knockout questions — work authorisation, minimum years of experience, a required certification, willingness to relocate. A disqualifying answer routes your application out before a human sees anything, regardless of how good the resume is.

These are worth reading carefully rather than clicking through. A question like "do you have 5+ years of X" is usually a hard filter, and answering it hastily is an avoidable loss.

7. You applied to a role you don't actually match

This is the uncomfortable one, and it's worth being honest about because the alternative wastes months. Sometimes the resume parsed fine, the keywords were there, and you were simply missing things the posting called non-negotiable.

No amount of rewriting fixes a genuine evidence gap. Better formatting and better vocabulary will surface experience you actually have — they cannot manufacture experience you don't. If three of the five stated requirements are absent from your history, the honest read is that your time is better spent on a closer role than on a fourth rewrite of this application.

How to check your own resume today

You can diagnose most of this yourself in about two minutes, without any tool.

A quick self-audit:

• Open your PDF and try to select text. If you can't, nothing else matters — re-export it.
• Copy the entire document and paste it into a plain text editor. What you see is roughly what the parser sees. If it's scrambled or missing your contact details, your layout is the problem.
• Check that every date reads as month-and-year in a conventional format.
• Read the job posting and list the exact terms it repeats. Search your resume for each one.
• Count how many of the stated must-haves you can point to concrete evidence for. If it's under half, consider whether this application is worth the effort.