Formatting That Survives Every ATS (With Templates)

I have configured six different ATS platforms across four companies. Greenhouse, Lever, Workday, iCIMS, Taleo, and a custom-built system that one startup insisted on building in-house (it was terrible). And across all of them, the single most common reason a qualified candidate's resume gets mangled has nothing to do with keywords or experience.

It is formatting.

I cannot count the number of times I have opened a parsed resume in the ATS and seen what looks like a ransom note. Text from the header jammed into the experience section. Bullet points turned into a single run-on paragraph. Entire sections missing because they were in a text box or a table cell that the parser could not read. Dates scattered randomly. Job titles merged with company names.

The candidate had a beautiful resume. The ATS had a different opinion.

Here is everything I have learned about what formatting survives and what does not, across every major ATS platform I have worked with.

The File Format Debate: PDF vs. DOCX

This is the question I get asked most often, and the answer is less straightforward than the internet wants it to be.

DOCX wins in most ATS platforms. Greenhouse, Lever, and iCIMS all parse DOCX files more reliably than PDFs. The reason is structural: a DOCX file is essentially XML under the hood. It has tagged content — headings, paragraphs, lists — that the parser can read programmatically. A PDF is closer to an image with text coordinates. The parser has to reconstruct the structure by analyzing where text blocks sit on the page, which is inherently less reliable.

Workday, notably, handles PDFs better than most. Its parser was built to handle government and enterprise documents that are almost always PDFs. But even Workday occasionally struggles with complex PDF layouts.

Taleo is the worst with PDFs. I have seen Taleo turn a perfectly formatted PDF resume into a wall of text with no line breaks. If you are applying to large enterprises — banks, insurance companies, government contractors — assume Taleo and send DOCX.

The exception: design roles. If you are a graphic designer, UX designer, or any role where visual presentation is part of the evaluation, a PDF preserves your layout. Most creative hiring managers expect a PDF. But know that the parsed version in the ATS may look rough. What saves you is that for design roles, the recruiter almost always downloads and opens the original file.

My recommendation: Submit DOCX unless the application specifically asks for PDF or you are in a visual design role. If you want to be thorough, keep both versions ready and match the format to what the application requests.

Section Headings the ATS Recognizes

Every ATS parser is trained on standard resume section headings. When it encounters one, it maps the content that follows into the correct database field. When it encounters a creative heading, it guesses. And it guesses wrong more often than you would think.

Headings that parse reliably across all platforms:

• Experience (or Work Experience, Professional Experience)
• Education
• Skills
• Summary (or Professional Summary)
• Certifications
• Projects

Headings that cause problems:

• "Where I Have Made an Impact" (the parser does not know this means Experience)
• "My Journey" (could be anything)
• "Toolbox" (the parser may not map this to Skills)
• "What I Bring to the Table" (this is not a section, it is a conversation starter)
• "Selected Achievements" (some parsers handle this, others do not)

I had a candidate for a senior engineering role whose resume had sections labeled "The Technical Stuff," "Places I Have Built Things," and "The Paper." Creative? Sure. The ATS parsed "Places I Have Built Things" as a skills section because it contained company names that looked like skill keywords. His actual work history was invisible in the recruiter's view.

Use standard headings. Save the creativity for the content underneath them.

Fonts That Do Not Break Parsing

The font question matters less than most people think, but it can still cause issues.

Safe fonts that every ATS handles:

• Arial
• Calibri
• Times New Roman
• Garamond
• Helvetica
• Georgia
• Cambria

Fonts that occasionally cause issues:

• Custom or downloaded fonts (the ATS may not have the font installed, causing character substitution)
• Icon fonts (wingdings, dingbats, custom icon sets used for visual bullet points)
• Fonts with unusual character encoding

The real issue is not the font itself. It is what happens when the ATS does not have the font. Most modern systems substitute a standard font and move on. But some older systems — and Taleo is the main offender — will occasionally drop characters or substitute them with question marks or boxes.

Stick with system fonts. Calibri or Arial for sans-serif, Garamond or Georgia for serif. No one has ever been rejected for using Calibri.

The Column Problem

Two-column resumes are one of the most common formatting traps I see.

Modern resume templates — the ones you find on Canva, Zety, or premium resume template sites — love two-column layouts. A narrow left column for contact information, skills, and education. A wider right column for experience. They look clean and modern on paper.

In an ATS, they are a disaster.

Most ATS parsers read content in a single stream from top to bottom. When they encounter a two-column layout, they have two choices: read the left column top to bottom, then the right column top to bottom, or read across both columns line by line. Different parsers make different choices. Some do neither correctly.

The result: your skills section gets interleaved with your experience section. Your contact information appears in the middle of your work history. Your education shows up between two job descriptions.

I have seen this happen with Greenhouse (which is generally good at parsing) when the columns were created using text boxes rather than tables. I have seen it happen with every parser when the columns were created using the column feature in Word.

The rule: use a single-column layout. One column of content, flowing from top to bottom. Your resume can still look professional and modern with a single column. It just cannot look like a magazine layout.

Tables, Text Boxes, and Headers/Footers

