How to Beat ATS: The Complete Guide to Getting Your Resume Past Applicant Tracking Systems

What Is an ATS and Why It Decides Your Job Search

An Applicant Tracking System (ATS) is the software your resume hits before any human sees it. It collects every application, parses the contents into a structured database, scores you against the job description, and ranks you in a list a recruiter will eventually filter. Workday, Greenhouse, Taleo, iCIMS, Lever, and SmartRecruiters together cover almost every Fortune 500 employer. Jobscan’s 2024 audit of Fortune 500 careers sites found that 97% used an ATS, and Capterra’s 2023 recruiter survey put adoption among US employers with 100+ staff at 78%.

Here is what that means in practice. Studies summarized by Harvard Business Review’s “Hidden Workers” report (Fuller et al., 2021) suggest that roughly three out of four resumes never reach a human recruiter. Your competition is not a person reading carefully, it is a parser trying to fill 12 fields and a ranking algorithm comparing you to a job description.

If you have ever sent 80 applications and heard back from 4, the math is not personal. The ATS filtered most of them out before anyone made a decision about you. The good news: ATS rules are mechanical, and once you understand them you can stop guessing.

For background on the screening systems themselves, see what is an ATS. This guide focuses on what to change in your resume to get past one.

How an ATS Actually Works (in 5 Steps)

1. Parsing - The system extracts text from your file and tries to identify sections: contact info, work experience, education, skills, certifications. PDFs generated from images or Canva templates with overlapping text boxes often fail at this step.
2. Categorization - Parsed data is mapped into structured database fields: current_employer, job_title, start_date, end_date, bullet_points, skills[]. If a field is empty, you are invisible to filtered searches.
3. Keyword matching - The system compares your text to the job description. Modern ATS use TF-IDF and synonym dictionaries; older ones still do exact string matching.
4. Ranking - Each candidate gets a score. Some platforms (Greenhouse, Workday) show recruiters a 0-100 match percentage. Others sort silently.
5. Filtering - Recruiters set thresholds (e.g., “show me only candidates with 75%+ match and the keyword ‘kubernetes’”). Below the threshold, your resume sits unviewed.

A useful mental model: an ATS is not reading your resume, it is filling out a form using your resume. Your job is to make that form easy to fill.

Why Most Resumes Get Rejected

Patterns from recruiter surveys and Jobscan’s resume-grading data point to five recurring reasons:

• Missing keywords - The job description’s exact terms do not appear in your resume.
• Broken formatting - Tables, text boxes, headers, footers, columns, and graphics confuse parsers.
• Wrong file type - Image-based PDFs, .pages files, or Google Doc share links break ingestion.
• Non-standard section headings - “My Adventures” instead of “Work Experience” causes the parser to skip the section.
• Generic content - The resume reads the same regardless of the job, so it never matches a specific listing well.

Each of these is a fixable problem. The rest of this guide is a checklist for fixing them.

Keyword Optimization: The Foundation

Keywords are the single biggest lever in ATS optimization. According to Jobscan’s 2024 benchmark, resumes with a 75%+ keyword match rate are roughly 3x more likely to result in an interview than resumes scoring below 50%.

Step 1: Mine the job description

Print the JD or paste it into a doc. Highlight three categories:

• Hard skills: tools, technologies, certifications. Examples: “Python”, “Salesforce”, “PMP”, “Tableau”, “AWS Lambda”.
• Soft skills mentioned more than once: “cross-functional collaboration”, “stakeholder management”, “data-driven decision making”.
• Domain language: “agile delivery”, “GAAP compliance”, “GTM strategy”, “design system governance”.

Anything mentioned twice or appearing in the “requirements” section is a candidate for inclusion.

Step 2: Use the exact phrasing

If the JD says “project management,” do not write “managed projects” and assume the parser will figure it out. Some will, many will not. Mirror the exact noun phrase at least once, then vary phrasing in adjacent bullets so the prose still reads naturally.

