ATS-Friendly Résumé: Format, Keywords and a Checklist

TL;DR — An ATS-friendly résumé is one an applicant tracking system can parse into the right fields and a recruiter can find by searching the posting's own terms. In practice that means one column, standard section headings, real text instead of images, contact details in the body of the page, and the posting's wording for skills you really have. The software mostly stores and searches applications; the rejections that are genuinely automatic come from knockout questions on the application form, not from a secret grade on your formatting. Set up the format once, then tailor the wording for each job.

An ATS-friendly résumé is a résumé that applicant tracking software can read correctly and that turns up when a recruiter searches for the job's requirements. Two things make one. The first is a layout the parser can follow: a single column, standard headings like Experience and Education, and text rather than graphics. The second is vocabulary: the posting's exact words for the skills, tools and credentials you've actually used, each attached to a line describing real work.

Neither is a trick. The myth that software rejects most résumés before a person sees them pushes people toward keyword stuffing, white-font text and "ATS-proof" templates. What follows is what these systems actually do, the formatting that survives them, how to pull keywords from a posting, a full example, and a checklist.

What does an applicant tracking system do with your résumé?

An applicant tracking system (ATS) is the software employers use to collect applications and move candidates through hiring. When you upload a résumé, it parses the file: it reads the text and fills in fields such as your name, contact details, job titles, employers and dates. Greenhouse's support documentation describes the parser as scanning the résumé and auto-filling "appropriate fields with information it detects." Workday's administrator guide says the same thing in its own words: résumé parsing "populates fields from a resume," and the results "can vary based on resume format and order of words."

Then people search what was stored. Greenhouse's account of what happens after you apply says most of its recruiters review applications "in the order they were sent," and that on busy roles they filter and search the queue, sometimes by answers to the application's questions and sometimes by terms. When a recruiter searches for a term, it says, they'll find exact matches in candidates' applications.

That gives you two jobs, and everything in this guide serves one of them:

1. Be parsed cleanly, so your history lands in the right fields.
2. Be findable and obviously relevant, so you turn up in the search and hold the reader once they open the file.

One practical consequence: parsing isn't only the employer's problem. Workday's guide notes that it doesn't auto-fill a candidate's Skills or Languages fields from the résumé, which is one reason so many applications make you retype things you already uploaded. Whatever the form auto-fills, read it before you click Next. A parse error you catch on the form is one that never reaches the database.

Does an ATS automatically reject résumés?

Rarely for the reasons people fear, and the honest answer depends on the employer's settings. What's reliably automatic is narrower and much more literal.

• Knockout questions. Many applications ask yes-or-no questions before or after the upload: work authorization, a required license, willingness to work certain shifts or relocate. Greenhouse describes rules recruiters can set to auto-reject on answers like these: say "no" when asked whether you're legally allowed to work in the country, and the application is rejected. Those rules are set and controlled directly by recruiters. Answer carefully and truthfully, because this is where applications really do disappear in seconds.
• Scoring and ranking. Some systems have it; whether an employer uses it varies. Greenhouse acknowledges that some companies use AI to analyze, score and auto-reject applications, and says its own auto-rejection runs only on specific rules that recruiters set. USC's career center tells students that an ATS may score your qualifications against the posting and rank your application. You can't see any of these scores, and no outside tool can reproduce them.
• Parse damage. A two-column layout doesn't usually trigger a rejection. It produces a wrong record: titles in the wrong field, skills missing, dates scrambled. Nobody rejects you; you just stop turning up in searches, and the version of you stored in the system is worse than the one you sent.

The useful part is that one résumé handles all three. A file that parses cleanly and uses the posting's words for real experience does well under a keyword search, a ranking feature, or a person reading it top to bottom. The bigger obstacle is volume. Greenhouse notes that many roles get hundreds or even thousands of applications as soon as they're posted, so the first pass is triage, not careful reading. Being clean and plainly relevant is what survives triage.

How do you format a résumé so an ATS can read it?

Most of this is the formatting that makes a résumé easy for a person to skim; a parser is just less forgiving about anything decorative. Greenhouse's documentation lists the formats that cause an unsuccessful or partial parse, and university career centers give the same warnings:

Two more rules round it out. Keep one date format, month and year for each role ("June 2024 – Present"), so each job binds to its dates. And use the reverse-chronological format: a functional résumé separates titles, employers and dates, the exact grouping a parser is trying to build. Résumé formats explained covers date styles and when a combination format makes sense. USC recommends 11- to 12-point type and one-inch margins, which keeps the page readable for the person who opens it after the search.

