Applicant tracking systems (ATS) are the bouncers of the modern job hunt. If your resume can't be parsed cleanly, a human never sees it - no matter how qualified you are.
What ATS actually does
It reads your PDF or DOCX, extracts text into structured fields (name, title, work history, dates, skills), and matches that text against the job description. Anything it can't parse becomes a missing field - and missing fields tank your match score before a recruiter ever opens the file.
The five things that get you filtered
| Mistake | Why it fails | Fix |
|---|---|---|
| Tables, columns, and text boxes | Most parsers read top-to-bottom, left-to-right; two-column layouts scramble | Single-column layout only |
| Headers and footers | Many parsers ignore them entirely | Never put contact info there |
| Graphics for section headings | "Experience" as an image is invisible text | Use plain text headings |
| Non-standard section names | Parser looks for known field labels | Use "Experience," "Education," "Skills" |
| Dates as text only | "Since last winter" can't be parsed into a date range | Use "Jan 2023 – Present" |
What gets you through
- A single-column layout in a normal font (Inter, Calibri, Arial, Helvetica) - nothing decorative.
- Reverse-chronological structure, most recent role first.
- Impact bullets that lead with a verb and a number: "Cut onboarding time 38% by redesigning the welcome flow."
- Keywords from the job description, used naturally in context - not stuffed in a hidden white-text block (some ATS flag this as manipulation).
- A .docx or text-based PDF - never a scanned image or a PDF exported from a design tool that flattens text to outlines.
The 30-second test
Open your resume, select all, copy, paste into a plain text editor. If the result reads top-to-bottom in the right order with all the right words, ATS will be fine. If it's scrambled - dates in the wrong place, sections merged, skills missing - fix the layout before you fix anything else. This test catches 90% of ATS rejections before you ever submit.
Beyond parsing: matching, not just passing
Getting parsed cleanly gets you through the gate. Actually ranking well requires matching. Most ATS platforms score resumes against the job description using keyword frequency and semantic similarity - not just presence/absence.
Three things that move your match score:
1. Mirror the job title. If the posting says "Senior Product Designer" and your resume says "Sr. UX/Product Designer," some systems won't connect the dots. Use their exact phrasing somewhere on the page.
2. Cover the required skills list verbatim at least once. Synonyms help for a human reader; the algorithm often wants the literal term from the posting.
3. Quantify every bullet you can. Systems that use semantic scoring still weight bullets with concrete outcomes higher than pure activity descriptions.
A before/after example
Before: "Responsible for managing customer accounts and improving satisfaction."
After: "Managed a portfolio of 45 enterprise accounts, improving renewal rate from 78% to 91% over 12 months through proactive quarterly reviews."
The second version has a number, a timeframe, a method, and an outcome - everything both a human skimmer and an ATS scoring model are looking for.
One more thing nobody tells you
Different ATS platforms (Workday, Greenhouse, Lever, Taleo) parse slightly differently, and you can't know which one a given employer uses. The single-column, plain-text-first approach above is the safe baseline that works across all of them - optimizing further for one specific platform usually isn't worth the effort unless you're applying to a very high volume of roles at companies you know use the same system.
What to do once you're past the ATS
Passing the parser gets you to a human reader, and that's a different game with different rules. Recruiters spend an average of 6-8 seconds on a first pass - long enough to check title match, years of experience, and one or two standout bullets. This means your top third of the page (name, most recent title, top 2-3 bullets) is doing almost all the work. Put your strongest, most quantified achievement first, not chronologically buried under a job from three roles ago.
A note on resume length
One page for under 10 years of experience, two pages beyond that - but length matters less than density. A one-page resume padded with vague bullets loses to a one-page resume where every line has a number and an outcome. If you're cutting content to fit a page, cut the vaguest bullets first, not the most recent role.
Want this done for you against your actual experience? Try the [Resume Builder](https://auth.mane.dev?site=aiagentstudio&template=resume-builder) - it applies this exact ATS checklist automatically.
The one-line summary to remember
If you forget every table in this post, remember this: write for a machine first, a human second, and quantify everything - that combination gets you further than either optimizing purely for keywords or purely for a beautiful design.