The most repeated piece of resume advice — "keep it to one page" — optimizes the wrong variable. What actually decides whether a resume works is relevance density: the proportion of the page that matters to the specific reader holding it. Page count is an output of that, not a target.
The one-page rule has real logic behind it — attention is scarce — it's just logic applied to careers it was never meant for.
When one page is right
- Under roughly ten years of experience
- Career changers, where older detail is mostly noise
- Most corporate roles, where the resume is a screening document, not a portfolio
Note the logic isn't "you don't have enough to fill two pages." It's that your strongest material genuinely fits on one, and everything else dilutes it.
When two pages are simply honest
- Senior individual contributors and managers — multiple roles, teams, and scopes a single page compresses into vagueness
- Long technical careers where the toolchain and project history is the signal
- Academic, medical, and federal roles, which follow CV conventions of their own
- Genuinely relevant project work — the kind a hiring manager will actually read
Here's the failure mode of cramming a senior career onto one page: you end up deleting the specifics, and specifics are what get interviews. "Led engineering" and "Led 14 engineers across three teams through a platform migration" are different sentences doing different jobs — and the second one needs the room.
The caveats that keep this honest
Two pages is not a license. Page two full of decade-old detail in full bullets is worse than a tight one-pager, because relevance decays: recent roles get space, older ones compress to a line or two each. Never pad to fill a second page — a half-empty page two is fine; a padded one is not.
And remember who decides whether page two happens: the reader. Page one has to be strong enough that they want to turn it.
A workflow that settles the question
Write everything. Then cut line by line, asking one question: would a reader hiring for this specific role care? Whatever survives earns its space, and the page count is simply what the survivors add up to.
This is also where scoring tools earn their keep. Aptly scores a resume against a specific job description and flags low-relevance sections — which, in practice, is where almost every length problem lives. Cut what scores as noise and the document tends to find its correct length on its own.
The rule isn't 'one page.' It's 'no line a specific reader would skip.'
The rule worth keeping isn't "one page." It's "no line a specific reader would skip."