I spent four years working on the integration layer of a large HR platform. I've seen what happens to your resume between the moment you click "Submit" and the moment a human looks at it. Almost everything you've read online about ATS is either wrong, outdated, or scary in a way that doesn't match reality.

Let's untangle it.

What an ATS actually is

An applicant tracking system is, at heart, a database. It stores applications so recruiters can find and review them. Greenhouse, Lever, Workday, SuccessFactors, Taleo, iCIMS — the names change, the architecture is similar. Your resume goes in, metadata gets extracted, and a recruiter sees a dashboard with candidate rows they can filter and sort.

The system does three things with your resume:

  1. Parses it — extracts structured fields like name, email, work history, education.
  2. Stores it — keeps the original PDF plus the parsed fields.
  3. Makes it searchable — recruiters can keyword-search across stored resumes.

That's it. That's the whole thing. Most systems do not automatically reject your application. Most systems do not give you a "score." Most of what you see labeled "ATS optimization" online is either solving for an imaginary system or optimizing for something that doesn't exist.

What they actually do with your resume

Parsing

When you upload a PDF, the ATS runs a parser that tries to identify sections and extract structured data: your name, email, phone, work history (company, title, dates), education, and skills. The quality of this parse varies wildly. Some systems use document-level heuristics, some use ML models. Some are very good. Some are very bad.

If the parse fails, you'll usually see the result: the "review your information" step of the application asks you to manually correct fields that should have been auto-filled. That's not a rejection — it's the system telling on itself.

Storage and search

Once parsed, your resume sits in the database waiting for a human to look. Recruiters typically work two ways: they either review new applications as they arrive, or they run searches across the stored pool when filling a role. The searches are mostly keyword-based — "Python AND Django AND California" — and the matches are returned as a list the recruiter then browses.

Ranking

Some ATSes offer a "match score" feature. These are typically simple keyword-overlap scores between the job description and the resume, sometimes with learned weights from historical hiring decisions. They are hints for recruiters, not gates. A low match score does not reject you. It may affect what order a recruiter sees you in.

Important

The story that "75% of resumes never reach a human" comes from a 2012 Preptel claim that was never substantiated and has been repeated uncritically ever since. Real-world rejection rates from ATS parse failures are a fraction of that, and "auto-rejection" features are usually disabled by default because they're a liability.

Five ATS myths that won't die

Myth 1: ATSes can't read PDFs

They can. Modern ATSes have been able to parse well-structured PDFs for over a decade. The old "always use .docx" advice is from an era when the parsers were worse. Today, a clean PDF with selectable text is parsed reliably. What ATSes can't reliably parse are image-based PDFs (where the text is actually a scanned image) — but a text-based PDF exported from Word, Google Docs, or LuckyResume is fine.

Myth 2: You must use "ATS-friendly" templates with no styling

You don't. What you must avoid are specific things that break parsers: text in images, text in headers/footers, text inside text boxes, and multi-column layouts where the column order is ambiguous. Clean visual design is fine. Color is fine. Typography is fine.

Myth 3: Hidden white keywords boost your score

This was a trick maybe once. Modern parsers strip formatting and extract raw text — they see the hidden words. Recruiters also have plugins that visualize the extracted text. "White keyword stuffing" now flags your resume as suspicious.

Myth 4: ATSes look for specific resume sections with exact headers

Partially true, then worse than true. Parsers do look for section headers — but they recognize a range of aliases. "Work Experience," "Professional Experience," "Experience," and "Employment History" all parse to the same field. You don't need to say "EXPERIENCE" in all-caps for the system to find it.

Myth 5: A perfect ATS score means you'll get an interview

Match scores do not replace recruiters. Recruiters read resumes. A 95% "ATS match" means you have the keywords; it says nothing about whether your work history is compelling or your bullets are written well.

The formatting rules that matter