Tables. Some resume templates use invisible tables to create alignment — putting dates on the right side of a line while the job title is on the left. This works in some ATS platforms (Greenhouse handles simple tables reasonably well) and breaks in others (Taleo and older iCIMS versions often strip table content entirely). If you use tables, keep them simple: two columns maximum, no merged cells, no nested tables. Better yet, skip tables and use tab stops for alignment.

Text boxes. Never. I have never seen a text box parse correctly in any ATS. The content inside text boxes is treated as a floating object, and most parsers either ignore it completely or dump it at the end of the document out of context. If your contact information is in a text box, the ATS may not capture your email or phone number. I have literally seen resumes come through with no contact information because everything was in a header text box.

Headers and footers. This is the trap that catches the most people. It seems logical to put your name, email, and phone number in the document header. It looks clean in the printed version. But many ATS parsers skip headers and footers entirely. They were designed to ignore page numbers and document titles, and your contact information gets caught in that filter.

Put your contact information in the body of the document, at the top, in regular text. Not in a header. Not in a text box. Not in a graphic. Plain text, first thing in the document.

Graphics, Images, and Visual Elements

Skill bars, pie charts, icons, profile photos, logos, infographic elements — none of these parse. The ATS sees an image placeholder or nothing at all.

The skill bar trend is particularly harmful. Candidates use visual bars or dots to represent their proficiency level in different skills (4 out of 5 dots for Python, 3 out of 5 for SQL). The ATS cannot read the image. It cannot interpret the dots. Your skills section appears empty.

I reviewed a candidate for a data analyst role who seemed to have zero technical skills based on the ATS view. When I downloaded the original resume out of curiosity, it was full of beautifully designed skill bars showing Python, SQL, R, Tableau, and Excel. None of it had parsed. If I had not been curious enough to open the original file — and I usually am not — that candidate would have been rejected for appearing unqualified.

The rule: if information is important, it must exist as text. Not as an image, not as a graphic, not as a visual element. Text.

The Encoding and Special Character Problem

This one is subtle and catches people who copy-paste content from other sources.

When you copy text from a website, a PDF, or even from Google Docs into a Word document, you sometimes bring along invisible formatting and non-standard characters. Smart quotes instead of straight quotes. Em dashes that are actually Unicode characters. Bullet points that are special symbols rather than standard list formatting.

Most of the time, this is fine. But I have seen cases where non-standard characters cause the parser to truncate content at the point of the unusual character. Everything after the character disappears.

If you are building your resume from scratch in Word or Google Docs, this is rarely an issue. If you are copying content from other sources, paste as plain text first (Ctrl+Shift+V), then reformat.

A Template Structure That Works

Here is the structure I recommend based on what I have seen parse reliably across all six ATS platforms I have used:

Notice what this template does not have: columns, tables, text boxes, graphics, headers, footers, or creative section headings. It is plain. It is boring. It parses perfectly every time.

Does this mean your resume has to look like a 1995 Word document? No. You can still use professional formatting within this structure. Bold for job titles. A horizontal line between sections. Consistent font sizing (14pt for your name, 12pt for section headings, 10.5-11pt for body text). These elements do not interfere with parsing.

The goal is not to make the ugliest resume possible. The goal is to make a resume that looks professional to a human and parses cleanly for a machine. Those two objectives are compatible — they just rule out the Instagram-worthy designs that template companies sell.

The Test You Should Run Before You Submit

Here is something most candidates never do, and it takes less than five minutes.

Copy all the text from your resume. Open a plain text editor (Notepad on Windows, TextEdit in plain text mode on Mac). Paste. Read what you see.

If the plain text version contains all your information in a logical order — contact info, then summary, then experience with job titles and bullets, then education, then skills — your resume will probably parse well.

If the plain text version is a mess — sections out of order, text missing, bullets merged into paragraphs, contact information scattered throughout — the ATS will see the same mess.

This is not a perfect test. Some ATS parsers are smarter than a plain text conversion. But it catches the most common problems: text boxes that do not convert, columns that reorder content, graphics that disappear.

What Happens When Your Resume Parses Badly

I want to be honest about this because the stakes are higher than most candidates realize.

When your resume parses badly, the recruiter sees a garbled version of your background. They do not see your beautiful original document. They see the parsed output. And here is the thing: recruiters review 50 to 100 resumes per day. They do not have time to download the original file for every candidate to check if the parsed version is accurate.

They make a judgment based on what they see. If what they see is a jumbled mess where they cannot quickly identify your current role, your years of experience, and your key skills, they move to the next candidate. Not because you are unqualified. Because the next candidate's resume actually communicated their qualifications.

I have flagged parsing issues to ATS vendors. I have submitted bug reports. I have tried to fix the problem from the employer side. The honest truth is that the technology is imperfect and improving slowly. In the meantime, the burden falls on candidates to format their resumes in a way that survives imperfect parsing.

It is not fair. But it is the reality. And the reality is manageable once you know the rules.

Use DOCX. Use a single column. Use standard headings. Keep contact information in the document body. Avoid graphics, text boxes, and tables. Test with a plain text conversion. Do these things, and your resume will survive every ATS I have ever encountered.

The content of your resume is what gets you hired. But the formatting is what makes sure the content gets seen.