The one-page rule is folklore with a grain of truth in it. Parsers don't count pages at all — and recruiters don't read past what's relevant regardless of where the page break falls. So instead of arguing about pages, look at what length actually changes.
What length does and doesn't affect
- Parsing: nothing. An ATS extracts a two-page resume exactly as reliably as a one-pager. Structure breaks parsing; length doesn't.
- Keyword coverage: more room helps — up to a point. A second page lets you cover more of a JD's weighted requirements with real experience bullets. Cutting to one page by deleting relevant evidence is trading points for aesthetics.
- Skim time: brutally fixed. A recruiter's first pass lasts seconds whether you wrote one page or three. Length doesn't buy you more attention; it dilutes where that attention lands. Page one, top half, decides.
A rule based on experience, not tradition
1 page
under ~5 years of experience
2 pages
5–15 years — compressing deletes evidence
2 pages
15+ years — old roles shrink to one line each
The reasoning behind each cell: under five years, a padded second page signals you couldn't tell what mattered. From five to fifteen, squeezing a decade onto one page usually deletes the quantified evidence that wins tiebreaks. Past fifteen, roles older than 10–15 years compress to a single line or drop off entirely — nobody screens you on that decade.
Cut by relevance, not by age
When you do need to shrink, the order matters. Our engine scales every quality axis by relevance to the target job — and that's the right mental model for cutting, too:
- 1
Drop bullets that don't serve this application
Even recent ones. Three sharp bullets per role beat seven complete ones.
- 2
Compress old roles to a single line
Title, company, dates — done. Their job is proving continuity, not detail.
- 3
Kill the filler sections
Interests, references-available, and any skill you'd fail an interview question on.
- 4
Never cut structure to save space
Contact info, dates, and section headings are parse-critical — deleting them is damage, not editing.
That last step is where cosmetic cuts turn into parse damage — a missing date range breaks the years-of-experience calculation everywhere.
Length is a symptom, not a score
We deliberately don't score page count: a dense, targeted two-pager beats a starved one-pager, and the reverse is also true. What gets scored is what length is a proxy for — coverage, evidence density, relevance. Run the free checker and look at those axes directly; the right length is whatever your strongest version happens to occupy.
Written by
JobFitAI Team
The team building JobFitAI's deterministic scoring engine — nine evidence-anchored axes, a nine-vendor ATS parse simulation, and every point backed by receipts.