The ATS-friendly resume — format rules that survive every parser.

The five rules of an ATS-friendly resume

After hundreds of thousands of scans, the same five layout choices separate parser-friendly resumes from parser-killed ones. Get all five right and you’ll never lose to a formatting issue again.

1. Single column, top to bottom. No sidebars, no two-column grids, no wraparound text. Parsers read row-by-row and routinely scramble multi-column layouts.
2. Standard section headings. Summary, Experience, Skills, Education, Projects. Save the wordplay for the bullets inside.
3. Real selectable text, not images. Export from Docs, Word, or Pages so your text is selectable. If you can’t highlight your name in the PDF, neither can the ATS.
4. Real bullet characters. Use • or - or *, not custom Unicode glyphs and not text inside graphics. Each bullet ~1–2 lines, verb first, number where possible.
5. Common fonts at body size. Inter, Arial, Calibri, Helvetica, Times New Roman. Body 11–12pt, headers 14–16pt. Skip decorative typefaces and ligature-heavy fonts.

The best resume fonts for ATS (and why)

Fonts matter for two reasons: parser compatibility (can the ATS decode the glyphs?) and recruiter readability (does it look professional at a 6-second scan?). The safe set:

• Inter — modern sans-serif, excellent screen readability, no licensing issues.
• Arial / Helvetica — the safest defaults. Installed everywhere, decoded by every parser.
• Calibri — Microsoft’s default for Word; pairs well with DOCX exports.
• Times New Roman / Georgia — serif options for traditional industries (law, academia, finance).
• Verdana / Tahoma — wide letterforms, very readable at small sizes.

Avoid: Calibri Light (some parsers can’t decode the weight variant), Garamond at body size (too thin, gets misread), anything with ‘Display’ or ‘Headline’ in the name (often a different glyph set), and any font that requires a license to embed (Gotham, Whitney, ITC fonts) unless you’re absolutely sure your export embeds correctly.

PDF vs DOCX: the honest comparison

Both work on every modern ATS, but the failure modes differ.

PDF — when to use it

• You want the layout to be pixel-perfect across devices.
• You’re applying to mid-size or larger companies (they almost always run modern ATS that handle PDFs well).
• You’ve exported from Word, Pages, or Google Docs — these generate clean text-PDFs.

DOCX — when to use it

• You’re explicitly asked for it in the application.
• You’re applying to government, university, or older enterprise systems with niche ATS.
• You’re worried about font embedding (DOCX preserves font info even if the recipient doesn’t have the font installed).

Never use

• Image-only PDFs (a scanned resume, or a PDF exported from a tool that flatters text to bitmap).
• .Pages files — most ATS reject them outright.
• ZIPs, RTFs, or oddly-named files (resume-final-v6-FINAL.docx is fine; resume-final.tar.gz is not).

Why tables and columns ruin ATS resumes

Visual editors love tables and columns — they’re an easy way to align two-column content like ‘skill name | proficiency’ or ‘date | role’. Parsers hate them. Here’s what happens:

• Row concatenation. A table parser reads cells left-to-right per row, then concatenates. ‘Python | 2019 – present | Senior Engineer | Acme Inc.’ becomes one undifferentiated string in the parser’s output.
• Cell-skipping. Empty or merged cells throw off the alignment. Information that visually belongs to one role gets attributed to another.
• Section misidentification. Headers inside table cells often don’t register as section headings — so your ‘Experience’ row gets bucketed as ‘Other’.

The fix is unglamorous: use real bullets and real paragraphs instead of table-based layouts. If you need two-column visual density, use tab stops or a single column with bold section labels. Neither breaks the parser.

ATS-safe resume templates: what to use and avoid

The templates that consistently pass our scans:

• Microsoft Word’s built-in ‘Basic Resume’ and ‘Chronological Resume’. Boring, effective, single column.
• Google Docs’ ‘Serif’ or ‘Modern Writer’ templates. Clean single-column, standard sections.
• LaTeX’s ‘moderncv’ (classic, not casual) theme. Popular with engineers; parses cleanly when exported to PDF.

The templates that consistently fail:

• Most aesthetic Canva templates with sidebars, icons, or color blocks.
• Figma resume templates from design portfolios — beautiful, but built as visual artifacts, not parsed documents.
• Anything labeled ‘infographic resume’ — these are designed for human recruiters scrolling Instagram, not ATS parsers.
• Templates with skill bars (e.g. ‘Python ▓▓▓▓░’) — the bar is an image, the proficiency level is invisible to the ATS.

The one-page skeleton that always works

If you want a copy-paste template that’s guaranteed to parse, use this structure:

• Header line — Name, email, phone, city, LinkedIn URL. Plain text, no header/footer placement.
• Summary (3–4 lines) — Role + years + domain + one quantified highlight.
• Skills — Comma-separated. Categorize only if you have 20+ skills.
• Experience — Most recent first. For each role: Company · Title · Dates · 3–5 bullets, each verb-led and quantified.
• Education — Degree, school, year. Add coursework only if you’re a recent grad.
• Projects / Certifications — Optional. Only when directly relevant.

ATS-friendly resume guides by role

Format rules are universal — but the keywords, pitfalls, and bullet structures that move your score are role-specific. Pick the role you’re targeting:

Want the full theory on what gets you past the ATS? Read the complete ATS Guide or How to Pass an ATS. For the keyword side, see the resume keyword scanner or scroll up and run a free formatting check on your resume.