Step 3: Include both acronyms and spelled-out forms

Spell it out the first time and follow with the acronym in parentheses: “Search Engine Optimization (SEO)”, “Customer Relationship Management (CRM)”. Older ATS only index one form; this hedges your bet.

Step 4: Place keywords where they count

• Skills section - The cleanest place for parsers to extract a keyword list.
• Work experience bullets - Use keywords in context, attached to outcomes.
• Professional summary - 2-4 sentences at the top is your highest-density opportunity.
• Section headers - Standard headers like “Work Experience” and “Skills” help parsers categorize correctly.

Step 5: Avoid stuffing

White-text keyword padding, repeating “Python Python Python” in a footer, or stacking 60 unrelated skills - all of these get penalized by modern ATS, and they look terrible to the human who eventually reads the document. The ceiling is roughly 75-85% keyword match. Do not chase 100%; you will end up with a resume a person cannot read.

If you want to skip the manual mining, you can paste your resume and a JD into Tailor and get a keyword gap report in under a minute.

Formatting: Where Most Candidates Lose Silently

Formatting is the place even strong candidates accidentally tank their match score. The parser is doing OCR-adjacent work; help it.

What to do

• Single-column layout with clear section breaks.
• Standard fonts: Arial, Calibri, Helvetica, Garamond, Times New Roman. 10-12pt body, 14-16pt section headings.
• Standard bullets: round or square. Skip emoji bullets and decorative dashes.
• Bold and italic are fine for emphasis; most modern ATS handle them.
• Left-aligned text throughout. No center-aligned bullet lists.
• Section order: Contact, Summary, Experience, Education, Skills, Certifications.

What to avoid

• Tables - Even simple two-column “skills tables” can scramble the parser. Use a paragraph or bulleted list instead.
• Text boxes - Anything floating outside the main text flow may be ignored entirely.
• Headers and footers - Some ATS strip them, taking your contact info with them. Put your name and contact info in the body of the document.
• Multi-column resumes - Beautiful in print, broken in parsing. The parser reads left-to-right top-to-bottom and mixes columns into nonsense.
• Graphics, logos, icons - Unparseable. Star ratings for skills are a recurring offender.
• Custom section names - “Where I’ve Made an Impact” is fine on a portfolio site. On a resume, it is “Work Experience”.

File type

Submit as .docx if the form accepts it. Most major ATS parse Word documents most reliably. PDFs are usually fine if generated from a text-based source (Word, Google Docs export), but PDFs flattened to images or generated by certain design tools (older Canva exports, image-heavy InDesign templates) are a parser death trap. Never submit a screenshot.

For a deeper template walkthrough, see our ATS-friendly resume template breakdown.

Section-by-Section Optimization

Contact Information

Keep it in the document body, not the header. Include name, city + state (or city + country), email, phone, and a LinkedIn URL. A portfolio or GitHub URL helps for technical and creative roles. Skip your full street address; nobody needs it and it can trigger location-based filters incorrectly.

Professional Summary

Two to four sentences. Lead with your professional identity, follow with one or two quantified accomplishments, and end with a hook that maps to the role.

Senior data engineer with 8 years building ETL pipelines on AWS and Snowflake. Led migration of a 12 TB analytics warehouse, cutting query latency 64% and saving $480K annually. Looking to apply distributed systems experience to consumer-facing analytics at scale.

That paragraph hits the keywords “data engineer”, “ETL”, “AWS”, “Snowflake”, “warehouse”, “distributed systems” - all in three sentences a human can read.

Work Experience

Reverse-chronological. Each entry should include:

• Company name, location, dates (Month Year - Month Year)
• Job title (use industry-standard titles, not internal ones; “Senior Software Engineer” rather than “Code Wizard III”)
• 3-6 achievement bullets, each starting with a strong verb and quantified where possible

