How Long Should a Resume Be? The One-Page Rule Is Mostly Wrong
The best available experiment found recruiters preferred two-page resumes 2.3 to 1, and the gap widened with seniority. Here is what the evidence supports, what it does not, and how to decide by content rather than page count.
How Long Should a Resume Be?
Two pages for most people with more than a few years of experience, one page for students and early-career candidates, and the page count matters far less than whether the content earns its space. The best experiment available on the question found recruiters preferred two-page resumes over one-page resumes by 2.3 to 1, and the preference grew as seniority increased.
The one-page rule is the most durable piece of advice in this category and one of the least supported. It is worth understanding where it came from, because the reason it persists is also the reason it still does some good.
What the evidence actually shows
The strongest study on this is ResumeGo's paired-resume experiment. The design is unusually good for the category: 482 recruiters, hiring managers, HR professionals, and executives reviewed 7,712 resumes in a simulated hiring process. Every one-page resume had a two-page counterpart describing a candidate with equivalent credentials, so length was the variable being tested rather than a proxy for having more to say.
| Candidate level | Preference for two pages | Two-page score | One-page score |
|---|---|---|---|
| Entry-level | 1.4x | 7.9 | 7.2 |
| Mid-level | 2.6x | 8.8 | 7.1 |
| Managerial | 2.9x | 9.0 | 7.0 |
| Overall | 2.3x | 8.6 | 7.1 |
Two things in that table deserve attention.
First, the preference holds at entry level. It is weaker, but it does not reverse. The population most often told to stay on one page was not penalised for using two.
Second, reviewers spent 4 minutes 5 seconds on two-page resumes versus 2 minutes 24 seconds on one-page resumes. Roughly double the page count bought roughly double the attention, which is not what the "recruiters are too busy to read two pages" argument predicts.
One important limit. This was a simulated review, not a live application funnel. It measured preference and rating, not callbacks. Anyone citing this study for "two-page resumes get 2.3x more callbacks" has changed what it found. That reframing is common, and it is one of several ways this topic's evidence gets distorted.
The stat that does not exist
A claim currently circulating across dozens of resume sites: a 2024 study in Career Development International found recruiters were 2.5 times more likely to call candidates with two-page resumes.
There is no such paper that can be located. The claim appears only in recently published guides, always phrased almost identically, never with a title, author, volume, or DOI. Career Development International is a real Emerald journal with a browsable archive, and searching it produces nothing matching.
This is the same failure mode as the "ATS rejects 75% of resumes" statistic, and it is spreading faster now because AI-assisted content generation reproduces plausible-sounding citations at volume. The practical defence is small and reliable: if a statistic is attributed to a journal but no article title is given, treat it as unsourced until you find the article.
Where the one-page rule came from
The rule is not arbitrary. It encodes a real observation from an era when it was more true.
Resumes were faxed and physically stacked. A recruiter working through a pile had a mechanical reason to prefer fewer sheets. More importantly, the rule functioned as a forcing device: told to fit one page, people cut the weakest third of their content, and the weakest third of most resumes is genuinely worth cutting.
That second function still works. The rule is a bad target and a decent constraint. What has changed is the medium. Nobody stacks paper. Resumes are read by scrolling, and the marginal cost of a second screen of text is close to zero for a reader who is already interested.
The category has moved accordingly. In Enhancv's analysis of its own resume corpus, two-page resumes rose to 47% of submissions while one-page fell to 43%, with the remaining 10% longer. The average sits at 1.7 pages.
Decide by content, not by page count
The useful question is not "how many pages am I allowed" but "does every line here earn its space." Work through the resume with three tests.
Would a screener act differently if this line were removed? A bullet describing routine duties that anyone in the role would perform changes no decision. A bullet with scope and an outcome does.
Is this relevant to the job in front of me? Your first two years are relevant when you have four. At twelve years they are archaeology, and the summary line "Earlier roles at Acme and Northwind (2012–2016)" covers them entirely.
Is this the strongest version of this claim? Two vague bullets are usually one specific bullet that was never written properly. Compression by rewriting is different from compression by deletion, and it is nearly always the better trade.
Apply those three and the length answers itself. What you must not do is delete a quantified achievement to hit a page target, because that is deleting the content that produces interviews in order to satisfy a formatting preference nobody is measuring.
Length by situation
| Situation | Length | Reasoning |
|---|---|---|
| Student, intern, 0–2 years | 1 page | Not enough content to fill two honestly |
| 3–10 years | 2 pages | Where the ResumeGo preference gap is widest |
| 10+ years, individual contributor | 2 pages | Compress the first decade to a summary line |
| Manager, director, executive | 2 pages | Scope detail matters; 2.9x preference at this level |
| Academic, research, medical | 3+ pages (CV) | Publications and grants are expected disclosure |
| Federal / government (US) | 3–5 pages | The format explicitly requires detail |
| Career changer | 2 pages | The argument for relevance needs room |
The awkward case is one and a half pages. A second page that trails off halfway reads as unfinished. Either fill it with scope and outcome detail on recent roles, which is content worth adding regardless, or tighten back to one full page. Do not solve it by widening margins and dropping to 9pt, which is visible and reads as evasion.
Length has nothing to do with ATS parsing
A persistent belief worth killing: two-page resumes get filtered by applicant tracking systems.
They do not. Parsers extract the text layer of a document and map it to fields. Page count is not an input. A two-page resume parses exactly as well as a one-page resume with the same layout, and there is no length threshold at which a system starts discarding content.
What does break parsing is layout. Two-column designs cause extractors to interleave lines across columns. Text boxes and headers can be skipped entirely. And an image-based PDF — one exported by screenshotting the page rather than writing text primitives — parses as completely blank regardless of how many pages it has. Length is not the risk. Structure is.
What actually gets read
The other statistic that shapes this debate is the 7.4-second recruiter scan, from Ladders' eye-tracking research. It is usually deployed as an argument for brevity, and it sits oddly next to a study where reviewers spent four minutes.
Both are correct, because they measure different passes. The 7.4 seconds is the triage pass, where a screener decides whether a resume is plausibly relevant. That decision happens in the top third of page one, more or less regardless of what follows. The four-minute read is what happens after a resume survives triage.
The design implication is not "be short." It is that the top third of page one does all the qualifying work and the rest of the document does the convincing. Front-load accordingly: name, target-relevant summary, then the most recent and most relevant role with its strongest bullets first. Everything past that point is being read by someone who has already decided you might be worth their time.
That ordering matters more than page count, and it is the same principle behind tailoring to a specific posting.
What to cut when you genuinely need to
In rough order of what goes first:
- The objective statement. Replaced by a positioning summary or nothing.
- "References available upon request." Assumed since roughly 1995.
- Full mailing address. City and region is enough, and the rest is a privacy liability.
- Roles older than 10–15 years. One summary line.
- Skills you would not want to be interviewed on. Listing them invites the question.
- Duty bullets. Anything that describes the job rather than your performance in it.
- Soft-skill claims. "Excellent communicator" is unverifiable and occupies the space where a demonstration would go.
- Graduation years, if you are managing age bias. The degree stays.
What stays, even under pressure: quantified outcomes, scope, promotions, and anything that answers a requirement listed in the first five lines of the posting.
Practical formatting notes
Page count is not a formatting strategy by itself. A few things that reliably matter more:
Margins between 0.5 and 1 inch. Below 0.5 the page looks crowded and some printers clip it.
Body text at 10–12pt. Below 10 signals cramming.
Break pages at a role boundary. A role split across the page break is harder to read than one that starts fresh.
Repeat your name on page two. Files get separated, printed, and reordered.
Do not use a header or footer element for contact details. Some parsers skip those regions entirely, which is a genuine risk unlike page count.
The short version
The one-page rule is a good editing constraint and a bad publishing target. The strongest experiment available found recruiters preferred two pages 2.3 to 1, with the gap widening at higher levels, and gave those resumes about twice the reading time. Write until the content stops earning its space, then stop. For most people with real experience that lands on two pages, and nothing is filtering you out for using them.