How do I write a résumé an ATS can read?

The internet is full of ATS rules that do not matter. Columns do not get you rejected. PDFs do not break parsers. There is no universal "ATS score" that decides your fate. A 2026 analysis of 1.7 million applications by Huntr found that no major ATS auto-rejects résumés — the real filters are knockout questions and the 6–10 seconds a recruiter spends on first scan.

What parsing actually sees

An ATS is a database with search, not a robot gatekeeper. When you upload a résumé, the parser extracts structured fields: name, contact, work history, education, skills. It does not read your summary paragraph. It does not score your creativity. It does not care about your objective statement.

What matters is whether the extracted fields match what a recruiter searches for. If the job asks for "React" and your résumé says "frontend frameworks," you may not surface in a keyword search. This is not a conspiracy. It is search mechanics — and it is why mirroring the job's exact language matters more than any formatting trick.

6–10 sec

recruiters spend on first scan of a résumé

Huntr

98%

of large organizations use an ATS

Onrec

0

major ATS platforms auto-reject for formatting alone

Huntr

Format rules that matter

The rules are boring because they work. Not because an AI is checking them — because a human is scanning in six seconds, and clutter kills clarity.

1. 1
   One column. Two-column résumés do not break modern parsers, but they do force a recruiter's eye to jump around. One column is the fastest path from top to bottom.
2. 2
   Standard fonts. Arial, Calibri, Garamond. No icons, no colors, no novelty typefaces. The parser handles them fine — but the human scan is what decides your week.
3. 3
   Exact language from the posting. If the role asks for "TypeScript," say "TypeScript" — not "strongly typed JavaScript." The recruiter searches for what they wrote, not what you think means the same thing.
4. 4
   Contact info in the body, not headers. Some older parsers skip headers and footers. Put your name, email, phone, and LinkedIn in the main text.
5. 5
   Save as PDF. Every major ATS reads PDFs reliably in 2026. The myth that PDFs break parsers comes from legacy systems that are largely retired.

What does not matter

Stop worrying about these. They are distractions sold by résumé-checker tools that make money from your anxiety.

• Keyword density. There is no magic percentage of keywords that triggers an approval. Write naturally for humans who scan in six seconds.
• .docx vs PDF. Both work. PDF is fine. The formatting matters more than the file extension.
• ATS-friendly templates. Any clean, one-column layout is ATS-friendly. You do not need a special template — you need clarity.
• One-page limits. Huntr's analysis of 225,000 résumés found two-page résumés perform as well or better than one-page at every level. Fill the space with outcomes, not padding.

The real filter

The 75% rejection rate you hear about is real — but it is not caused by machines. It is caused by volume. A corporate opening gets 250 résumés on average, and a recruiter cannot read them all. The ATS helps them search and sort. The recruiter decides who advances. The filter is human attention, not algorithmic rejection.

That changes how you write. Your goal is not to game a parser. It is to make the six-second scan so clear that the recruiter stops and reads more. Put your strongest qualification in the top third. Use numbers. Attach a link to something runnable. That is what turns a scan into a hire.

FAQ