Most 'ATS-safe' resume templates on the internet are anything but. The Word templates with two-column layouts, custom icons, and skills ratings — those are the resumes getting silently dropped at the parse step. This article gives you the exact format we've verified against the four dominant ATS platforms (Workday, Greenhouse, Lever, Taleo) in 2026.

What ATS parsers actually do

An ATS parser converts your resume into plain text, then tries to bucket that text into fields: name, email, employers, titles, dates, skills. Anything visual — tables, columns, headers inside text boxes, images, icons — either confuses the parser or is silently discarded. The cleanest format is boring: single column, standard fonts, explicit section headings, top-to-bottom reading order.

The exact format

  • Layout: single column, 0.5-0.75 inch margins
  • Font: Inter, Calibri, Arial, or Georgia — 10 to 11 pt body, 12 to 14 pt name
  • Section headers: ALL CAPS or bold, exactly one of: SUMMARY, EXPERIENCE, EDUCATION, SKILLS, PROJECTS
  • Dates: right-aligned, format 'Mar 2024 – Present'
  • Bullets: standard bullet character, hanging indent, no sub-bullets
  • Links: spelled-out URLs, no clickable icons (LinkedIn, GitHub)
  • File: .docx or text-based .pdf — never an image PDF
Stop doing this
Tables for contact info, text boxes for skills, icons next to section headers, skills meter bars, photos — these all parse badly in 2026. Yes, even Workday, which is better than it used to be, still drops icons.

The order that maximizes scan speed

  1. Name and contact (one line if possible)
  2. Summary (3-4 lines, tailored to the job)
  3. Experience (most recent first)
  4. Skills (compact, no bars)
  5. Education
  6. Projects or Publications (optional)

Bullet-point rules that pass the 7-second scan

Every bullet should begin with a strong verb and end with a measurable outcome. Avoid any bullet that could describe five different people — 'contributed to backend services' is invisible; 'rebuilt the order-processing pipeline in Go, cutting P95 latency from 1.8s to 240ms' is a hire signal.

Keyword density without keyword stuffing

Aim for 60% of the job description's hard keywords to appear verbatim in your resume — exact strings, not synonyms. ATS systems don't reliably match 'Postgres' to 'PostgreSQL' or 'React.js' to 'React'. Our free Resume Tailor surfaces a gap list of missing keywords after every run so you can iterate until you're above the 60% threshold.

Copyable skeleton

ALEX GOLDEN
alex@example.com | 555-123-4567 | linkedin.com/in/alex | github.com/alex

SUMMARY
Senior software engineer with 8 years shipping Go and Python services at scale. Specialize in payments, observability, and on-call reduction.

EXPERIENCE
Company Name — Senior Backend Engineer                                 Mar 2024 – Present
  • Rebuilt order pipeline in Go + Kafka; P95 1.8s → 240ms; eliminated 3 pages/wk
  • Led migration from Postgres 13 → 16 across 40 services with zero downtime
  • Owned incident response rotation; cut MTTR from 42min → 12min

Company Name — Backend Engineer                                        Jul 2021 – Mar 2024
  • (role bullets)

SKILLS
Go, Python, PostgreSQL, Kafka, Kubernetes, AWS, Terraform, gRPC, Prometheus

EDUCATION
State University — B.S. Computer Science                                  May 2018
Skip the template hunt
Fitted Resume outputs this format automatically when you paste your resume and a job description. Export to .docx is available on Pro.