Should you send an ATS a PDF or a Word document?

Send exactly what the application asks for; that overrides every general rule. When there's no instruction, either works if the file is text. Greenhouse's list of parse problems names résumés uploaded "as an image, rather than a document (such as a .docx or .pdf)," which tells you the trouble is image files and scans, not the extension. UMN Duluth's career center suggests submitting a PDF unless another file type is specified, and USC suggests a Word document or a PDF converted from Word.

Three things matter more than the extension:

• The text has to be real text. Open your PDF and try to select and copy a line. If you can't, no parser can either, and the file is effectively a picture.
• Design-tool templates are the riskiest source. Résumés built in graphic design apps often layer text as shapes or images, which is exactly what Workday's guide warns against. Build it in Word or Google Docs and export.
• Keep the file small. Greenhouse can't parse a résumé larger than 2.5 MB, and an embedded photo or high-resolution graphic is the usual reason a file gets that big.

How do you find the right keywords in a job description?

Keywords aren't a secret list. They're sitting in the posting, and they tell you what the recruiter is likely to type into the search box. Your job is to notice them and mirror them where they're true.

1. Copy the posting into a blank document and highlight every concrete skill, tool, certification, license and qualification.
2. Watch for repetition. A term the posting uses two or three times ("stakeholder communication," "SQL," "project coordination") is almost certainly one someone will search for.
3. Separate the must-haves from the nice-to-haves. Anything under Requirements or Qualifications outranks anything under Preferred or Bonus.
4. Use the exact phrasing. If the posting says "customer success," write "customer success," not "client happiness." If it says "JavaScript," don't write "JS."
5. Name the umbrella and the specifics. If the posting asks for AWS and your résumé lists only Redshift, Lambda and DynamoDB, a search for "AWS" may never find you, even though all of it is AWS work. Write "AWS (Redshift, Lambda, DynamoDB)."

Then the rule that keeps this honest: explain the keyword, don't stuff it. Every term you take from the posting has to sit inside a line describing something you actually did, in a job, a project, a course or a volunteer role. A keyword you can't attach to real work gets dropped, not listed. Put the survivors in two places: your skills section, so a search finds you, and a bullet, so the person who opens the file believes you.

A quick before and after:

• Before: "Worked with numbers and helped organize team stuff."
• After: "Analyzed weekly sales data in Excel and SQL; coordinated schedules for a five-person project team."

Same truth, but the second version contains the words a recruiter actually searches for.

The rule isn't only a moral point. A skills list that claims everything reads as padding to the person who decides whether you get a call. And hidden keywords don't fool anyone for long: DePaul University's career center warns that overstuffing keywords or slipping them in with invisible white text is often obvious to experienced recruiters. UMN Duluth's career center is blunter: "ATS tricks = cheating."

Hard skills vs. soft skills: which ones does an ATS find?

Hard skills, the specific and teachable ones like a programming language, a lab technique, a forklift certification or Spanish fluency, are the terms people search for, so they belong in your skills section in the posting's exact wording. Soft skills like communication and leadership matter to the humans reading, but a search for "great communicator" isn't one recruiters run, so prove those in a bullet instead of listing them. Skills for a résumé covers how to choose both, where each goes, and examples by field.

An ATS-friendly résumé example

Here's what all of the above looks like on one page, for an early-career operations analyst. Every section uses a standard heading, the contact line sits in the body, there's one column, and the skills echo a posting that asked for SQL, Excel, Power BI and inventory control.

ALEX RIVERA
Columbus, OH | (555) 555-0187 | [email protected]
linkedin.com/in/alexrivera

SUMMARY
Operations analyst with two years of inventory and reporting work in a
regional distribution center. Builds the SQL and Excel reports managers
use to plan staffing, cycle counts and stock levels.

EXPERIENCE
Operations Analyst | Riverbend Distribution, Inc. | Columbus, OH
June 2024 – Present
• Built a weekly inventory accuracy report in SQL and Excel that four
  shift supervisors use to schedule cycle counts
• Created a Power BI dashboard of pick rates by shift, replacing a
  manual spreadsheet the operations manager updated by hand
• Cut mis-picks on the two busiest product lines by about a third after
  reorganizing slot locations with the warehouse team
• Trained six new associates on the warehouse management system

Inventory Associate | Riverbend Distribution, Inc. | Columbus, OH
August 2022 – May 2024
• Ran daily cycle counts across 1,200 bin locations
• Logged recurring count discrepancies, which led to a new receiving
  checklist adopted on both shifts

