The ATS Resume Guide: Formatting That Parses Every Time

What is an ATS, really?

An Applicant Tracking System is a piece of software companies use to receive and manage job applications. When you submit a resume online, the ATS parses it — that is, it reads the text and turns it into structured data: name, email, jobs, education, skills.

Popular ATS platforms include Workday, Greenhouse, Lever, iCIMS, Taleo, and SuccessFactors. They differ in details but share the same core parsing behavior. If your resume works for one, it likely works for all.

How parsing actually works

Parsing is a text-extraction problem. The ATS reads your file, finds the text, and tries to fit it into predefined fields. If your resume is well-structured, parsing succeeds. If it's not — for example, if your contact info is in a header, a table, or an image — the ATS will either miss it or import it incorrectly.

After parsing, the ATS may also score your resume against the job description by counting keyword matches. This is where ATS-filtering horror stories come from. It's not magic; it's keyword counting.

The 12 ATS-safe formatting rules

1. Single-column layout

Multi-column layouts confuse almost every parser. Text from the left and right columns gets interleaved, breaking the flow. If you must use columns, keep important content in the main column.

2. Standard fonts

Arial, Calibri, Helvetica, Times New Roman, Georgia. No display fonts, no decorative typefaces.

3. Standard section headings

"Work Experience" beats "Where I've Been." Use the headings ATS expects: Experience, Education, Skills, Certifications, Projects, Summary.

4. No tables, text boxes, or graphics for important content

These are separate text objects that many parsers skip. Contact info in a sidebar? Skipped. Job history in a table? Broken.

5. No headers or footers

ATS reads the body of the document. If your name, phone, and email live in the document header, they'll often be ignored.

6. Text-based PDF

Not a scan. Not an image. The PDF must contain a real text layer. Test by selecting and copying text from the exported file.

7. Simple date format

Use "Jan 2022 – Present" or "01/2022 – Present" consistently. Avoid ordinal suffixes ("January 1st") and unusual separators.

8. Plain bullets

Standard bullet characters are fine. Custom icons are not — the parser may drop the bullet and merge lines, or may treat the icon as text and corrupt the sentence.

9. No images for skill bars or icons

Percentage bars rendered as images contain no text. If the underlying information matters, write it out.

10. Standard characters for special terms

Use the ASCII hyphen instead of an en dash in dates where possible. Use standard apostrophes, not curly ones.

11. Consistent capitalization

Don't mix "Software Engineer" and "software engineer." ATS matching is often case-sensitive, and consistency helps both the parser and the human reader.

12. File name that means something

Firstname-Lastname-Resume.pdf. Some systems read file names as a hint for candidate identity.

Keywords: the other half of ATS success

Even a perfectly formatted resume gets filtered if it doesn't contain the terms the recruiter searches for. Fix this by:

• Copying the job description into a plain text editor.
• Highlighting every skill, tool, methodology, and requirement.
• Counting frequency — repeated terms matter most.
• Adding those terms to your skills section and experience bullets.
• Using both acronym and spelled-out forms: "Search Engine Optimization (SEO)."

The goal is coverage without stuffing. If reading your resume out loud sounds like a buzzword dump, remove half the keywords and keep the ones that appear most often in the job description.

How to know if ATS is actually rejecting you

In most cases, ATS does not auto-reject. It surfaces candidates to a recruiter, who makes the call. When you don't hear back, it's usually because:

• Your resume didn't parse cleanly, so the recruiter saw broken fields.
• Your resume didn't contain enough keyword matches to make the shortlist.
• Your resume parsed fine but didn't stand out to the human reader.

Fix the first two with formatting and keywords. Fix the third with a stronger summary, clearer achievements, and a tighter story.

Do you need a "clean" resume for humans too?

Yes. Everything that helps ATS also helps humans. The resume a recruiter sees in the ATS dashboard is often the parsed version — the same fields the parser extracted. If those fields are broken, the recruiter sees a broken candidate.