ATS-Friendly CV and Resume Format

Most ATS failures are formatting failures, not talent failures. Candidates obsess over keyword lists while shipping two-column Canva PDFs where work history lives in a table the parser reads as alphabet soup. Recruiters then search for React, find nothing, and assume you never used it — even when the skill is sitting in a graphic chip the database ignored. This guide covers fonts, columns, tables, headers, bullets, and file types that survive real imports into Greenhouse, Workday, Lever, and iCIMS — without making your resume ugly to humans. Fix layout once, then stop fighting the same invisible rejection.

Skip unsourced claims about what percentage of text a parser keeps. Check your own file: paste the resume into a plain-text editor. If titles, dates, and bullets come out in a sensible order, a parser can probably read them. If they come out scrambled, fix the layout before you worry about keywords.

Why does formatting break before anyone reads?

ATS imports strip layout and keep text flow. Anything that depends on position — sidebars, tables, text boxes — loses meaning when order shuffles. Recruiters rarely see your PDF as you designed it; they see a profile built from whatever parsed. If your title ended up under the wrong company, search breaks. If your skills section never imported, keyword filters skip you. Formatting is infrastructure. Treat it like HTTPS — invisible when right, catastrophic when wrong.

Which formatting choices are safe?

• File: .docx from Word or Google Docs, or PDF printed from those tools — not from Figma or Canva.
• Fonts: Arial, Calibri, Helvetica, Georgia, Times New Roman at 10–12pt body, 14–16pt name.
• Layout: single column for experience; margins 0.5–1 inch; left-aligned body text.
• Headers: standard labels — Experience, Education, Skills, Projects.
• Bullets: simple hyphen, dot, or circle — not custom Wingdings or emoji.
• Contact: plain text in body, not only in PDF header/footer.

Which formatting looks fine but fails a parser?

• Two-column templates with work history split across the page.
• Tables used to align dates and job titles — cells import out of order.
• Skill bars, star ratings, and icon grids instead of words.
• Text boxes for summary or contact blocks.
• Scanned paper PDFs or image-only resumes.
• Tiny gray font or white-on-color blocks parsers skip as decoration.

Can the same content parse differently?

• Before: Two-column Canva résumé with jobs in left column, dates in right margin. After: Single-column export; title, company, dates on consecutive lines per role.
• Before: Skills shown as 5-star icons for Python and SQL. After: Skills: Python, SQL, dbt, Looker — plain list under a Skills heading.
• Before: Name and email in PDF footer on every page. After: Contact block at top of first page in main body text.
• Before: Experience in a three-row table with merged cells. After: Each job as heading + bullet list with no table borders.

When are columns and sidebars okay?

A narrow sidebar for contact and skills can work if your employment narrative is full-width below the header. Never put job bullets in a sidebar. Never split one role across columns. If you use a template with two columns, run the copy-paste-into-Notepad test. If employment paragraphs interleave with skills, rebuild. Recruiters forgive plain. They do not forgive missing history.

Should you send a PDF or a DOCX?

Many enterprise ATS still parse DOCX more reliably than PDF. PDF from Word is usually acceptable; PDF from design tools is not. Some postings force PDF — export from Word, not Canva. Avoid password-protected or portfolio-combined files unless requested. If you maintain two versions, keep content identical — recruiters notice when the PDF says Senior Analyst and the DOCX says Analyst II. When in doubt, upload what the form labels as preferred and keep a plain backup ready.

What section order should you use?

Put Experience before Education if you have relevant work history. Avoid orphan headings at page bottoms — Word's keep with next on job headings helps. Do not bury Skills on page three if the role is skill-heavy; a short skills block under summary is fine. Page breaks inside a single job's bullets can split parse oddly in some systems; keep each role's bullets together when possible. If you must use two pages, make page two start with a full job block, not a lone bullet stranded from the previous role.

What should you check before you apply?

Export final file. Select all, copy to plain text — read for scrambled order. Search your must-have keyword in that paste — if missing, parsers will miss it too. Open on phone — if you pinch-zoom to read, simplify. File size under 2MB. Filename: Firstname-Lastname-Resume.pdf. Thirty seconds of QA beats fifty applications to a black hole.

Does accessible formatting also parse better?

Good ATS formatting also helps screen readers: real headings, logical order, text instead of images for contact info. Alt text in PDFs rarely helps parsers — put the words in the body. Hyperlinks are fine when the visible text is descriptive; avoid click here as your only LinkedIn label. Accessible structure is parseable structure. Candidates who fix layout for robots often accidentally fix layout for humans too.

See the reading order of your own file in the ATS parser test

Tables get their own note: can an ATS read tables in a resume?

Validate formatting and keywords with our ATS resume checker