7 min read
Candidates obsess over fonts and margins. Recruiters scan for whether the file survived the portal import and whether proof sits where the ATS can weight it. You won't hear these rules in a career fair booth because they're boring. They're also the difference between a readable queue row and a blank preview, and you'll spot the gap the first time you open an employer's import screen.
Start with check your resume for free on one target posting. If sections extract out of order, fix layout before you debate serif versus sans.
Below, themed Q&A covers contact blocks, dates, proof placement, and exports. Each answer maps to what shows up in Workday and Greenhouse after upload. For a cover note once the file is clean, use the cover letter generator with the same job text.
Quick Wins
- Move phone and email out of headers into the body contact block.
- Put Month Year on the same line as each job title.
- Name posting tools inside the top two Experience bullets.
What recruiters actually scan first
The first screen isn't aesthetic. It's whether your latest title, employer, and dates imported correctly. Then recruiters look for proof in the first two bullets: tool named, scope clear, outcome inside the line.
Resume formatting rules recruiters never tell you are really import rules. A two-column file can push your MBA into the skills field and your phone into education. You look unqualified in the queue even when the PDF on your desktop looks fine.
Before: Graphic banner contact row with icons and a right-margin date column.
After: Plain text contact in the body and dates inline with titles.
I've screened corporate reqs where the shortlist files all opened with title, company, and dates on consecutive lines and a metric in bullet one. The passes weren't prettier. They were easier to read in the ATS preview pane.
Resume formatting rules as themed Q&A
Contact and header rules
Q: Can contact info live in the document header?
A: Avoid it. Headers and footers often drop on parse. Put name, email, phone, city, and LinkedIn URL on line two of the body in plain characters.
Q: Should you use icons for email and phone?
A: No. Icon fonts become empty boxes or vanish. Text labels parse every time.
Before: Logo image beside name with phone inside a footer.
After: Alex Rivera | [email protected] | 312-555-0198 | Chicago, IL | linkedin.com/in/alexrivera
Date and title rules
Q: Where do dates belong?
A: On the same line as the job title or directly beneath the employer name. Use Month Year: January 2022 to March 2024. Avoid seasons and "Present" without a Month Year start.
Q: Can you use a table to align dates on the right?
A: Tables scramble import order. One line per role header beats aligned columns.
Before: Employer in left cell, dates in right cell across six rows.
After: Product Manager, Acme SaaS | Austin, TX | March 2021 to Present
Proof and skills placement
Q: Do skills lists matter more than bullets?
A: Dated bullets matter more. Put each must-have tool from the posting inside a recent Experience line with scope and a result inside the bullet text.
Q: How many bullets per job?
A: Three to five on recent roles, four is a sweet spot. Lead with the strongest proof line, not a duty opener.
Q: Should education sit above experience?
A: Only for new grads with thin work history. Everyone else leads with Experience so recruiters see proof first in the preview pane.
File export rules
Q: PDF or Word for corporate uploads?
A: DOCX is the safer default when the posting doesn't specify. Use a text-based PDF only after copy-paste keeps section order intact.
Q: Does font choice change screening?
A: Arial, Calibri, and Times New Roman parse reliably. Fancy display fonts can embed as shapes on export. Keep 10.5 to 12 pt body text.
Q: How wide should margins be?
A: Standard one-inch margins are fine. Ultra-narrow margins squeeze lines on screen and can wrap dates onto orphan rows in the preview pane. Readable beats dense.
Q: Should you bold job titles?
A: Bold titles help human skim when import preserved them. Don't rely on bold alone to separate roles; keep a blank line between jobs so parsers see boundaries.
Copy-paste block: recruiter-safe role header
Job Title, Company Name | City, ST | Month Year to Month Year
• [Action] [scope] using [tool], [result inside bullet]
• [Action] [scope] using [tool], [result inside bullet]
• [Action] [scope] using [tool], [result inside bullet]
For file-type tradeoffs, read PDF vs Word resume for ATS . For what to strip before export, see resume formatting errors that break ATS parsing .
Pretty layouts that fail the screen
Skill clouds and bar charts. They look modern in PDF and flatten poorly. Recruiters see undated tool dumps without project context.
Creative section titles. "Impact Journey" doesn't map to Experience in Taleo or iCIMS. Standard headers parse; cute names don't.
Text boxes for summaries. Floating boxes reorder on import. Keep summaries as normal paragraphs under a Summary header.
Hyperlinks that hide the URL. Plain linkedin.com/in/handle text beats "LinkedIn" as display text with a buried URL some parsers skip.
Multiple font sizes in one section. Headers that jump three sizes look sharp in PDF and confuse hierarchy on import. Keep H1 name, H2 section headers, and body text in a tight range.
Bullet symbols that aren't standard dots. Checkmarks, arrows, and custom glyphs sometimes strip entirely. Use simple round bullets or hyphens the parser has seen before.
Before: Two-page design resume with color blocks and a sidebar skills chart.
After: One-column DOCX with tools named inside four dated bullets per recent role.
Verify parse before polish
Upload your export to HireFlow's free ATS resume checker with the posting pasted beside it. Fix section order before you tweak fonts.
Draft a plain one-column file in the free resume builder , then save DOCX for portals that strip PDF styling.
Apply the rules tonight
Resume formatting rules recruiters never tell you come down to import order and proof placement. Polish matters after the file copies cleanly into plain text.
- Move contact data into the body on plain lines.
- Inline Month Year dates with each title.
- Put posting tools inside the top Experience bullets, then parse-check once.
Read more
Frequently asked questions
Color is irrelevant if the file parses. Light gray text on white can fail OCR on some PDF paths. Stick to black text on white and let bullets carry the signal.
No for ATS uploads. Put Month Year on the same line as the job title or directly under the employer name. Right-aligned date columns often import as orphan strings.
Below Experience as a single list, or skip a standalone Skills block and name tools inside bullets. Recruiters trust dated proof over undated lists.
Not for ATS. A two-line summary helps humans when title match is unclear. If you use one, keep it under three lines and mirror the posting title once.