By Peter Miller · Published August 10, 2026 · Last updated: September 15, 2026
12 min read · You don't need a new template tonight
Your PDF shows three employers, clear dates, and a Skills block. Workday shows one paragraph and the wrong company on bullet two. That's not a hidden keyword penalty. It's export structure, and it won't fix itself when you add keywords. Corporate teams on Workday, Greenhouse, Lever, Taleo, and iCIMS all import your file into a text profile before a human opens it. When you park Month Year dates in a table cell or hide your phone in a footer, the parser flattens blocks you spent an hour polishing.
Before you swap fonts or add more Skills rows, check your resume for free with the posting pasted in. Paste your export into Notepad first. If employer names and dates merged into one string, structure broke upstream. You won't rescue that upload by stuffing terms into a footer row.
You've probably seen generic lists: use Arial, avoid graphics, save as PDF. Fine advice, useless when bullet three never imported as its own line. Job searching through portals is already slow, especially when you're qualified and still hear nothing back. This diagnostic walks symptom to cause to fix. You don't need a template swap tonight.
And it is not only entry-level applicants. A mid-level analyst with six years of reporting work can miss the screen because bullet one still reads responsible for weekly reports while the posting asked for SQL and Looker. The years are real. The parsed view just never attached them to the right employer block.
If the portal asks for a cover letter, don't paste your Skills block into paragraph one. Generate a cover letter that names the same tools you put on bullet one, then stop rewriting.
Do these three things first
- Paste your export into Notepad before you apply. Merged lines mean layout broke.
- Move Month Year dates onto the same line as job title and company. No sidebar cells.
- Put phone and email on row one of the body. Headers and footers often drop on import.
When your PDF looks fine but the recruiter view does not
The symptom is quiet. Portal status stays submitted. No rejection email. You open the file on your screen and everything looks clean. So you assume the problem is volume or bad luck.
Parsing failures often show up before a human ever reads bullet one.
Workday and Greenhouse attach your upload to a candidate profile recruiters skim inside the platform. They see parsed text alongside or instead of your PDF. For operations, finance, and tech roles at mid level, the first ctrl-f is often the core tool, then tenure, then scope in bullet one. When import flattens structure, those fields disappear or attach to the wrong employer line.
A composite marketing coordinator whose PDF shows dates in a right-column cell but Greenhouse imports one jumbled block loses to the same facts on plain single-column lines. Same qualifications. Different skim surface for the coordinator forwarding to a hiring manager.
For how parsers treat Skills differently from employer bullets, see how ATS interprets skills vs tools vs technologies . The short version: tags are not proof. Formatting still has to deliver those tags on dated lines.
Resume Formatting Checklist That Prevents Parsing Errors: four causes
Checklist posts fail when they list twelve font rules. You need one decision: which layer broke your file. Work through the four causes below in order. Stop when you find a clear miss.
Cause 1: Two-column layouts and invisible tables scramble employer blocks
This is the most common break on resumes built from Canva or Word templates with a sidebar. Job title and company sit in column one. Month Year dates sit in a right-column table cell. Workday reads top to bottom inside the file, not left to right across your design.
Before: Two-column template. Left column: Operations Analyst, Northwind Retail Group, Chicago. Right column table cell: Jan 2022 to Present. Bullets below in a shaded text box.
After: Single-column plain block:
Operations Analyst | Northwind Retail Group | Chicago | Jan 2022 to Present
Built weekly inventory dashboards in Looker; cut stockout tickets 14% in Q2 2025.
I've screened Greenhouse stacks where a coordinator's budget bullets buried inside a skills table imported after job two, so the parser attached forecast work to a six-month contract from 2021. The recruiter never reached the scope because the parsed view looked like job hopping without proof up top.
Edge case: you used a Word table without visible borders. Parsers still read the cell grid. Convert to plain lines with pipe separators or commas on one row, then delete the table entirely.
Cause 2: Headers, footers, and text boxes drop contact lines and bullets
Cause two looks like cause one but the body is already single-column. Your phone, email, and LinkedIn URL live in a header zone. Bullet blocks sit inside text boxes for visual spacing. Greenhouse and Lever often strip those zones on import.
Before: Contact details in a Word header. Three experience bullets inside a floating text box under each role.
After: Row one of the body: Jane Doe | Phone: 312-555-0142 | Email: [email protected] | linkedin.com/in/janedoe
Plain bullets with standard round markers directly under each employer line.
Edge case: icons or emoji beside email and phone. Parsers read them as blank characters. Write Phone: and Email: as plain labels. No glyphs.
Cause 3: Wrong file type or image PDF hides text from the parser
Cause three looks like a upload problem but the fix is export settings. You saved a designed PDF from a portfolio site or scanned a printout. The file displays fine on screen. The parser sees a picture, not selectable text.
Before: Canva PDF with invisible tables and gradient backgrounds. Text looks crisp but does not highlight when you click and drag.
After: DOCX exported from Word with standard Heading 1 for employer names. Text highlights cleanly. If PDF is required, export from Word after you strip tables, then confirm highlight works.
Try DOCX first when the portal allows it. Word files with normal styles usually keep employer blocks separated better than designed PDFs. When only PDF is accepted, paste the export into Notepad anyway. If nothing appears, you are still in Cause 3.
Cause 4: Creative section headers skip whole experience blocks
Cause four looks like a wording choice but the parser treats labels as anchors. You renamed Experience to Where I Delivered Results. Education became Learning Path. The ATS never flags those strings, so employer blocks import as undifferentiated body text.
Before: Section title: My Professional Story. Bullets follow with no Experience label.
After: Standard header: Experience. Employer line with Month Year dates, then bullets. Keep Education and Skills as separate conventional headers too.
Edge case: combined header like Experience and Projects in one section. Split them. Parsers map one label to one block. Mixed headers bury project proof under employment or drop it entirely.
How to tell which cause is yours
- Layout check: Paste your export into Notepad. If employer names and Month Year digits merged into one string, you are in Cause 1.
- Contact check: Search the Notepad paste for your phone digits. If they are missing, you are in Cause 2.
- Highlight check: Open the PDF and try to select a bullet with your cursor. If text will not highlight, you are in Cause 3.
- Header check: ctrl-f Experience in the Notepad paste. If zero hits while bullets exist, you are in Cause 4.
Read how to tell if your resume is ATS friendly in 60 seconds when you want a faster layout pass before you open Word again.
Copy-paste employer block (edit every bracket)
[Full Name] | Phone: [digits] | Email: [address] | linkedin.com/in/[handle]
Experience
[Job Title] | [Company] | [City, ST] | [Mon Year] to Present
• [Verb] [tool or scope] for [object]; [metric] in [timeframe]
• [Second bullet only if it supports the same scope]
• [Third bullet optional; do not bury the must-have here]
Skills (short; each tool above must appear on a bullet):
[capability] · [capability] · [tool already on bullet one]
Copy-paste this block, then replace every bracket with your real dates and scope.
Habits that put the next apply back in the maybe pile
Even after you fix the cause that blocked you, these habits put the next apply back in the maybe pile.
Mixed date formats on the same file. One role uses Jan 2022 to Present. The next uses 01/2022 to 12/2023. A contract row says Q3 2021. Parsers cannot anchor tenure when the pattern shifts mid-file. Pick Month Year everywhere.
Creative job titles like Data Wizard instead of Data Analyst. Recruiters ctrl-f for standard titles. Parsers keyword-match the same strings.
Fancy Unicode bullets, arrows, or emojis as list markers. Use plain round bullets. Each line should start on its own row in Notepad.
Chasing keyword density in Skills while bullet one still says worked on reports. Shipped, built, cut, or migrated with a number tells the desk what you did last quarter.
Uploading a designed PDF when the portal accepts DOCX. Word exports with standard heading styles usually keep employer blocks separated better than template PDFs with invisible tables.
Saving the file as resume.pdf instead of Firstname_Lastname_Role.docx. Recruiters search folders by role title. A clear filename helps humans even when parsers ignore it.
Run a parse check before you reapply
Rebuilt layout still fails if the checker shows your must-have only in Skills. Upload the file you will send and run a free ATS check against the same posting. Confirm the posting's top term appears inside extracted experience text, not only in a footer row.
Fix layout and contact lines first. A longer Skills list cannot invent proof on a dated line.
When you are choosing which reqs deserve a rewrite tonight, score your job match on the posting before you spend an hour on bullets three and four.
Rebuild plain structure tonight
That is the file a desk can forward. Skills still matter as tags. Bullet one under your current employer is where scope proof lives. When those disagree, you stay in the maybe pile even with the right qualifications on paper.
Open the posting. Highlight the first requirement. Rebuild one single-column employer block with Month Year on the title line. Rewrite bullet one so the first eight words answer the posting with a tool, scope, and metric.
Job searching is already hard. You do not need a longer keyword list. You need a plain export Workday or Greenhouse can read. When you are ready to verify the wording, check your resume for free against the same posting before you send it.
Frequently asked questions
Workday reads a text stream, not your visual layout. Two-column templates, sidebar date tables, and invisible Word tables flatten into one block. Job titles, dates, and bullets merge before a recruiter opens the file. Paste your export into Notepad. If employer names and Month Year digits sit on one line, rebuild as a single-column block with dates on the title line.
Most parsers read top to bottom inside the file, not left to right across your design. A table that parks dates in a right cell often imports after the company name, which slides bullets onto the wrong employer. Use plain lines instead. If you must keep a table, test the export in Notepad before you apply.
Try DOCX first when the portal allows it. Word files with standard heading styles usually keep employer blocks separated better than designed PDFs from template sites. If PDF is required, export from Word after you strip tables and columns. Paste the export into Notepad so you see what the recruiter view receives.
Yes on many platforms. Greenhouse, Workday, and Lever often drop header and footer zones on import. If your phone number, email, or portfolio URL lived only there, the parsed profile looks incomplete. Move contact lines to row one of the main body as plain text labels.
Sometimes, but parsers keyword-match standard labels like Experience, Education, and Skills. A header such as Where I Made Impact may import as body text, which buries employer blocks under the wrong section. Use conventional headings so the parser knows where each block starts.