12 min read
Your resume looks clean in Word. You upload it, and the portal preview doesn't match what you wrote. Your skills block sits under a job you left four years ago. You're not imagining it. The parser read your file in the wrong order, and none of the polish on screen mattered once the upload finished.
Most rejections that feel like keyword problems are layout problems wearing a keyword mask. You didn't miss the role. You broke a resume formatting rule that doesn't show up until Workday or Greenhouse imports the file. Job searching is already draining. Watching a qualified file die on a table border makes it worse, and it's fixable in one evening if you know which rule you broke.
Before you rewrite bullets, check your resume for free and confirm your contact line and section order survived the import. That pass takes less time than tailoring another posting you'll never reach a human on.
This page walks the symptom you'll recognize, three causes that scramble parsing, how to tell which one is yours, and the fix for each without buying a new template every week.
Quick Wins
- Copy-paste your file into Notepad. If the order is wrong, fix layout before keywords.
- Move contact info out of headers and into the body text at the top.
- Search your PDF for your phone number. No match means the file is an image, not text.
The symptom: polished file, scrambled import
You open the application preview after upload. Your name parses. Your email is blank. Your most recent job title landed under Education. You still hit submit because the PDF on your screen looks fine. Two weeks later, silence. The symptom isn't missing experience. It's a file the system couldn't read in the order you intended.
Parsers do not see your design. They strip text and guess structure from position on the page. A sidebar of skills read before your summary pushes keywords into the wrong bucket. A borderless table that aligns dates on screen becomes a single mashed line in plain text. I've screened stacks of these in Workday and Greenhouse, and the file that wins is boring and specific: one column, standard headings, contact in the body.
Candidates blame the ATS score or the keyword list first. Fair. But when the preview already scrambled your sections, no amount of skill stuffing fixes the import. You need to know which layout rule failed before you touch wording.
The feeling is specific: you meet the posting on paper, you tailor carefully, and you still never get a screen. When friends with similar backgrounds advance, you assume it's networking or luck. Sometimes it's a two-column Canva export nobody warned you about.
Creative templates from university career centers and free design sites are the usual source. They look modern on a laptop. They fall apart the moment a parser reads column two before column one finishes.
Senior candidates hit the same wall with executive layouts: logos in margins, charts for skill ratings, contact blocks in colored bands. Recruiters never see the color. They see missing phone numbers and jobs listed backward.
When resume formatting rules get ignored, parsers guess wrong
Cause 1: Columns and tables reorder your history
Symptom: skills appear above your summary, or job bullets from 2019 sit between 2024 roles. The parser read across columns or through invisible table cells instead of top to bottom.
Before: marketing resume with a left sidebar listing HubSpot, Salesforce, and Google Analytics beside a main column of campaign bullets. Plain-text paste shows all skills first, then a wall of jobs out of order.
After: single-column layout. Skills section after Experience. First bullet under current role: "Ran paid search across Google and Meta, lifting demo requests 18% in Q2 while cutting CPL 12%."
Fix: delete columns and borderless tables. Stack sections vertically. Use tab stops or line breaks for dates, not table cells. Open Word, turn on gridlines, and rebuild anything that shows a grid.
Cause 2: Headers, footers, and text boxes hide contact info
Symptom: preview shows your name but no email or phone. Recruiters cannot reply even if they want to. Some systems skip header and footer regions on import entirely.
Before: software engineer resume with phone and LinkedIn URL in a footer on every page. Workday import leaves contact fields empty while job history parses.
After: contact block as the first lines of body text: full name, city and state, phone, email, one link if needed. Footer removed. Bullet one under current role names the stack from the posting in the first eight words.
Fix: repeat contact details in the document body. Avoid text boxes and floating shapes. If the portal preview drops a field, move that line out of any special region and upload again.
Cause 3: Image PDFs and design exports are not text
Symptom: you cannot highlight text in the PDF, or search for your phone number returns zero results. The file is a picture. Parsers extract nothing useful.
Before: nurse resume exported from a design app as a flattened PDF. Epic documentation skills sit inside a graphic badge the parser skips.
After: DOCX with 11-point Calibri, single column. Line reads "Registered Nurse, Med-Surg" above employer. Bullet: "Documented care in Epic on 32-bed unit; precepted four orientees on fall-prevention workflows."
Fix: save as DOCX from Word or export a text-based PDF. Run the highlight test and the phone-number search before you apply. Read how resume file type impacts screening when the posting forces a specific format.
How to tell which cause is yours
Run three checks in order. First, select all text and paste into Notepad. If reading order is wrong, you have a column or table problem. Second, open the portal preview after upload. If contact fields are blank, move details out of headers and text boxes. Third, search the PDF for your phone number. If search fails, you have an image file, not a resume the ATS can score.
Only one cause usually dominates. Fix that one completely before you tweak fonts or margins. Mixing partial fixes leaves the preview half broken.
Fix for cause 1: rebuild as a single column
Strip the template to bare sections: contact, summary if you use one, experience, education, skills, certifications. No sidebars. No skill bars. No icons replacing words.
Copy-paste header block for every role:
Job Title | Employer Name | City, ST
Month Year to Month Year
• First eight words name the top skill from the posting, then proof with a metric.
Paste that skeleton under each job before you argue about design. Consistent headings beat clever layout every time in Greenhouse and Lever imports.
Fix for cause 2: body contact, standard section names
Put name, city, phone, and email as normal paragraphs. Use Experience, Education, and Skills as section headers. Creative titles like Career Highlights may not map to a filter recruiters use.
Month Year dates on one line with the employer. Mixed formats (Jan 2020 here, 01/2020 there) confuse timeline parsing and create fake gap flags on a fast skim.
Fix for cause 3: export settings that keep text selectable
From Word, Save As PDF with standard options, not Print to PDF. From Google Docs, Download as PDF after confirming you can copy a bullet. Scanned paper resumes fail every time unless the posting explicitly allows them.
Read DOCX export settings that improve US ATS parsing when Word keeps embedding hidden styles that break on upload.
Edge case: academic CV length on corporate portals
A four-page CV with publications in multi-column journal format may parse fine for a university system and fail on a corporate Workday req. For corporate roles, ship a two-page single-column version with publications condensed to a short list. Keep the long CV for grants, not for a product manager posting.
Edge case: contractor roles with stacked clients
Listing five clients in a nested table under one consultancy title often parses as one employer with garbled bullets. Flatten: one block per client with dates, or one consultancy header with bullets that name the client in the first five words.
What a clean import looks like in preview
Name and email populate. Most recent job sits on top. Skills land in a skills field or directly under the roles where you used them. Dates read left to right in order. That file is ready for keyword tailoring. Everything else is still a layout repair job.
Save a screenshot of a good preview next to your export. When a new template tempts you, compare before you switch. Boring imports beat pretty PDFs that never reach a recruiter inbox.
Where these layouts go wrong on US resumes
Skill rating bars and star icons. Parsers cannot read a filled circle as expert level. Recruiters distrust them even when they display.
Putting must-have keywords only in a sidebar. When the sidebar parses first, keywords detach from the jobs that prove them.
Using photos and logos. They add file weight, break parsing on some systems, and create bias risk recruiters avoid.
Mixing fonts and sizes for emphasis. Consistent 10.5 to 12 point Calibri or Arial reads clean in import and on paper.
Relying on page two for contact details. If page one is all summary and page two starts experience, some imports never attach page two contact back to the profile.
Submitting the design PDF and the Word file interchangeably. They are not the same file. Test the one you will actually upload.
Ignoring the preview because the score looked fine. A keyword score on scrambled text is noise. Fix order first.
Read why weak bullet points get ignored after layout is clean and you still need stronger proof lines under each role.
Test the import before the next application
Upload your file to HireFlow's free ATS resume checker and confirm section order and contact fields before you spend an hour tailoring bullets that will not parse.
If you are rebuilding from a broken template, build your resume in a single-column structure so you are not fighting hidden tables from an old download.
When the posting asks for a cover letter and your resume required a full layout rebuild, draft a short note with the cover letter generator after the resume preview looks correct. Formatting fixes come first. Cover letters second.
Run the layout pass tonight
Resume formatting rules are not about looking plain for sport. They keep your work history in the order you wrote it so recruiters can score the right bullets. When the preview scrambles, keywords cannot save you.
Pick the file you send most often. Paste into Notepad. Fix columns and tables if order fails. Move contact into the body if preview fields are blank. Re-export if search cannot find your phone number. Then tailor once and submit.
Keep one master DOCX and one tested PDF derived from that master, not from separate design tools. Name the folder with the date you last confirmed a clean preview. Future-you will not remember which export passed Lever last month.
Ask a friend to run the same three checks on your file. Fresh eyes catch sidebars you stopped seeing. If their paste order fails, yours fails too, no matter how long you stared at the template.
When a new job board asks for a different format, test that format once before you batch apply. A DOCX that parsed in Greenhouse may need a text PDF for an older Taleo req. One test upload beats ten silent rejections.
- Single column, standard headings, body contact line.
- Notepad paste reads top to bottom in the right order.
- Portal preview shows email and most recent job on top.
Run the free resume check after the layout pass, then apply with the file that already survived import. You did the work. The rules above make sure a machine reads it in the order you intended.
Read more
Frequently asked questions
Using a two-column layout. Parsers read left to right in a straight line. When columns force them to guess, skills from a sidebar attach to the wrong job and your work history arrives jumbled. Single column is boring and it wins.
No. Many ATS platforms skip header and footer regions entirely. Your contact line can look perfect on the PDF while the imported profile shows a blank email field. Repeat name, phone, email, and city as normal body text at the top.
DOCX is the safer default when the posting does not specify a format. A clean Word file with standard fonts parses reliably in older enterprise systems. PDF works when the text is genuinely selectable, not when the file is a flattened image export from a design tool.
Yes, when they replace standard labels. Experience, Education, and Skills map to known fields. Creative headers like My Journey or Where I Have Been may land in a generic text block recruiters never filter on.