EDUCATION
Bachelor of Science, Business Analytics | State University | Columbus, OH
May 2022

SKILLS
Data and reporting: SQL, Microsoft Excel (pivot tables, XLOOKUP), Power BI
Operations: inventory control, cycle counting, warehouse management systems
Certifications: Lean Six Sigma Yellow Belt

What makes it work for both readers:

• Each job is one block of title, employer, location and dates, in the same order every time, so the parser can bind them.
• The keywords sit in bullets as well as the skills list. "Power BI" appears where it was used, not only where it was claimed.
• Nothing is decorative. No icons, no photo, no columns, no table, so nothing can scramble.
• It reads well to a person. An ATS-friendly résumé isn't a stripped-down résumé; it's an ordinary, well-organized one.

If you're building the content itself from scratch, how to write a résumé goes section by section, and what a résumé is covers the basics. With no work history yet, a résumé with no experience shows how coursework and projects fill the same sections.

How do you check whether your résumé is ATS-friendly?

Start by ignoring the number most checkers sell. A scanner's "match rate" compares two blocks of text, so a résumé no person would advance can be tuned to score near-perfect. Treat it as a vocabulary spellcheck at best; it isn't what the employer's system calculates, if it calculates anything.

The checks that work take about ten minutes:

1. Plain-text test. Open the file, select all, copy, and paste into a plain text editor. What survives is roughly what a parser sees. If the order scrambles, sections collide, bullets vanish or your contact details are missing, fix the layout.
2. PDF copy test. In your exported PDF, try to select a single line. If it highlights as one block or not at all, the text is an image.
3. Must-have test. List the three to six things the posting leads with, repeats, or files under Requirements, and point each one at a specific line on your résumé. A must-have with nothing behind it is a real gap, and knowing that before you apply is worth more than any percentage.
4. Search test. Search your own file for the posting's terms. If something you'd confidently discuss in an interview isn't there in the posting's words, add it inside a bullet.
5. Form test. After you upload, read every field the application auto-filled and correct it before you continue.

If you'd rather have a second pair of eyes, Olive's résumé builder runs an ATS review on a résumé you upload: it checks whether the layout survives parsing and whether each of a posting's stated requirements is backed by a real line in your history, and shows you the gaps. When it's time to adapt the same résumé to a specific job, résumé tailoring rewrites from your own profile, and you keep or revert each change.

If you can't fill most of the must-haves, no wording fixes it, and that's information rather than failure. Never claim a skill you can't defend in an interview: stuffing it past a person only moves the rejection one round later.

The ATS-friendly résumé checklist

Run this before every submission:

• One column; no tables, text boxes, columns or graphics.
• Name, phone and email in the body, not the header or footer.
• Standard headings: Summary, Experience, Education, Skills, Projects, Certifications.
• A common font at 11 to 12 points; no icons, photos or skill bars.
• Full job titles and employer names, with one date format throughout.
• The posting's exact wording for the hard skills and tools you've really used.
• Every keyword backed by a bullet describing real work.
• The file type the application asked for, as real text, and well under 2.5 MB.
• The plain-text paste test passed, with the order intact.
• Knockout questions answered carefully and truthfully.
• Every auto-filled field on the form checked before you moved on.
• Tailored to this posting, not the same file you sent everywhere.

Get those right and you've cleared the part of the process you control. A clean, well-matched résumé makes you findable and readable; it can't make you a match or add openings to your field. If months of applications have produced nothing, look first at the level you're aiming at and the channels you're using, not the font. Fix the résumé once, properly, then put your hours into how you apply, people who can refer you, and a cover letter that gives the reader a reason to call.

Sources

• Greenhouse Support — Unsuccessful resume parse
• Greenhouse — What really happens after you apply for a job?
• Workday Administrator Guide — Concept: Resume Parsing
• University of Minnesota Duluth Career Center — Applicant Tracking System (ATS) Tips
• University of Southern California Career Center — Resume Format Guidelines
• DePaul University Career Center — Optimize Your Resume for ATS Software

A note on sourcing: most of the ATS statistics circulating online, such as the share of large employers using one, the percentage of résumés "rejected by the ATS," or the seconds a recruiter spends, trace back to companies selling résumé-optimization scores. We've left them out rather than repeat a number we can't stand behind. Where this guide describes how these systems behave, it cites the vendors' own documentation or a university career center.