How to Write an ATS-Friendly Resume in 2026

The vast majority of mid-size and large companies use an Applicant Tracking System (ATS) to collect, parse, and rank resumes before a recruiter reads a single one. If your resume isn't formatted in a way the software can parse — or doesn't contain the language the job posting uses — it can get filtered out before a human ever sees it, regardless of how qualified you are.

What ATS software actually does

An ATS extracts text from your resume file and maps it into fields: name, contact info, work history, skills, education. Some systems also score resumes against the job description's keywords. The failure mode isn't usually "rejected" — it's "parsed incorrectly," where your job titles or dates end up in the wrong field, or entire sections get dropped because the layout confused the parser.

That distinction matters because it changes what you're actually optimizing for. You're not trying to trick an algorithm into a high score — you're trying to make sure the software can correctly read what's already a strong resume. A beautifully written resume that parses into a jumbled mess of misattributed dates and missing sections will still lose to a plainer one that parses cleanly.

Where people go wrong even with a "good-looking" template

This is the most common trap: a resume template downloaded from a design site looks polished on screen but is built with layout elements — text boxes, tables, multi-column grids, graphic sidebars — that a parser reads out of order or skips entirely. The visual quality of a template tells you nothing about how it parses. If you didn't build the file yourself and don't know what's happening under the hood, it's worth testing before you rely on it (see the checklist below).

Formatting rules that actually matter

• Use a single-column layout. Multi-column resumes and text boxes are the single most common cause of scrambled parsing, because most parsers read left-to-right, top-to-bottom in one stream.
• Stick to standard section headers — "Experience," "Education," "Skills" — rather than creative labels like "My Journey" that a parser won't recognize.
• Avoid tables, headers/footers, and embedded images for anything containing text you want read. Contact info placed in a header is frequently skipped entirely.
• Export as a PDF from a tool built for it (not a scanned image), or use .docx if the posting requests it. Both parse fine as long as the underlying layout is simple.
• Use standard, widely-installed fonts. Unusual fonts can render as garbled characters when a parser extracts text.
• Keep dates in a consistent, unambiguous format ("Jan 2023 – Mar 2025") in the same position relative to each role, so the parser doesn't have to guess which text is a date.

A simple pre-submission checklist

Before you submit a resume through an online application portal, it's worth spending two minutes verifying it will actually parse the way you expect:

1. Select all the text in your exported PDF and paste it into a plain text editor. If the result is readable, in a sensible order, with nothing missing — that's roughly what a parser will see too.
2. Check that your name and contact details aren't sitting inside a header/footer region or a text box layered over the page.
3. Confirm every section has a plain, standard heading a machine (and a skimming recruiter) would recognize instantly.
4. Make sure job titles, company names, and dates are in normal body text, not inside a table cell or graphic element.
5. Name the file sensibly — "FirstName_LastName_Resume.pdf" — some systems display the filename directly to recruiters.

Keywords: match the job description, don't stuff it

ATS keyword matching isn't magic — it's largely literal text matching against the job posting, and Indeed's guide to ATS resume keywords notes the average resume is missing about half of a posting's target keywords. If the posting says "stakeholder management" and your resume says "working with clients," that's a miss even though a human would read them as equivalent. The fix is to mirror the exact terms the posting uses, in context, in your experience bullets — not to paste a wall of keywords in white text (which some systems now flag) or cram unrelated terms into a skills list. Our full guide to resume keywords covers this in more depth.

As a worked example: if a posting asks for "experience with cross-functional stakeholder management in an agile environment," a bullet that says "Coordinated with engineering, design, and marketing stakeholders across two-week sprint cycles" hits nearly every phrase a parser and a recruiter would both be scanning for — without reading as keyword-stuffed, because it's describing a real, specific thing you did.

This is also why a single generic resume performs worse than one tailored per application: the required keywords change from job to job, even for similar titles at different companies.

Skills section: how ATS actually reads it

A skills section is one of the most heavily weighted fields in most parsers, which makes it worth getting right rather than treating as an afterthought. List tools and technologies explicitly rather than only broad categories — "Figma, Sketch, Adobe XD" parses and matches better than just "design tools." If you use an acronym the posting also uses (like "CRM" or "SEO"), spell it out at least once elsewhere on the resume too, since some parsers match on the full term and some on the acronym, and you want to be safe either way.

Common myths, debunked

• "ATS rejects resumes over one page." Most modern systems have no page-length rule — length matters more for the human reader afterward (see our guide on how long a resume should be).
• "You need to guess the exact ATS brand and format for it." Nearly every major ATS (Workday, Greenhouse, Lever, iCIMS) parses standard, simple layouts fine — the formatting rules above apply broadly.
• "Adding a photo automatically disqualifies you." It depends on the country and system — photos are common on European CVs and rarely cause parsing issues, though some US companies strip them for bias-reduction reasons.
• "A slightly lower keyword match means automatic rejection." Most systems rank rather than hard-reject on keyword score alone — a strong, well-matched resume with a few missing exact phrases still gets seen by a recruiter far more often than people assume.

The fastest way to keep resumes ATS-safe and tailored

Manually rewriting a resume for every posting is the main reason people stop tailoring after a few applications. zeroApply.ai reads the job description directly and generates a resume matched to it, using ATS-safe templates by default — so tailoring per application takes under a minute instead of an hour. You can still edit every field before exporting. See pricing or browse templates.