How Long Should a Resume Be?

One page is advice, not a rule. The real constraint is that almost nobody reads past the first third, whatever the length.

From the team behind PassATS. Free to read, no email required.

The short answer

Under five years of experience: one page. You will not have enough evidence to fill two without padding, and padding is visible.

Five to fifteen years: two pages is normal and expected. Compressing fifteen years onto one page means cutting the evidence that makes you credible.

Academic, research or senior technical: longer is conventional, and a publication list is not a resume anyway.

Why the rule exists

The one-page rule is a proxy for a real problem: most resumes are too long because they list duties rather than outcomes.

Cutting to one page usually forces the right edit. That is why the advice works even though the rule itself is arbitrary.

What actually gets read

The top third of the first page. Your name, your summary, and your most recent role.

This is why page count matters less than order. A strong second page nobody reaches is worth less than one line moved higher.

What to cut first

Roles more than fifteen years old, unless they are the reason you are qualified. A single line each is enough.

Duties that any holder of that job title would have had.

"References available on request." Everyone knows.

A skills rating out of five. Nobody agrees what four means, including you.

Anything you would not want to be asked about in detail.

What length does to parsing

Length itself is not scored. A parser reads two pages as happily as one.

What does hurt is the compression people apply to hit one page: shrinking margins to nothing, dropping to eight point type, or moving content into a sidebar to save vertical space. That last one is a genuine parsing failure, and it is caused by the page count rule rather than by the length.