Forget the 50-item "ATS-safe template" checklists. These are the rules that actually affect parsing:

  • Use standard section headers. "Experience," "Education," "Skills," "Projects" — these all parse. "My Journey" and "Stuff I've Done" do not.
  • Put dates in the same format, in the same place. "Jan 2022 – Mar 2024" is parseable. "winter of '22 until recently" is not.
  • Use real bullets, not emoji or graphics. The round disc (•) or hyphen (–) is fine. An emoji rocket is not.
  • Keep text out of images. Anything you'd want the system to index must be live text, not part of a PNG or SVG header.
  • Avoid headers and footers for important content. Many parsers skip them. Your name, email, and phone should live in the document body.
  • Single-column is safest. Two-column resumes can parse in strange orders. If you love the look, test it by copy-pasting the rendered PDF into a plain-text editor and checking the order.
  • Use a standard font. System fonts, Google Fonts, or common print fonts (Inter, Source Sans, Garamond, etc.) all work. Rare or display-only fonts can render as glyph boxes in some parsers.
Quick test

Select-all (⌘A / Ctrl+A) in your PDF. Copy. Paste into a plain-text editor. If the resulting plain text is legible top-to-bottom in the correct order, your PDF will parse correctly for 95% of ATSes.

Keyword matching, done right

This is where TikTok gets it almost, but not quite, right.

Yes, keywords matter — because recruiters search for them. Yes, tailoring a resume to a specific job description helps — because the tailored version uses more of the recruiter's vocabulary. But keyword stuffing does not work. What works is: using the job's actual vocabulary when describing work you actually did.

How to find the right keywords

  1. Read the job description three times.
  2. Mark every noun that looks like a technology, methodology, or responsibility. ("SaaS," "B2B," "React," "Figma," "incident response," "A/B testing.")
  3. Mark the top 3–5 verbs. ("Led," "Built," "Designed," "Owned.")
  4. For each marked term, ask: have I done something in this shape? If yes, can you use this vocabulary in a bullet that's still honest?

If you can't honestly match a keyword, don't add it. A recruiter who reads "kubernetes" on a resume from someone who has never run a cluster will catch it in the first 30 seconds of the phone screen.

LuckyResume exports ATS-clean PDFs by default

Single column, live text, standard section headers, vector type. No tweaks needed.

Try the editor →

The 10-point ATS-safe checklist

  1. PDF export is text-based (select-to-copy works).
  2. Single column layout, or two-column tested via copy-paste.
  3. Standard section headers (Experience, Education, Skills, Projects).
  4. Dates in one consistent format ("Jan 2022 – Mar 2024").
  5. Contact info in document body, not page header/footer.
  6. No text inside images or graphics.
  7. Standard fonts (system, Google, or common print).
  8. Standard bullets (•, –) not emoji.
  9. Job titles and company names as plain text, not styled SVG.
  10. File name that includes your real name (jane-smith-resume.pdf, not final-final-v3.pdf).

FAQ

Do I need a different version of my resume for ATS?

No. One well-formatted resume handles both. The days of "a pretty version for humans and a plain version for robots" are over.

What about creative roles — do ATS rules still apply?

If you're applying to a design role at a startup, the ATS rules still apply (because they have a Greenhouse account like everyone else), but the recruiter is also going to look at your portfolio. Ship both.

Are there ATSes that auto-reject people?

Some systems have auto-disqualification features for hard-requirement questions ("Are you legally authorized to work in the US?"). That's different from auto-rejecting based on resume content. The latter is rare and usually disabled.

How do I know what ATS a company uses?

Look at the URL of the application page. boards.greenhouse.io, jobs.lever.co, workday.com — each has a giveaway URL pattern. But honestly, this doesn't matter. A well-formatted resume parses across all of them.

What's the single most important thing?

Use live text in a clean, single-column layout, with standard section headers and consistent date formatting. Do that and you've handled 90% of what ATSes care about. The remaining 10% is writing bullets that are actually good — which is what a human recruiter cares about too. More on writing bullets →