How to Beat the ATS: A Practical Guide for 2026
Most "beat the ATS" advice is recycled, misleading, or both. The truth: ATS systems are simpler than people think, but the rules for passing them are real. This guide explains how modern ATS actually works, what matters (and what doesn't), and the exact optimization steps that move resumes from filtered to forwarded.
What an ATS actually does
An Applicant Tracking System is software that ingests, parses, and ranks resumes. The dominant systems — Workday, Greenhouse, Lever, iCIMS, Taleo, Ashby — all do roughly the same thing:
1. Parse the uploaded file into structured fields (name, work history, education, skills).
2. Match the parsed content against the job description.
3. Rank candidates by match score.
4. Surface top-ranked candidates to recruiters.
Recruiters then read the top of the stack first. If your resume ranks low, it may technically be in the system but it will never be read.
There are exactly two ways an ATS hurts you: (1) parsing errors that mangle your resume into unreadable fields, and (2) low keyword match that ranks you below the cutoff. Optimize for both.
Formatting rules that actually matter
Most ATS parsers in 2026 are vastly better than they were in 2018. Modern systems handle PDF well, parse most common layouts cleanly, and don't require the rigid "ATS-friendly templates" the SEO content has been pushing for a decade. Still, certain choices break parsers consistently. Avoid them.
- Single-column layout. Multi-column resumes break in many parsers.
- Standard section headings: "Experience," "Education," "Skills." Don't get clever.
- Reverse-chronological work history.
- Standard fonts: Calibri, Arial, Helvetica, Times, Garamond, Georgia.
- PDF is fine. So is .docx. Don't use .pages, .odt, or images.
- No headers/footers for important content (some parsers skip these).
- No tables for layout (use them for actual tabular data only).
- No graphics, icons, or images of text — they're invisible to parsers.
Formatting rules that hold up:
The keyword strategy that wins
Keyword optimization is where most candidates leave the most points on the table. The rule: ATS does roughly exact matching, not semantic matching. If the JD says "TypeScript" and your resume says "JavaScript," that's a miss.
The strategy:
- Identify the top 15-25 keywords from the JD (tools like our Keyword Extractor do this).
- Mirror the relevant ones verbatim in your resume — same casing, same form.
- Distribute them naturally across the resume — Summary, Skills, Experience bullets.
- Don't stuff. Recruiters notice. ATS doesn't reward density past a threshold.
- Focus on technical/domain terms first — those are weighted highest.
Adding "Kubernetes" to your resume because the JD asks for it — when you've never touched it — is short-sighted. The ATS will love it; the technical interview will not. Only mirror keywords that genuinely match your experience.
The section-by-section optimization
Each section has different ATS implications:
- Header — name, email, phone, city/state, LinkedIn. ATS reads name from this; don't put it in a graphic header.
- Summary — 2-3 lines, keyword-dense, written for the specific role. Skip "Objective" — it's dated.
- Skills — list 12-20 relevant terms. Single column, comma-separated or grouped by category.
- Experience — reverse-chronological. Each role: title, company, location, dates, then 3-5 bullets.
- Education — degree, institution, graduation year. Optional GPA if 3.5+ and within ~5 years of graduation.
- Certifications — list any current certs. Especially valuable in healthcare, finance, project management.
How to write experience bullets that pass ATS and impress humans
Every bullet should: start with a strong verb, describe what you did, and quantify the outcome. The standard formula is [Action verb] + [what you did] + [measurable result].
Examples:
- "Led migration of recommendation service from batch to streaming, reducing p95 latency 38% across 40M monthly users."
- "Built lifecycle program from scratch sourcing $3.2M annual pipeline; lifted MQL-to-SQL conversion from 14% to 22%."
- "Closed 142% of quota in 2024 across $1.4M book through targeted outbound to mid-market RevOps leaders."
How to test your resume against ATS
Before you submit, run two checks:
- Copy your resume into a plain text editor. If sections appear out of order, sections are missing, or content is garbled — your formatting is breaking parsers. Fix it.
- Use an ATS keyword checker (like our free ATS Resume Checker) against the actual job description. Aim for 70%+ match before submitting.
Most resumes can be moved from "ranked low" to "ranked high" with 30 minutes of focused keyword and formatting work per application. It's the highest-leverage time you can spend in your job search.
Common myths to ignore
A few persistent pieces of bad advice you can safely disregard in 2026:
- "Use white-on-white invisible keywords." Detected and penalized. Don't.
- "Submit a Word doc instead of PDF." Both work fine. PDF preserves formatting better.
- "Avoid headers and footers." Modern parsers handle them — just don't put load-bearing content there.
- "Use the exact same job title from the JD." Your actual title is fine. Add the JD title in parens if helpful.
- "ATS scores you on grammar." Most don't. Recruiters do.
Frequently Asked Questions
What ATS match score should I aim for?
70% or higher. 70-100% means strong alignment. 50-69% has real gaps to close. Below 50% suggests the role may not be a fit, or your resume needs significant tailoring.
Are PDF or Word documents better for ATS?
Both work. PDF is preferred — it preserves formatting reliably across systems and devices. Use Word only if the application explicitly requires it.
Can ATS read images and graphics?
No. Anything in an image — logos, headshots, graphical headers, icons — is invisible to ATS parsers. Keep critical content as plain text.
Should every resume be a different version?
Yes — at minimum, tailor keywords and the summary to each role. A 30-minute customization on each application is the single biggest lever in your job search.
Apply this guide automatically.
CareerThings AI builds cover letters and resumes that follow every principle in this guide — tailored to any specific job posting in seconds.
Related Guides
How to Write a Cover Letter (That Actually Gets You an Interview)
Most cover letter advice on the internet is identical, vague, and 10 years old. This one is different. Below is the exact framework professional recruiters use to screen cover letters at scale, the structure that consistently moves candidates forward, and concrete examples for entry-level, mid-career, and senior roles. Read it once, write yours in 30 minutes, and never write a generic cover letter again.
How Long Should a Resume Be? (One Page or Two?)
The question "how long should my resume be" has spawned a decade of conflicting advice. The answer is simpler than the internet suggests: it depends on years of experience, role seniority, and field. This guide gives you a decision tree that resolves the question in under a minute.
How to Write a Resume Summary (with 12 Examples)
The resume summary is 2-3 lines at the top of your resume. It's the most-read section after your name. Done well, it gets the recruiter to read the rest of the page. Done poorly, it triggers the skip. This guide covers the formula, the common mistakes, and 12 concrete examples to model from.