ATS-friendly resume format

Most advice about applicant tracking systems is either fearmongering or folklore. Modern parsers handle a well-structured single-column PDF perfectly well, and the claim that 75 percent of resumes are auto-rejected by robots is not supported by anything credible.

What genuinely breaks parsing is narrower than the panic suggests: text inside images, multi-column layouts that interleave when linearised, contact details in the header or footer region of the file, tables used for layout, and unusual section headings.

So the practical goal is not to make the resume ugly. It is to keep the underlying structure linear and the headings conventional, which costs almost nothing in visual quality.

Section order

Top to bottom. The order matters more than the styling, because it decides what a reader sees in the first few seconds.

HeaderContact details in the body of the document, never in a PDF header or footer.
SummaryPlain text. No text boxes.
SkillsComma-separated within category lines. Parses better than graphical proficiency bars.
ExperienceConventional heading. Company, role, dates in a consistent order.
ProjectsStandard bullets, no nested icons.
EducationConventional heading. 'Education', not 'Academic Journey'.

What has to be on the page

A single-column layout, or a two-column one you have verified linearises correctly.
Standard section headings: Experience, Education, Skills, Projects, Certifications.
Dates in one consistent format throughout, ideally 'Jan 2026 – Mar 2026'.
Selectable text in the PDF. If you cannot select your name with a cursor, no parser can read it.
Contact details in the document body, not in the page header or footer region.

Bullets in the right shape

Bracketed values are placeholders. Substitute your own real figures, and leave a line out entirely rather than inventing a number for it.

Test it yourself: open the PDF, select all, paste into a plain text editor. What you see is roughly what the parser sees.

Skills as parseable lines: 'Languages: Python, SQL, JavaScript' rather than a five-dot proficiency graphic.

Dates consistent throughout: '[Jun 2025 – Aug 2025]', not 'June 2025 to Aug 25'.

Mistakes that cost this profile interviews

Instead ofBelieving that any design at all breaks an ATS.

Do thisIt does not. Colour, rules, a considered typeface and a sidebar that linearises correctly are all fine. Structure is what matters, not restraint.

Instead ofSkill proficiency bars and star ratings.

Do thisUse words. A parser reads '4 of 5 stars' as nothing, and a human cannot tell what your four stars mean either.

Instead ofContact details placed in the PDF's header or footer region.

Do thisPut them in the body. Some parsers skip header and footer content entirely, which loses your phone number.

Instead ofCreative section headings like 'My Journey' or 'What I Bring'.

Do thisUse the conventional ones. Parsers map known headings to fields; unknown ones get dropped into an unstructured bucket.

Instead ofSubmitting a scanned or image-based PDF.

Do thisExport text-based PDF from the source. A scan is unreadable to every parser without OCR.

Free template for this format

Meridian — Single column, conventional headings, selectable text, and contact details in the body. It parses cleanly while still looking designed. Hand-designed, and the PDF and Word exports are free with no watermark and no card.

Use the Meridian template Score a resume you already have

Questions

Do applicant tracking systems really reject 75% of resumes?

No. That figure circulates widely without a credible source. Most systems rank and surface rather than auto-reject, and a human decides. Poor parsing hurts by making your resume incomplete in the database, not by triggering an automatic rejection.

Should I send a PDF or a Word file to an ATS?

PDF, unless the portal explicitly asks for .docx. Modern parsers read PDF reliably, and a PDF preserves your layout where a Word file reflows on the reader's machine.

Do two-column resumes work with an ATS?

Often, yes, if the reading order linearises correctly. Test it: select all in the PDF and paste into a text editor. If the columns interleave into nonsense, switch to a single column.

Should I stuff keywords from the job description?

Match genuine terms you can defend, particularly exact tool and technology names. Stuffing is visible to the human reading after the parser and reads as dishonest, which costs more than the keyword gains.