By Peter Miller · Published August 18, 2026 · Last updated: October 4, 2026
7 min read
Your file looks sharp on a phone screen. You've used a template with sidebars, subtle color bands, and neat icon bullets. Then you upload to Greenhouse and the preview shows your skills block above your current job title. That's not bad luck. That's decorative formatting fighting the parser.
You don't have to ship an ugly document. You do have to know which design choices reorder text. If you're applying tonight, run a parse check before you blame keywords.
Check your resume for free on the version you're about to send. If sections scramble in plain text, decorative formatting hurts ATS on that portal even when the PDF looks fine to you.
Quick Wins
- Paste the export into Notepad and read dates top to bottom.
- Drop columns and tables; use one column only.
- Replace icon bullets with standard dashes.
When decorative formatting hurts ATS, what you see
The symptom is scrambled order, not a polite rejection email. Contact info lands in the skills field. A 2022 role appears after a 2024 role. A bullet you spent an hour on never shows in the recruiter preview because it sat inside a colored sidebar the parser skipped.
Recruiters rarely see your pretty PDF first in enterprise stacks. They see the parsed profile beside it. When those two views disagree, they trust the structured fields for search and filters. That is why a formatting fix beats another round of keyword stuffing on a broken layout.
Cause one: multi-column layouts. Parsers read left to right across the full page width. A sidebar column can be read before your main experience column, so a certificate line jumps above your manager title.
Cause two: tables used as spacing. Invisible table grids in Word or Canva look like clean alignment to you. The parser reads cell by cell and may attach a date in column two to a company name in column one.
Cause three: graphics replacing text. Skill bars, logos, and icon lists do not always export as words. The ATS stores an empty skills row while the human PDF still looks polished.
Cause four: font substitution on export. Custom fonts can swap characters when the portal re-renders your PDF. A bullet glyph becomes a square. A dash becomes a question mark. Stick to Calibri, Arial, or Helvetica at 10 to 12 points so the export matches what you typed.
How to tell which one hit you: open plain text. If the first lines are sidebar content, it's columns. If dates stick to random words mid-line, it's tables. If whole sections disappear, it's graphics or text boxes. If characters look broken, it's font or icon fonts.
Fix the parser without starting over
Font and bullet cleanup
Before: Wingding-style bullets and a display font for your name.
After: Standard hyphen bullets and a system font throughout. Export again and paste into Notepad to confirm bullets read as normal characters.
Columns and sidebars
Before: Contact block in a left rail, experience in a wide right column.
After: Stack everything in one column. Name, phone, email, city, then Experience, then Education, then Skills. Boring order is correct order for Workday imports.
Tables and text boxes
Before: Two-cell row with dates on the left and bullets on the right.
After: One line per role: Job Title, Company, Month Year to Month Year on the same line, bullets below as plain dashes.
Icons, color, and skill meters
Before: Five-star icon row labeled Advanced Excel.
After: A Skills section with the phrase Excel pivot tables and VLOOKUP in plain text, backed by one bullet that names a workbook you built.
Copy-paste block: plain-text sanity check
{`1. Export PDF or save DOCX
2. Select all, copy, paste into Notepad
3. Read first 20 lines: is your name and email at the top?
4. Scan dates: each job's dates sit next to that job title?
5. If not, remove columns/tables and repeat`}
For deeper layout rules, compare why tables break ATS parsing with your file open. Tables and decorative spacing share the same failure pattern.
Layout traps that look professional
I've opened plenty of Greenhouse previews where the PDF attachment looks hire-ready and the parsed profile is nonsense. Decorative formatting hurts ATS most when candidates trust the visual PDF and skip the text view.
Header and footer contact lines. Some portals ignore header regions. Put phone and email in the body under your name, not in a running header band.
Creative section titles. My Journey or Impact Portfolio are pretty labels. Use Experience, Education, and Skills so the mapper finds the right bucket.
Design-first exports for every role. Keep one plain master for ATS portals and save the designed PDF for email introductions when a human asked for it. See resume formatting rules US employers expect for the baseline hiring teams already know.
Mixing PDF and DOCX versions. Some candidates upload a designed PDF while the profile import reads an older Word file. Recruiters then see two different timelines. Keep one master and export from that file every time.
Test the file, not the template preview
After you flatten layout, run the export through the free ATS resume checker so you see missing sections before a recruiter does. Fix structure once on the master, then tailor content per posting.
If you're rebuilding from a scrambled Canva file tonight, start in the free resume builder with single-column defaults so you're not fighting hidden tables at midnight.
Plain structure is the design
Why decorative formatting hurts ATS comes down to read order. Parsers are literal. Columns, tables, and icons change that order. Flatten the file, paste into Notepad, and only then tune keywords for the role you want tonight.
When the plain-text view matches what you meant, you're ready to tailor bullets. Decorative formatting hurts ATS less once the skeleton is linear. Then you can spend your evening on posting keywords instead of layout rescue.
Pair the fixed resume with a short letter from the cover letter generator so the application packet reads consistent in Greenhouse or Lever.
Frequently asked questions
Standard bold on job titles and section headers is usually fine. Problems start when bold sits inside tables, text boxes, or multi-column bands where the parser cannot tell a heading from body text. Keep bold on plain lines in a single column.
Treat icons and percentage bars as decorative. Many parsers skip them or read the icon font as garbage characters. Spell the skill in plain text on its own line instead of a graphic meter.
A clean look on screen does not guarantee clean text extraction. Design exports often hide columns and ordering layers. Copy the PDF text into Notepad. If dates and employers jump around, rebuild as a plain Word or PDF export from a single-column doc.
You do not need a gray-only file. Keep body text black on white. If you use accent color, limit it to your name line and do not put keywords only in colored type. The parser may drop colored runs entirely.