9 min read
You can have perfect bullets and still lose the screen because the file reads like a jigsaw puzzle.
I don't score your font choice first. I score whether I can find employer, title, and dates without squinting.
If you're getting silence and you've already rewritten bullets, paste the PDF into Notepad tonight. That's the same order many parsers see, and it won't lie about column damage.
Most resume layout mistakes recruiters notice aren't typos. They're structural choices that looked fine in the template preview and broke on upload.
Check your resume for free after you flatten columns so Workday still shows your latest role on line one of Experience.
Quick Wins
- Paste into plain text; if dates sit under the wrong company, drop the second column.
- Replace tables with left-aligned lines: Company, Title, Month Year to Month Year.
- Remove icons, skill bars, and text boxes from the header block.
Why your layout fails before your bullets do
Parsers and humans share one habit: they read top to bottom, left to right. Sidebars break that contract.
The symptom looks like a content problem. You assume keywords are missing. Often the Experience block imported as a Skills paragraph and your top role never linked to dates.
Before: Two-column Canva layout with contact details in a colored rail; plain-text export shows phone number between bullet two and bullet three of your oldest job.
After: Single column with name and email on two lines, then Experience; export keeps each employer block intact.
Recruiters in Greenhouse and Workday live in preview panels. If the panel shows blank employer rows, many of us won't open the PDF attachment to reconstruct your career.
Layout also drives trust. Cramped margins and six font sizes signal you didn't proof the file you'd ask a stranger to read.
White space isn't wasted space. It's how a tired recruiter confirms you're at the right company before they read bullet one.
When a posting asks for PDF, export from a simple Word doc instead of a design tool when you can. Design exports embed layers that plain text can't see but parsers still trip over.
For parser mechanics, see how resume layout impacts data extraction . For column-specific damage, see why columns and tables kill resume accuracy .
Fancy templates fail for the same reason in why fancy resume layouts fail . The fix is structural, not cosmetic.
Five checks to diagnose layout damage
Check 1: Run the plain-text export test
Copy the whole PDF or Word file into a plain editor. Read the first thirty lines aloud. If you hear your email in the middle of a job block, stop and rebuild layout.
Before: Export opens with SKILLS Python SQL then ACME CORP buried on line eighteen.
After: Export opens with your name, contact line, EXPERIENCE, then ACME CORP with dates on the next line.
Check 2: Kill tables and text boxes
Tables look tidy in Word. Parsers treat each cell as a random fragment. Convert to simple lines and standard bullets.
Keep section headers as plain words: Experience, Education, Skills. Custom icons before headers often strip the label entirely on import.
Check 3: Standardize dates and alignment
Put Month Year on the same line as company or directly under title. Right-aligned dates in a second column frequently detach in preview.
Use one date style across the file. Mixing 01/2024, Jan 2024, and 2024 only in the same resume confuses both humans and imports.
Check 4: Simplify the header
Name, phone, email, city if needed, one link. No photo for US corporate screens unless the employer asks. Logos in the header can push contact fields into the footer in Taleo uploads.
Check 5: Re-export and compare page breaks
Open the PDF on another device. If a role splits across pages mid-entry, add a line break before the employer name or trim sidebar content so the block stays together.
Copy-paste skeleton for a safe employer block:
COMPANY NAME, City, ST (optional)
Job Title | Month Year to Month Year
• Verb + outcome + tool + metric
• Verb + scope + team size + metric
EDUCATION
Degree, Major, School Name | Year
I've passed on strong operators because the Greenhouse preview showed three employers stacked under one date range while a weaker candidate's single-column file imported cleanly on the first upload.
Print page one if you still trust the PDF on screen. Sometimes a margin error only shows on paper or in a different PDF reader than the one you used to export.
If you're mid-career and need two pages, keep page breaks between roles, not between a title and its first bullet. A split block looks like two half jobs in preview.
Layout traps that survive proofreading
- Skill bars and star ratings that replace plain skill lines.
- Putting core keywords only in a sidebar Skills column with no proof in Experience.
- Using headers and footers for contact info the parser skips.
- Saving a designed PDF when the posting allows .docx and your tables won't translate.
- Micro font to force a second page of relevant work onto page one.
- Center-aligned job titles with justified body text that adds odd spaces between words.
- Nested bullet levels more than two deep; parsers flatten them into one run-on line.
- Hyperlinks styled as buttons that strip the URL text on import, leaving blank lines.
If you inherited a template from a friend who works in design, assume it's wrong for corporate ATS until the paste test passes. Their industry rewards visuals; your screen rewards order.
Creative layouts that fail ATS checks are covered in why ATS rejects creative resume layouts . Start with structure, then tune bullets.
Confirm layout before you submit again
Upload the same file you plan to send. Scroll the preview top to bottom. Missing sections mean layout, not word choice.
Compare preview against your plain-text paste line by line for the first role. If the company name differs or dates shift, rebuild before you tweak summary language.
Name the file Firstname-Lastname-Resume.pdf unless the portal specifies otherwise. Recruiters search folders after reqs reopen; a clear name beats Resume_final_v7.pdf every time.
Score your job match after layout passes. Keywords only help when Experience imported under the right employer row.
Run the ATS check on the flattened file. If employer names disappear, fix columns before you add keywords.
Generate a cover letter only after the resume preview looks right. A letter won't rescue a parser error on the attachment.
Make the file boring on purpose
Resume layout mistakes recruiters notice aren't about taste. They're about read order. One column, plain headers, and a clean plain-text export give your bullets a chance to matter.
Run the five checks, re-upload once, and keep a saved flat version for the next req. You'll spend less time guessing why silence keeps showing up.
Save the plain-text export in a notes file dated today. When you tailor bullets next week, rerun the paste test so a new sidebar doesn't sneak back in from an old template.
Read more
Frequently asked questions
They care about scan speed. Fancy design that breaks plain-text export makes your dates and employer names land in the wrong order. Clean single-column layout reads the same in Workday preview and on paper.
Not always, but parsers often read down the left column first. Skills on the right can attach to the wrong job. If your export shows scrambled lines, switch to one column before you apply again.
Follow the posting. If it says PDF only, export from Word without text boxes. If it allows .docx, that file often survives Greenhouse imports better than a designed PDF from a template shop.
Roughly half-inch to one-inch margins keep text selectable. Margins below a quarter inch plus tiny font is how strong candidates still get skipped because the parser merges lines.