ATS-Friendly Resume Format: The Rules That Actually Get You Past Screening

Your resume looks great. You spent hours on it. The spacing is tight, the layout is clean, and you even matched your accent color to the company's brand palette. And it's getting zero callbacks.

Here's the painful irony: the more design work you put into a resume, the worse it performs with the software that screens it first. That polished two-column layout with your headshot and LinkedIn QR code? An Applicant Tracking System sees that as a garbled mess of misaligned text, or nothing at all. The resume that gets you through automated screening looks nothing like the resume you see on Pinterest or in "best resume templates" roundups.

Most job seekers are failing a test they don't know they're taking.

TLDR

ATS software cannot read columns, graphics, text boxes, tables, or headers/footers — they either skip that content or scramble it
Use a single-column layout, standard section headings, and 10–12pt serif or sans-serif fonts
DOCX is the safest file format for most ATS; PDF works on modern systems but fails on older ones
Section headings must use standard labels: "Work Experience," "Education," "Skills" — not creative alternatives
Your contact info must be in the body of the document, not in the header or footer
Test your resume before you apply — paste it into a plain text editor and see what survives

Why Resume Design Hurts More Than It Helps

ATS software doesn't see your resume the way a human does. It reads the underlying text layer and tries to map it to structured fields: name, contact info, job titles, dates, employers, skills. When you add visual complexity, you're not impressing a hiring manager — you're confusing a parser.

Here's what actually happens with common design choices:

Two-column layouts are one of the most common resume formats sold as "modern" and "professional." They are also one of the most reliable ways to get your resume scrambled. Systems like Workday, Greenhouse, and iCIMS parse resumes left-to-right, line by line. A two-column layout causes the parser to interleave content from both columns into a single stream of text. Your job title from the left column ends up next to a skill from the right column. The result is incoherent to the system and your data gets filed incorrectly or ignored.

Text boxes are a popular way to make callouts or highlight key accomplishments. ATS software typically skips them entirely. The content inside a text box is not part of the document's main text layer in Word or most PDF formats — it lives in a separate object. Taleo, one of the most widely used enterprise ATS platforms, is particularly bad at extracting content from text boxes. Whatever you put in one is likely invisible.

Tables have the same problem. Resumes that use tables to organize skills or create a structured layout lose that content when the parser flattens the document. What looks like a clean grid becomes either garbled text or blank fields.

Headers and footers in Word documents and PDFs are technically separate from the body content. Many ATS systems — including older versions of Taleo and SAP SuccessFactors — either skip header and footer regions entirely or extract them inconsistently. If your name and phone number are in the document header (a common design pattern), some systems will not see them.

Graphics, icons, and photos are completely invisible to ATS. The system sees an image object and moves on. Any text embedded in an image is lost. Any icon used to represent a skill or contact method is ignored. This matters because many resume templates use small icons next to phone numbers, email addresses, and LinkedIn URLs — which means the labels for that contact information may be missing in the parsed output.

Infographic resumes — the kind with skill bars, timelines, and visual charts — are essentially unreadable to ATS. They look impressive to humans, and they are useless to the software that decides whether a human ever sees them.

The ATS-Safe File Formats

The PDF vs. DOCX debate has a real answer, and it depends on the system.

DOCX is the safest universal choice. Modern ATS platforms — Workday, Greenhouse, Lever, iCIMS — all handle DOCX reliably. The format has a well-structured XML layer that parsers can navigate cleanly. If you don't know what ATS a company uses, submit DOCX.

PDF is acceptable on modern systems but risky on older ones. Greenhouse and Lever handle PDFs well because they use updated parsing engines. Taleo, particularly older enterprise deployments, has historically had poor PDF parsing — especially for text-heavy PDFs or those generated by design tools like Canva or Adobe InDesign rather than Word or Google Docs. PDFs created by design software often embed text as outlines (essentially as shapes) rather than actual characters, which makes them completely unparseable.

Never submit a resume as an image file — JPG, PNG, or a PDF that's actually a scanned image. There is no text layer. The ATS sees nothing.

If a job posting specifically requests a format, follow it exactly. If the system accepts both, default to DOCX.

Font and Spacing Rules That ATS Can Parse

ATS software can technically read most fonts, but the safest choices are common system fonts that parse cleanly and render consistently across environments.

Stick to these fonts: Calibri, Arial, Garamond, Georgia, Times New Roman, Cambria, Helvetica. These are universally available and parse without issues.

Font size: Body text should be 10–12pt. Section headings should be 12–14pt. Going smaller than 10pt doesn't save you space in any meaningful way — it just makes the content harder for both ATS and humans to read.

Avoid decorative or uncommon fonts. Script fonts, thin-weight display fonts, and anything that needs to be embedded in the PDF rather than accessed from the system font library can cause parsing issues or character substitution.

Spacing: Single or 1.15 line spacing works well. Margins between 0.5" and 1" on all sides are standard. Don't compress margins below 0.5" to fit more content — it's a signal to human reviewers that you're padding, and it doesn't help ATS parsing.

Bold and italics for emphasis are fine — they're part of standard text formatting and parse correctly. Underlines work too but are visually noisy. Avoid using color as the sole differentiator for any text that needs to be read by ATS.

Section Headings ATS Actually Recognize

ATS systems are trained to look for specific section labels. They use these labels to categorize the content beneath them. If you use non-standard headings, the system may miscategorize your experience or fail to find it at all.

