How Long Should a Resume Be?
One page for most people; two once there is genuinely two pages of relevant work. That is the whole answer, and the reason it stays contested is that both camps are describing different candidates.
What has changed is that a second page is no longer unusual. Recruiter surveys now split roughly evenly between one and two, and the old rule that anything over a page is automatically rejected describes a hiring culture that has largely gone.
The useful reframing is that length is an output rather than a target. Write what is relevant, cut what is not, and the page count settles itself.
What actually decides it
The rough guide is one page per five to ten years of relevant experience. Relevant is doing the work in that sentence: fifteen years of which eight are in a different field is not fifteen years for this purpose.
| Situation | Length |
|---|---|
| Student or new graduate | One page |
| Under about five years of relevant work | One page |
| Five to fifteen years | One or two — whichever the content supports |
| Senior, or a long technical history | Two |
| Academic CV, research, or federal application | As long as the format requires |
| Career changer | One — the irrelevant history is what you are cutting |
The second page has to earn itself
A second page justified by content reads as substance. A second page created by inflating margins, adding an interests section and listing every tool you have ever opened reads as padding, and it is obvious within a few seconds.
The test worth applying to every line: would removing it change whether someone wants to interview me? If not, it is there because there was room, and it will make the things that do matter harder to find.
The specific failure to avoid is a second page holding four lines. It reads as a mistake rather than as a decision — either find the content or cut back to one.
What an applicant tracking system does with length
Modern parsers read content, not page count. A two-page resume is not scored down for being two pages, and the widespread belief that it is comes from a decade-old version of these systems.
What genuinely breaks parsing is formatting: text inside images or graphics, multi-column layouts read in the wrong order, tables used for structure, headers and footers containing your contact details, and unusual section names the parser does not recognise.
So the effort spent compressing a resume onto one page for the sake of the software is misdirected. Spend it on a single-column layout with conventional headings instead, which is the thing that actually changes whether the parse succeeds.
How to cut without losing anything
Cutting is also where a resume gets stronger rather than merely shorter. Almost every first draft spends its best space on duties and its worst on results.
- Delete jobs older than about fifteen years unless one is directly relevant — a single line under "Earlier experience" covers them.
- Cut the responsibilities that any holder of the title would have had, and keep what you specifically achieved.
- Remove the objective statement if it says you want a challenging role at a growth-oriented company.
- Drop "References available on request" — it is assumed, and it costs a line.
- Trim early-career detail to title, employer and dates once later roles carry the story.
- Cut a skills list that names basic office software, unless the posting names it too.
Where longer is expected
Academic CVs are not resumes and are not length-limited. Publications, teaching, grants, service and conference presentations all belong, and a mid-career academic CV running to many pages is normal rather than indulgent.
US federal applications also run long. The format expects detail — hours per week, supervisor contact, salary — and a private-sector one-pager submitted to a federal posting frequently fails on missing required information rather than on merit.
Some technical fields expect a separate project or portfolio appendix. Keep the resume itself to the normal length and attach the appendix, rather than letting it grow into the main document.
Margins, fonts and the temptation to shrink
The obvious way to make two pages into one is to reduce the font and the margins, and it is the wrong lever. Below about ten and a half points, or margins under half an inch, a document stops being comfortable to read and starts signalling that it was squeezed.
Recruiters read many of these in sequence, frequently on a phone. White space is not wasted space in that context; it is what makes the document scannable in the ten to twenty seconds an initial screen actually takes.
If it will not fit at a readable size, the answer is fewer words rather than smaller ones. That is almost always achievable, and the resulting document is better as well as shorter.
Frequently asked questions
One page under about five years of relevant experience, two once there is genuinely two pages of relevant material. A second page justified by content is fine; one created by widening margins and adding an interests section is not.
No. Modern parsers read content rather than counting pages. What breaks a parse is formatting — multi-column layouts, text in images, tables used for structure, contact details in a header — not length.
Around ten to fifteen years for most roles. Older work can sit in a single "Earlier experience" line unless a specific role is directly relevant to what you are applying for.
Not below about ten and a half points, and not with margins under half an inch. If it will not fit at a readable size the answer is fewer words, which usually improves the document as well as shortening it.