For most candidates, a resume should be one page. Two pages is reasonable once your record is long enough that page two is genuinely full, not three-quarters, not padded. Three pages is reserved for academic CVs, federal applications, and a small set of senior executive records where the page count is conventional inside the field.
The underlying discipline isn't a rule about years of experience; it's selection. The page is as long as the strongest version of the case for one role, and no longer. Most of what's written about resume length argues the question as a count, at what year do you earn a second page, at what title does one page stop being credible. That framing misses what the page is doing. A resume isn't a record of everything you've done; it's a tailored case for one specific role. Length is downstream of that tailoring, not upstream of it.
How long should a resume be?
One page, unless the second page is genuinely full. That answer holds for early-career, mid-career, and most senior records, including ten and fifteen-year careers that the conventional advice would push toward two pages by default.
The reason the answer isn't "it depends on your years of experience" is that years of experience is the wrong unit. Two engineers with the same fifteen-year record produce different resumes for different roles. A platform-stewardship pitch leads with reliability and incident bullets; a zero-to-one pitch leads with the migrations and the launches. Same record, two pages of selection work, two different pages, and often both fit on one page because the selection has already done the cutting.
Recruiter-preference surveys in 2025 reported a softening on the one-page norm, a 1,013-person HR survey found about half preferred two pages for experienced candidates, and a FlexJobs report named two pages as common preference for senior records. Worth knowing. Not worth treating as a mandate. The same surveys consistently find that what readers reject is a thin second page, not a single page that's been edited carefully. The reader's complaint about a one-pager is when it's been crammed; the complaint about a two-pager is when it could have been one.
When should a resume be two pages?
Two pages is the right answer when three conditions all hold. First, you have enough verifiable, role-relevant bullets that the second page would be substantively full, not padded. Second, the role you're targeting respects depth on the record, executive positions, technical leadership, deeply specialized senior individual-contributor roles where the work itself is long-form. Third, you've already done the cutting work and the page is still over.
If any of those three is missing, you're a one-pager. A senior candidate who hasn't pruned older roles is a one-pager hiding behind a two-page draft. A mid-career candidate whose second page is half-full of soft bullets is a one-pager whose page two is working against them.
When the second page is real, it should look like the first, same density, same restraint, same selection discipline. Page two isn't a relief valve for everything page one couldn't fit. It's the rest of the same argument, made at the same standard. The method for getting a senior record onto the right page count is the substance of refining a senior record without redoing it.
When does a third page make sense?
Three pages is conventional in three places, and almost nowhere else. Academic CVs, where the genre expects a publication list, conference history, and teaching record laid out in full. Federal applications, where the format itself asks for more detail than a private-sector resume. And a small subset of executive searches in regulated industries where board roles, governance history, and a record of named transactions all need to appear on the page.
If you're not in one of those three contexts, a three-page resume reads as a record that didn't get edited. Cut.
Does length affect how your resume gets read?
Yes, in two practical ways, both of which point the same direction.
The first is parsing. Resume-screening systems read the text in your file regardless of how many pages it sits on; length itself doesn't trip the parser. What does trip the parser is the formatting choices people reach for when they're trying to compress a long record onto fewer pages, multi-column layouts, headers stored as images, dense tables, custom-positioned text boxes. Those break extraction. The page-count question and the parsing question feel related, but the parsing question is really about format. Standard structure parses regardless of length; clever layout breaks regardless of length.
The second is the human reader. A long resume isn't read longer; it's read with less attention per bullet. A reader who has thirty resumes to get through in a sitting will not read your two-page resume with twice the care of your one-pager. They'll scan both at roughly the same speed and form roughly the same impression, but on the two-pager, the weak bullets dilute the strong ones. Length is a denominator. Every weak bullet that goes on the page divides the page's average claim. A short, strong resume reads as composure; a long, mixed one reads as a record someone didn't have time to edit.
Per-role tailoring is the move that resolves both pressures. A resume tailored for one role (bullets reordered for fit, weak claims cut, the strongest evidence at the top) almost always wants to be shorter than the same person's untailored draft. The discipline is in what tailoring changes; page count follows.
What density really costs
The other common move when fitting a long record onto one page is to shrink everything, narrow margins, smaller type, tighter leading, more bullets crammed per role. That works up to a point. The point it stops working is well before most people stop pushing.
A page that's been compressed below readable density signals exactly what its writer was trying to hide: there's more here than will fit, and rather than cut, the choice was to cram. Readers notice. The page reads as anxious, every inch of margin recruited for evidence, no room left for the eye to rest, every bullet shouting for space against every other bullet.
The fix is almost always to cut, not to shrink. A bullet that doesn't survive a cold read is the same bullet whether it sits in 11pt or 9pt; making it smaller doesn't make it earn its spot. The cut version of the same record reads as confident at standard density. The shrunk version reads as crowded.
Crammed page, fifth bullet on a role
Also participated in cross-functional planning meetings, presented quarterly updates to stakeholders, and contributed to the team's onboarding documentation for new engineers.
Cut, with the four kept bullets at standard density
(removed)
Three responsibilities folded into one bullet to save a line. Each one is generic enough that any engineer on any team could have written it. Cut the bullet, give the remaining four room to breathe, and the page reads stronger at the standard size than it did compressed.
The same principle applies to the move that puts older roles into a tiny bottom section to "save space." If a role from twelve years ago doesn't earn a real entry, it earns a one-line title-and-dates listing, not a shrunken three-bullet block. Pick the format that matches the weight, not the format that lets you keep more.
What about a career change or a thin early record?
Two cases sit outside the standard one-page advice, but in opposite directions.
A pivot resume is often shorter than the candidate's chronological draft would be, because the through-line for a new role rarely needs every job described in full. Older bullets that don't point at the target shrink to one-line entries. The page lands at one page or under, deliberately, because the structure is doing the case-making and the length isn't carrying it. The mechanics are in the pivot reads as fit.
An early-career resume sometimes struggles to fill a page rather than to fit on one. The fix isn't to inflate, it's to widen the definition of work and order what's there for fit. A first resume can be three-quarters of a page and read as composed; what it can't read as is padded. The piece on making the case from work you have covers the move.
In both cases, the page length is downstream of the tailoring discipline, not upstream. The candidate writing the third version of a tailored draft worth the weeks a real application earns almost never has a page-length problem to solve, because the selection has already happened.
Closing
Length is downstream of selection. Cut until the page makes the case, and the page count answers itself.
The question that started this piece, how long should a resume be?, has a clean answer once the framing is right. The page is as long as the tailored case for one role. For most candidates, that's one page. For some, on some applications, it's two. The years on the record don't decide. The role you're applying to, and what you've chosen to put on the page in service of it, do.
Cut until the page earns itself. Send fewer applications, each one finished.
Read next