We’ve seen great candidates get rejected for dumb reasons. Not because they lacked skills. Not because they were unqualified. But because their resume looked “nice” instead of readable.
Here’s the uncomfortable truth: ATS software doesn’t care about design. It cares about structure. And if your formatting confuses the parser, your resume never reaches a human.
Let’s kill some myths and talk about what actually works.
What ATS actually is (and isn’t)
An ATS isn’t a sentient gatekeeper judging your worth.
It’s closer to a filing system that:
- Extracts text
- Assigns it to fields (job title, company, dates, skills)
- Ranks candidates based on keyword match and basic rules
When people say “the ATS rejected me,” what usually happened is:
- The system couldn’t read the resume correctly
- Or it read it fine, but the content didn’t match the role
Formatting affects the first problem only. But that alone wipes out a lot of otherwise solid candidates.
For a deeper dive into how these systems work, see How ATS Systems Actually Work.
Myth: “ATS-friendly means ugly”
Wrong.
ATS-friendly means predictable.
You can still have:
- Clean spacing
- Consistent typography
- A professional look
You just can’t get cute with layout.
Do this: Single-column layout with clear section headers.
Not that: Two columns, sidebars, text boxes, or “designer” layouts that look like a startup homepage.
If the text doesn’t flow top-to-bottom, left-to-right, many ATS systems misread it.
One column. The safest default.
This is the safest default for 2026.
Two-column resumes break parsing because:
- ATS may read across rows instead of down
- Dates and titles get scrambled
- Skills land in the wrong fields
Modern ATS platforms like Greenhouse and Lever handle two-column layouts better than they used to, but single-column remains the safest choice — especially when you don’t know which system you’re up against.
We’ve seen resumes where:
- Job titles turned into bullet points
- Company names disappeared
- Dates attached to the wrong role
And yes, those candidates were rejected automatically.
Fonts: boring wins
ATS systems don’t hate fonts. They hate unusual fonts.
Stick to:
- Arial
- Calibri
- Helvetica
- Times New Roman
- Georgia
Font size:
- Body: 10.5–12 pt
- Headers: 13–16 pt
Smaller risks parsing errors. Bigger looks padded.
Headers: stop being clever
ATS looks for expected section names.
Use:
- Work Experience
- Professional Experience
- Education
- Skills
Avoid:
- “My Journey”
- “What I’ve Done”
- “How I Add Value”
If the system can’t confidently map a section, it may ignore it.
Skills sections: structure beats creativity
Do this:
Skills
- Product management
- SQL
- Agile methodologies
- Stakeholder communication
Not that:
Product Strategy | Roadmaps | Execution | Leadership
Bullets win. Pipes can cause issues with some parsers. Bullets are the safest choice.
For help identifying which skills to include, see Keywords That Matter: ATS Optimization.
Dates: consistency > cleverness
Pick one format and stick to it:
- Jan 2021 – Mar 2024
- 01/2021 – 03/2024
Don’t hide dates. ATS flags gaps anyway, and humans read avoidance as a red flag.
PDF vs Word: the real rule
- Posting says PDF → upload PDF
- Posting says Word → upload Word
- No guidance → PDF is usually fine
Problems happen when PDFs come from design tools or flatten text.
Icons, charts, visuals: don’t
ATS can’t read them.
That means:
- Skill icons = invisible skills
- Charts = ignored content
- Logos = wasted space
Plain text wins every time.
File names matter
Recruiters see them.
Do this: FirstName_LastName_Resume.pdf
Not that: Resume_Final_REAL_THIS_ONE_v9.pdf
For more formatting pitfalls, check out Common ATS Mistakes to Avoid.
The quiet truth
ATS-friendly formatting:
- Prevents accidental rejection
- Gets your resume parsed correctly
It does not fix weak content.
Clear the machine first. Then let a human decide.
Not sure if your formatting is ATS-safe? Upload your resume to Resumes Coach and see exactly how it parses — with specific formatting fixes highlighted.