Most rejected resumes never get rejected by a person. They get filtered out by software the candidate never sees. This guide covers what that software actually does, what it scores on, and how to write a resume that gets through every common ATS without losing the qualities that get you hired by humans.
The advice here is calibrated to the five platforms that account for most of the screening at scale: Workday, Greenhouse, Lever, Taleo, and iCIMS. Patterns differ between them, but the rules of thumb that work on all five will work for almost any hiring process you encounter.
What an Applicant Tracking System actually is
An Applicant Tracking System is a database with a workflow on top of it. Resumes come in through a job posting, a referral, or a sourcing tool. The ATS parses the resume into structured fields, stores the candidate, applies any automated screening rules the recruiting team configured, and presents a ranked list of candidates the recruiter can search and filter.
Two things follow from that. First, the ATS is mostly a tool for the recruiter, not a wall to keep candidates out. The most common way a strong resume gets buried is that the parser misread the resume, the recruiter searched for a keyword the resume actually contained but the parser had dropped, and the candidate never surfaced.
Second, the rules of the game are about being findable. A well-structured resume that contains the literal phrases the recruiter will search for is more likely to surface than a beautifully designed one that the parser couldn't read.
Why companies use them
A single mid-market role commonly gets 250 applications. A high-visibility role at a well-known employer can get thousands. Even with a strong recruiting team, no human can read every resume that arrives. The ATS exists to let recruiters operate at that scale without dropping qualified candidates by accident.
Some of the more aggressive uses of the ATS, like automatic knockout rules on years of experience or required credentials, are decisions the employer made, not behaviors of the software. The same platform looks different at a company that trusts its recruiters versus one that hard-codes filters to reduce volume.
The five platforms that decide most outcomes
The major ATS platforms differ in parser quality and recruiter workflow, but a resume that performs well on the most strict platform usually performs well everywhere.
Most enterprise resumes flow through Workday. Strict on parsing, prefers DOCX, often re-keys data into structured fields a candidate later edits.
Common at fast-growth tech companies. Better parser, accepts PDFs cleanly, ranks on a scorecard recruiters customize per role.
Used heavily in mid-market tech. Parses PDFs well. Keyword search is the recruiter's primary tool — searchable terms beat clever phrasing.
Legacy enterprise system at large traditional employers. The strictest parser in common use. Old Taleo instances still struggle with PDFs.
Used by many Fortune 500 companies, especially in retail, healthcare, and finance. Strong keyword search; recruiters rely on it heavily for filtering at volume.
How parsing works (and where it fails)
The parser's job is to convert your resume into structured data: name, contact info, work history with titles and dates, education, skills, certifications. Most parsers do this with a mix of layout heuristics and trained models. They read top to bottom, left to right, and look for section headers they recognize.
They fail predictably. Multi-column layouts cause the parser to interleave content from different columns. Tables turn into runs of broken text. Headers and footers are often skipped entirely. Graphics and icons render as gibberish or empty space. PDFs generated by design tools sometimes store text as outlined shapes rather than real characters, which look fine to a human but appear blank to the parser.
The practical rule is the one piece of advice every recruiter will give you: use a single-column layout with standard section headers, export to PDF or DOCX from a tool that produces real text, and verify by saving the file as plain text and reading the result.
How scoring works
Recruiters configure scoring per role, usually by selecting required keywords, preferred keywords, and minimum experience levels. Most platforms then produce a score and let the recruiter sort the candidate list by it. The exact weights vary by platform and configuration, but the inputs are consistent.
Does the resume contain the role's expected keywords, and in what density and position? A keyword inside an achievement bullet weighs more than the same keyword listed alone in a skills section.
If the posting wants a senior, the resume should show senior-level titles and years of experience. ATS systems infer level from titles, dates, and explicit year counts.
Standard sections (Experience, Education, Skills, Certifications) should exist and be findable. Missing sections shave score points and can disqualify outright.
Licenses and certifications (RN, CPA, AWS Solutions Architect, PMP) are scanned as discrete signals. Recruiters often filter on them as a hard requirement.
Length, font choices, and whether the parser produced a clean candidate record. A clean parse doesn't earn you points, but a broken parse loses them.
What gets you rejected before scoring
Some rejections happen before the resume ever enters the scoring step. The most common ones:
- Knockout questions on the application form that the candidate answers in a way the recruiter flagged as a hard no.
- A required certification or license missing from the resume. The system often searches for the literal string.
- Years of experience clearly below the posted threshold, inferred from dated work history.
- Work-authorization filters at companies that don't sponsor visas, when the candidate indicated they require sponsorship.
- Geographic filters when the role is on-site and the candidate is far enough away that the recruiter doesn't want to review.
These are policy decisions, not algorithmic ones. A resume that would otherwise score well can be filtered out by a single checkbox answer. Read the application form carefully and answer deliberately.
Myths that waste your time
ATS systems reject resumes that don't have keywords in white text.
They don't. Hidden-keyword tricks were detected and penalized over a decade ago. Modern ATS reads exactly what you wrote and ignores formatting tricks.
If I hit 80% keyword match, I'll get the interview.
Keyword match is one input among several. A resume with a high keyword match but no titles or years of experience that fit the role can still score below the cutoff.
The ATS picks the candidates. Humans don't actually read anything.
The ATS shortlists. A human recruiter then reviews the shortlist, usually in seconds per resume. Both gates matter. The ATS gets you into the room; the recruiter decides whether you stay.
I should put every skill I've ever touched in the skills section.
Recruiters can see when a skills section is padded. Some ATS searches penalize skill stuffing. Keep the section honest and put your strongest signals into achievement bullets where they're load-bearing.
The formatting rules that actually matter
A short list of choices accounts for almost every parsing failure. Fix these and most of the ATS problem is solved.
- Single column for the work experience section. A header or sidebar with contact info is fine; the body should not be multi-column.
- Standard section headers, spelled the way an ATS expects. Experience, Education, Skills, Certifications, Projects.
- Plain text exported from Word, Google Docs, or a code-based editor. PDFs from design tools often store text as outlined shapes that parsers can't read.
- Contact information in the body of the document, not the Word header. Headers are inconsistently parsed across platforms.
- Dates on every job (month and year is enough), in a consistent format throughout.
- Job titles that mirror the language of the role you're applying for. A title like "Resident Genius" reads as a joke to a parser; "Senior Software Engineer" reads as a data point.
How to test your resume against an ATS
You don't need a real recruiter's ATS instance to validate. The cheapest test is a plain-text export. Anything an ATS can do, a plain text reader can also do.
- Save your resume as plain text from your editor. If sections collapse, line breaks fall apart, or job titles end up in the wrong place, the ATS will see the same mess.
- Search the plain-text version for each keyword in the job description. If a keyword from the posting isn't there, the ATS won't find it either.
- Read the plain text top to bottom. The first three lines, the section headers, and the first bullet of each role are the highest-signal positions. Move your strongest material there.
- Run the file through a free ATS checker that parses it the same way Workday or Lever does. The output tells you which sections were detected and which keywords matched.
When the ATS matters less than you think
The ATS plays a smaller role in three situations: when you have a referral inside the company, when the role is at a small enough company that a human reviews everything anyway, and when you reach the recruiter directly through outbound.
Resumes still get parsed even with a referral, but a referred candidate's record is usually opened and read by the recruiter regardless of automated score. If you have access to a referral, use it. The ATS rules above still apply to the contents of the resume, but the screening pressure on the keyword side relaxes meaningfully.
What this means for how you write the resume
The strategic takeaway is short. Write the resume for the human reviewer who will read it after the ATS clears it, and make a small number of structural choices so the ATS clears it cleanly.
Practically, that means: write strong achievement bullets, quantify what you can, use the language from the job posting when it fits naturally, and pass the resume through a plain-text check before you submit it. None of this requires tradeoffs. A well-structured resume reads better to humans and parses better through software.
The remaining pages in this cluster go deeper on individual pieces of that puzzle.
Cluster: ATS Fundamentals deep dives
This is the pillar guide. The pages below cover specific parts of the ATS story in more depth.
See your resume's ATS score
The fastest way to apply this guide is to upload your resume and let the checker score it against the role you're targeting. Keywords, formatting, and bullet quality all show up in the report, with specific suggestions you can accept or edit.
Score my resume