An ATS-friendly format is not ugly — it is disciplined. The rule is simple: everything a parser needs sits in one predictable column of real text.
The safe layout
- One column, top to bottom; no sidebars, tables, or text boxes
- Standard fonts (Arial, Calibri, Georgia) at 10.5 to 12 points
- Section headers on their own lines: Summary, Experience, Skills, Education, Certifications
- Dates in one consistent format, like "Mar 2023 - Present"
- File name like "Juan-Dela-Cruz-Virtual-Assistant.pdf"
Section-by-section template
Header: name, role headline, city and timezone, email, phone, and one profile link. Summary: three lines maximum, tailored to the post. Experience: company, role, dates, then outcome bullets. Skills: a flat comma-or-line list of tools and competencies, no skill bars or star ratings — parsers cannot read graphics, and humans distrust "5 stars in Excel". Education and certifications close the page.
What breaks parsing
- Headers and footers holding your contact details (some parsers skip them entirely)
- Icons standing in for words, like a phone icon instead of "Phone:"
- Photos and logos — also a bias risk many employers strip anyway
- Creative section names like "My Journey" instead of "Experience"
FAQ
One page or two? One page under five years of experience; two pages when you genuinely need them. Never shrink the font below 10 points to force one page.
Does PDF or DOCX parse better? A text-based PDF is safe nearly everywhere and locks your layout. Only send DOCX when the post explicitly asks.