Use these exact headings (or close variations):

Work Experience / Professional Experience / Experience
Education
Skills / Technical Skills / Core Competencies
Certifications / Licenses
Summary / Professional Summary / Profile
Projects (acceptable as a secondary section)
Volunteer Experience / Volunteer Work

Do not use these headings:

"My Journey" — Greenhouse will not map this to an Experience field
"What I Bring to the Table" — this content will likely be ignored or miscategorized
"Areas of Expertise" — borderline; some systems recognize it, many don't
"Things I've Built" — unparseable
"Education & Beyond" — the "& Beyond" part breaks pattern matching on most systems

The rule is simple: if it doesn't sound like a standard HR category, don't use it. Creative section naming is for portfolios and personal websites, not ATS-screened applications.

What to Never Put in a Resume If You Want ATS to Read It

This is the complete list of resume elements that either confuse or are invisible to ATS:

Columns — cause left-to-right parsing errors in Workday, Greenhouse, and iCIMS
Text boxes — content is skipped by Taleo and most other enterprise systems
Tables — parsed inconsistently; content often lost or scrambled
Headers and footers — skipped by older Taleo and SAP SuccessFactors deployments; never put contact info here
Graphics, logos, and icons — completely invisible; any text label attached to an icon may be lost
Photos — invisible to ATS; a liability in US hiring contexts for EEO reasons
QR codes — invisible to ATS; no human reviewer is scanning your resume's QR code
Infographic elements — skill bars, timeline graphics, pie charts — all invisible
Watermarks — can interfere with text layer parsing
Fancy bullets — decorative bullet characters (arrows, checkmarks, custom glyphs) sometimes parse as garbled characters; use standard round bullets or hyphens
Colored backgrounds or shaded sections — not readable by ATS; some systems strip formatting and lose text that was color-matched to a background

The Correct Resume Section Order for ATS

ATS systems expect content in a rough top-to-bottom hierarchy. Deviating significantly from this order doesn't necessarily break parsing, but it does affect how well your key qualifications surface in the parsed output.

Standard ATS-optimized order:

Contact Information (name, phone, email, LinkedIn URL, city/state — no full street address)
Professional Summary (2–4 sentences; keyword-dense but readable)
Skills (especially for technical roles; ATS skill-matching algorithms pull from this section heavily)
Work Experience (reverse chronological; each role has company name, title, dates, bullet points)
Education (degree, institution, graduation year)
Certifications (if applicable)
Projects or Volunteer Experience (if relevant and space allows)

For early-career candidates or recent graduates, Education can move above Work Experience. For everyone else, keep Experience as the dominant section and place it before Education.

A Sample ATS-Optimized Resume Structure

Here's what a properly formatted ATS resume looks like in plain terms — not a visual template, but the actual content structure that parses cleanly.

JANE DOE jane.doe@email.com | (555) 123-4567 | linkedin.com/in/janedoe | Austin, TX PROFESSIONAL SUMMARY Results-driven marketing manager with 7 years of experience in B2B SaaS. Specializes in demand generation, content strategy, and marketing automation (HubSpot, Marketo). Proven track record of pipeline growth and cross-functional collaboration. SKILLS Demand Generation | Content Marketing | HubSpot | Marketo | Salesforce | SEO/SEM | Google Analytics | A/B Testing | Campaign Management | Budget Planning WORK EXPERIENCE Senior Marketing Manager Acme Corp — Austin, TX March 2021 – Present Led demand generation programs that increased MQL volume by 40% YoY Managed $1.2M annual marketing budget across paid, content, and events Built and scaled email nurture sequences using Marketo, achieving 28% open rates Marketing Manager Beta Solutions — Remote June 2018 – February 2021 Owned content marketing strategy; grew organic traffic 65% in 18 months Coordinated with sales on ABM campaigns targeting Fortune 500 accounts Launched company podcast; reached 10,000 subscribers within first year EDUCATION Bachelor of Science, Marketing University of Texas at Austin Graduated: May 2018

CERTIFICATIONS HubSpot Marketing Hub Certified | Google Analytics Certified

Notice what this resume does not have: columns, design elements, icons, a photo, creative section names, or anything that requires visual rendering to make sense. It is optimized for machines first, humans second — but it still communicates clearly to both.

Testing Your Resume Against ATS Before You Apply

Before you submit to any job, run a basic ATS simulation yourself. It takes five minutes and reveals problems immediately.

The plain text test: Copy the entire text of your resume and paste it into Notepad (Windows) or TextEdit in plain text mode (Mac). What you see is roughly what an ATS parser sees. If your contact info is missing, your columns are interleaved, or sections are scrambled — that's what the ATS is working with.

Dedicated ATS testing tools: Platforms like Jobscan, Resume Worded, and ResumeRabbit allow you to test your resume against a specific job description and see how well the keywords align and how cleanly it parses.

Check the parsed output directly: Some ATS platforms (Greenhouse, in particular) show candidates a parsed preview of their application before they submit. If you see scrambled or missing information in that preview, the system couldn't read your file correctly. Go back, fix the formatting issue, and resubmit.

Match keywords to the job description: Parsing is only half the problem. After your resume is parsed, it's scored against the job description for keyword relevance. If your resume doesn't include the exact language from the posting — "project management" vs. "program management," "JavaScript" vs. "JS" — you may score lower than a less experienced candidate who mirrored the language more precisely.