Bullet structure that works: [Action verb] [what you did] [tool or method] [result with number].

Reduced infrastructure costs $1.4M annually by migrating 18 legacy services from EC2 to ECS Fargate, leading a team of 4 engineers across a 9-month rollout.

Skills

Group skills into categories and list them as a comma-separated paragraph or simple bulleted list. Examples:

• Programming: Python, TypeScript, Go, SQL
• Cloud and infrastructure: AWS (Lambda, EKS, RDS), Terraform, Docker
• Data: Airflow, dbt, Snowflake, Kafka
• Methods: Agile, code review, on-call rotation, mentoring

Aim for 12-20 specific skills, not 60. Older skills you have not used in 5 years can come off unless the JD asks for them.

Education

Degree, institution, graduation year (or expected graduation). GPA only if 3.5+ and you graduated in the last 3-5 years. Skip irrelevant coursework once you have 5+ years of work experience.

Certifications

List active certifications with the issuing body and year: “AWS Solutions Architect - Associate (2024)”, “PMP (2022)”. Expired certs come off unless they signal foundational training.

Tailoring: The Step Most People Skip

A generic resume hits maybe 40-55% match against any specific JD. A tailored resume gets to 75-85%. The delta is where interviews live.

Tailoring does not mean rewriting from scratch. It means:

1. Re-reading the JD and reordering your bullets so the most relevant ones lead each role
2. Swapping in the JD’s specific phrasing where you have honest equivalents
3. Updating the summary to mirror the role’s language
4. Adjusting the skills section so the JD’s must-haves appear first

Plan on 15-20 minutes per application once you have a master resume. For more on this workflow, see our tailor-your-resume guide and the broader set of 2026 resume tips.

Picking the Right Format

For ATS purposes, reverse-chronological wins almost every time. Combination resumes are fine if structured correctly. Pure functional resumes consistently score worst because parsers cannot link skills to employers and dates. The full breakdown is in our resume format guide.

Common Myths to Drop

• “Submitting white text full of keywords still works.” It does not. Modern ATS detect it; recruiters see it the moment they open the document. It will get you blacklisted at some employers.
• “PDF always wins.” Not in 2026. Word is parsed more reliably across the major ATS. Use PDF when the form requires it or when design fidelity matters more than parsing.
• “More keywords is always better.” Above ~85% match, you are starting to look unnatural. The bar is high enough; do not climb past it into stuffing territory.
• “ATS is the same everywhere.” Workday, Greenhouse, Lever, and Taleo each parse slightly differently. Following the rules in this guide gets you above the parsing threshold for all of them.
• “AI-generated resumes always pass ATS.” They pass parsing fine. They often fail the human scan because the writing is generic. See our AI resume optimization guide and the ChatGPT resume prompts breakdown for how to use AI without sounding like everyone else.

A 10-Minute ATS Audit Checklist

Before you submit any application, run this list:

1. Single-column layout, no tables or text boxes
2. Standard section headings (Work Experience, Education, Skills)
3. Contact info in the body, not the header
4. Standard font, 10-12pt body, 14-16pt headings
5. Keywords from the JD in summary, skills, and at least 2 bullets
6. Acronyms and spelled-out forms both present
7. Each work entry has dates, employer, location, and 3-6 quantified bullets
8. Skills section has 12-20 specific items, no 1-5 star ratings
9. File saved as .docx (or text-based PDF if required)
10. No graphics, icons, or photos

If you want this audit automated against a specific job description, paste both into Tailor and you will get a scored gap analysis.

The Honest Bottom Line

ATS optimization is not a magic trick. It is a list of mechanical things you can do that meaningfully change your odds. Get the formatting clean, mirror the JD’s keywords without overdoing it, structure your sections the way parsers expect, and tailor every application even when you would rather not. That is the work that turns 80 applications and 4 callbacks into 25 applications and 8 callbacks. The math is the whole point.