By Peter Miller · Published March 24, 2026 · Last updated: October 4, 2026
7 min read
Pretty templates sell peace of mind. Parsers do not care about peace of mind. They care whether experience landed as continuous lines with dates attached.
You've probably already tailored keywords for a role that went quiet. If the preview pane looked empty or scrambled, the issue wasn't fit. It was export.
If your last upload looked blank in the preview pane, don't blame the req yet. Check your resume for free and read what imported before you rewrite bullets for the third time.
Use the grouped checklists below on the file you're about to submit. Each group matches a failure mode recruiters still see in Workday imports every week. You won't need a design degree, just a boring layout that survives paste. It's not glamorous, but it's faster than another week of silence.
Quick Wins
- Switch to one main column for experience and education.
- Paste the PDF into Notepad; if order scrambles, fix layout before keywords.
- Type contact lines in the body, not the Word header region.
Why formatting beats keywords on the first pass
Parsing happens before matching. If the experience block imports as one blob, keyword rules have nothing clean to attach to.
Greenhouse, Lever, Taleo, and iCIMS each handle messy files differently, but the pattern is the same: broken structure creates fake gaps, merged employers, and missing titles.
Humans suffer too. A recruiter opening a garbled profile trusts the data less, even when your story is strong on paper.
Keyword stuffing cannot fix a file where job three imported before job one. Match rules need anchors. Formatting supplies those anchors.
Think of ATS resume formatting mistakes as silent: you will not always get an error message. You get a thin profile and a fast rejection you cannot explain.
For contact-specific traps, see resume contact information for ATS . This page focuses on layout and export choices.
Pre-upload ATS resume formatting checklist
Work top to bottom. Do not tick keywords until structure passes.
Layout and columns
- One main column holds experience, education, and skills in that order.
- No sidebar that splits dates from employer names.
- Section headings are plain text lines, not icons-only labels.
- Margins wide enough that lines do not wrap mid-word on export.
Tables and text boxes
- Experience is not stored inside invisible table cells.
- Bullets use real bullet characters or hyphens, not manual spacing columns.
- Text boxes for summaries are removed; summary sits in normal paragraphs.
- Skill grids are a single list or comma line, not a crossword of cells.
Fonts, lines, and graphics
- Body font is a standard sans or serif at 10 to 12 pt, consistent throughout.
- Horizontal rules between jobs are removed or replaced with blank line spacing.
- No background shading behind experience blocks.
- Charts and skill meters are deleted; describe level in words if needed.
File type and export
- PDF is exported from Word or Docs, not flattened from Canva unless tested.
- File is selectable text, not a scan or photo.
- Hyperlinks use full https strings if you include a portfolio URL.
- File name is simple: Firstname-Lastname-Resume.pdf.
Dates and section labels
- Section titles are standard: Experience, Education, Skills, not cute icons.
- Month Year dates sit on the same line as employer or directly under title.
- Present is spelled out, not a symbol or graphic.
- No footer repeating contact info parsers may skip.
I've opened Lever previews where a two-column template stapled skills between job titles, and the candidate looked unemployed for a year they were not.
Copy-paste: plain-text sanity check
1. Save PDF → Select All → Copy
2. Paste into Notepad
3. Confirm: name, contact, Experience, jobs newest-first, dates beside titles
4. If skills interrupt a job block, rebuild that section in one column
Before: Skills column sits left; jobs run down the right with dates orphaned on the margin.
After: Skills line sits under experience as a comma list; each job line reads Company · Title · Jan 2022 to Mar 2024.
Before: Experience lives inside a Word table with hidden borders.
After: Same jobs as plain paragraphs with bold company names and normal bullets.
ATS resume formatting mistakes in the portal preview
| What you see after upload | Likely formatting cause |
|---|---|
| Jobs out of order | Columns or tables read sideways |
| Missing employer names | Graphics or icons replaced text |
| Skills merged into bullets | Sidebar dumped into body stream |
| Blank experience section | Scanned PDF or broken export |
Pair this table with how resume file type impacts screening when you are choosing PDF versus DOCX for a picky portal.
Fixes that look worse before they parse better
Stripping color feels bland. Parsers prefer bland. Save the designed version for networking PDFs if you want, not for ATS upload.
Deleting icons makes the header plain. Plain is the goal. Recruiters need your email as text they can click.
Shortening a pretty one-pager into two pages of text is fine when the second page is still one column and readable.
Job searching is hard enough without fighting your own template. Pick the plain version for applications and keep the designed PDF for humans who ask over email.
Confirm the parser view before you tailor
Upload the same file you will send to the employer. Scroll the imported experience block line by line.
Score your job match after structure passes so you are not tuning keywords on top of a broken timeline.
Formatting will not fix applying to roles you cannot do. It stops qualified files from dying because the machine read the layout wrong.
Structure is the first filter
ATS resume formatting mistakes hide in templates that never get paste-tested. Run the checklist, rebuild in one column, and only then fight for keyword fit.
When you attach the fixed file to a note, keep dates aligned using the cover letter generator so nothing contradicts what the parser imported.
Frequently asked questions
Not always, but they fail often enough that a single main column is the safer default. Parsers read left to right and can merge sidebar skills into experience or drop dates that sit in narrow cells. If you love a template, run a plain-text paste test before you rely on it.
DOCX usually preserves heading structure when the file is simple. PDF is fine when it is a clean export from Word or Google Docs without text boxes. Scanned PDFs and design-tool exports are the usual troublemakers because text is not selectable.
Yes when they replace typed contact lines. Parsers read strings, not phone icons. Put email and phone as plain text under your name in the body. One small logo rarely breaks a file, but a header built from shapes often does.
You can upload a corrected file if the portal allows replacements. Some systems lock the first parse. Save a fixed version anyway for the next req and for recruiter email attachments so humans see the clean layout.