Skip to main content

Resumes & ATS

Best resume format for ATS in 2026

The most reliable resume format for applicant tracking systems has not changed much, despite how much is written about it each year: reverse-chronological, single column, standard headings, real text.

Updated 21 July 2026

Reverse-chronological, and why the alternatives struggle

Reverse-chronological, most recent role first, is what parsers are built to expect, and what recruiters scan for. It is the default for good reason.

Functional resumes, which group by skill and downplay dates, parse badly and are read with suspicion, because their main historical use has been concealing gaps. If you have gaps, a chronological resume with a brief honest note handles them better than a format that hides them.

Hybrid formats, a short skills summary above a chronological history, parse fine and are a reasonable choice for career changers, provided the chronological section is intact underneath.

Section order that works: contact details, a brief summary, experience, education, skills. Certifications or publications after that if relevant to the field.

Layout, fonts, and length

Single column. This is the highest-impact rule and the one most attractive templates break.

Standard fonts at 10-12pt: Arial, Calibri, Helvetica, Georgia, Times. The specific choice matters far less than legibility and consistency.

One page for under roughly ten years of experience, two pages beyond that. Three pages is rarely read in full outside academic CVs, where different conventions apply entirely.

Avoid tables for layout, text boxes, headers and footers carrying important content, and any graphic containing words. Simple bullet points, real text, consistent date formatting.

Include your contact details in the body of the document, not only in a header, header content is a common parsing casualty.

Keywords, without the folklore

Match the language of the job description for skills you actually have. If the posting says "PostgreSQL" and your resume says "Postgres", write both once.

That is the whole legitimate technique. What does not work: white text keyword stuffing, which parsers extract and humans then see as deception; long ungrammatical skill lists; or repeating a term a dozen times.

Most modern systems rank candidates rather than filtering on keyword counts, and the ranking is one input to a recruiter who will read the document. Write for the recruiter, make sure the parser can read it, and you have done everything that reliably helps.

Common questions

Is a two-column resume always bad for ATS?

Not always, some modern parsers handle them. But it is the single most common cause of scrambled output, and there is no upside worth that risk when a single column reads just as well.

Should I include a photo on my resume?

In the US, UK, and Canada, conventionally no, and many employers prefer it omitted to reduce bias. In parts of Europe and Asia it is expected. Regionally driven rather than a parsing issue.

How long should a resume be in 2026?

One page under about ten years of experience, two pages above that. Length is less important than every line earning its place.

Related