The one-page rule is entry-level advice that never got retired. At 10+ years, page count follows scope more than years: recruiters in a 482-person simulated-hiring study picked two-page resumes 2.3x more often, and the gap widened for senior roles. The page budget by career stage and market (US/UK/CA/AU/EU), the 10-year compression rule (which roles get full bullets, which collapse to one line), what page 1 must do in 7 seconds vs what page 2 must verify, how ATS parsers actually treat page 2, why the portfolio belongs on a site and not on page 3, a 13-year before/after, a cut-order list, and five mistakes that turn a strong career into a weak document.

The one-page rule is entry-level advice that never got retired. It made sense when a resume had one internship and one degree on it. At 10+ years, forcing 14 years of scope onto one page produces either 9-point type with 0.4-inch margins, which nobody reads and some parsers mangle, or a list of job titles with the impact stripped out.

The data does not support the one-page reflex at senior level. In a simulated-hiring study of 482 recruiters, hiring managers, and HR professionals, participants were 2.3x as likely to pick the two-page resume over an otherwise equivalent one-page version (5,375 of 7,712 selections), and the preference was strongest for managerial and senior roles. At the same time, eye-tracking research puts the initial recruiter scan at roughly 7 seconds. Both findings are true at once, and together they define the job: page 1 makes the decision, page 2 verifies it.

This piece is the rulebook: the page budget by career stage and market, the 10-year compression rule for which roles get full bullets and which collapse to a line, what page 1 must accomplish in the scan, how ATS parsers actually treat page 2, where the portfolio goes (a site, not page 3), a 13-year before/after, a cut-order list, and five mistakes that turn a strong career into a weak document.

1. Page Budget · By Career Stage and Market

Page count is driven by scope. Years on their own do not add pages: a 12-year career of similar-scope roles fits on two pages with room to spare, while a 12-year career spanning IC → lead → manager across three industries needs every line of two pages and occasionally a third.

Career stage	Pages	Why
Entry (0-3 YOE)	1	One role plus projects. Two pages signal padding
Mid (3-8 YOE)	1-2	Two pages only when the second is full of quantified achievements, not duties
Senior / Staff / Manager (8-15 YOE)	2	The default at this stage. One page reads as under-scoped; three reads as unedited
Director+ / 15+ YOE	2-3	A third page is acceptable when it carries board work, publications, patents, or P&L history the target JD asks for
Academic / medical / research CV	Uncapped	Different document, different rules. Out of scope here

Market conventions change how much slack you get:

US / Canada: two pages is normal at 10+ years. Three is tolerated for Director+ and rare below it.
UK / Ireland: two-page CV is the standard at every level above entry. Three pages is read as a failure to edit.
Australia / New Zealand: the most tolerant market. Two to three pages is standard, and 3-4 pages is not unusual for experienced professionals. A US-style one-pager reads as thin.
Germany / DACH and most of the EU: two pages, with formal structure expectations (and in Germany, conventions around a photo and personal details that US resumes omit). Three pages is common only for senior technical or academic profiles.

Rule of thumb for 10+ years, any of these markets: two pages, and every line on page 2 has to earn its place. If you are applying across markets with one master document, build it to the two-page norm and let the Australian version breathe rather than compress the US version to one page.

2. The 10-Year Compression Rule

The biggest structural error past the ten-year mark is chronological completeness: every role since 2010 gets four bullets because that is what the template offered. Recruiters evaluate the last 5-7 years in detail and everything before that as context. The document should allocate space the same way.

Recency	Space	Content
Current role (and the one before, if within ~5 years)	5-7 bullets each	Full impact bullets with numbers. The decision is made here
Years 5-10 back	2-4 bullets per role	Only achievements that map to a must-have on the target JD. Cut the rest
Years 10+ back	1 line per role, grouped under "Earlier Experience"	Title · Company · Years. No bullets, unless a single achievement is the only evidence of a JD requirement
Internships, part-time, pre-degree work	Omit	They do not survive the 7-second scan and they cost lines

The Earlier Experience block is the tool most senior resumes are missing. Three early roles that currently occupy half a page compress to:

Earlier Experience
Software Engineer II · Northwind Logistics · 2012-2014
Software Engineer · Contoso Retail · 2010-2012

Nobody loses information that matters (the timeline is intact, the progression is visible), and half a page returns to the roles that get evaluated.

One exception, applied deliberately: if a JD's must-have is something you did ten years ago and nowhere since (a regulatory domain, a specific platform), one bullet under that early role is justified. Keep it to one bullet, and leave the rest of that role as a one-liner.

3. Page 1 Decides · Page 2 Verifies

The 7-second scan lands on the top third of page 1 and moves in an F-pattern: name and title, summary, first role's first two or three bullets. Everything the recruiter decides on sits in that area, so it has to be built with that in mind.

Page 1 must carry:

Header: name, target title (not your current one, if they differ), location or work authorization line, email, LinkedIn, phone. Contact details in the body, not in a header/footer element (the ATS reason is in the next section).
Summary, three lines maximum, built from numbers: "Engineering manager, 13 years · led teams of 6-18 across payments and ledger · shipped 3 platform migrations at 10M+ daily transactions · $2.1M annual infra savings." Adjectives such as "results-driven" or "seasoned" use up scan time without proving anything.
Current role, top 3 bullets above the fold: the strongest quantified outcomes lead. Put scope numbers (team size, budget, volume) inside the bullets rather than in a separate paragraph.
Previous role, started: a role can begin on page 1 and continue on page 2. A single bullet should never split across the page break.

Page 2 carries the verification layer:

Roles from years 5-10 back (2-4 bullets each)
Earlier Experience block (one-liners)
Education, certifications, patents, publications, talks, board or advisory roles
Skills section (grouped, current tools only)

Page 2 header: repeat your name and "Page 2 of 2". Printed or screen-shared resumes get separated; a page 2 without a name is an orphan.

Page 2 should not open with Education. If the first thing on page 2 is a 2011 degree, the reader concludes the substance ended on page 1. Continue the roles first and put the credentials at the end.

4. What ATS Actually Does With Page 2

The recurring worry is that ATS "only reads the first page". Modern parsers ingest the whole document, and page boundaries are not a parsing unit. What matters for page 2 is the same thing that matters for page 1: structure the parser can read.

What the parser handles fine:
- Two or three pages of single-column body text
- Standard section headings (Experience · Education · Skills)
- Bullets, bold, plain tables with one value per cell

What breaks, on any page:
- Contact information inside a header/footer element. Several parsers skip document headers and footers entirely, and if your email lives there, the record is created without it. Put contact details in the body of page 1.
- Two-column layouts and text boxes. Column text is often read straight across, merging your left-column skills into your right-column bullets.
- Skills matrices with graphic rating bars. The bar is an image, so the parser records nothing for that skill.
- A role split across the page break mid-bullet. Most parsers reassemble it; some do not. Insert the page break before the role or before a bullet.

Keyword matching counts page 2. If the JD's must-have appears only in a year-8 role on page 2, it still matches. This is the strongest argument for keeping a targeted 2-4 bullets on those mid-career roles rather than cutting them to one-liners too early.

The recruiter-side reality is different from the parser-side reality: most ATS show the recruiter a parsed profile plus the PDF, and the human opens the PDF at page 1. So page 2 matters fully to the parser and only secondarily to the human reader. Keep the structure parseable on every page, and put the content that decides the outcome at the top of page 1.

The full structural checklist is in ATS 7 Rules 2026.

5. The Portfolio Question · It Is a Site, Not Page 3

The most common reason a long-career resume runs to three pages is the work-sample appendix rather than the roles themselves: a "Selected Projects" page, a case-study summary per product, screenshots, a list of publications with abstracts. The worry behind it is legitimate ("the bullets do not show how I think"), but the resume is the wrong container for the answer.

Map the portfolio against the three gates a resume passes through:

Gate	What it reads	What the portfolio does here
ATS parse	The file, structure only	Nothing. Screenshots and project pages are noise to the parser
Recruiter, ~7 seconds	Page 1, top third	One line: a URL in the header. Roughly one in five recruiters clicks it
Hiring manager, ~3 minutes	The whole resume, then the link	Everything. This is the reader who opens the site to see how you reason

A project appendix inside the resume spends gate-2 real estate (the scarce resource) on gate-3 material (which the gate-3 reader would rather see on a site anyway). Move it to a site, and leave one URL on page 1.

Why a site and not a PDF attachment: a PDF portfolio is lost with the laptop, cannot be updated without re-sending, is invisible to search, and tells you nothing about who opened it. A site is backed up by default, updated in one place, findable by recruiters who search your name, and can carry analytics that show which company opened which case study. Developers have the same trap in a different shape: GitHub-only. A repository shows what you built and says little about the trade-offs behind it. Put the site first and link GitHub from inside it.

What the site carries (four sections, and the material you cut from the resume lands here):

Landing: one-line value proposition, 3-5 headline outcomes with numbers, a resume download button. Same 7-second logic as page 1.
Career history: company, title, dates, and impact written at more length than the resume allows. The year-8 role that became a one-liner gets its full story back here.
Case studies, three to five: each with Context · Problem · Approach · Impact · Learnings. Approach is the section that matters at senior level. Anyone can state the problem and the result. The explanation of why you chose B over A is what a hiring manager reads for.
Writing: methodology notes, post-mortems, industry views. Four to six pieces a year is enough to show how you think.

On the resume itself: the URL sits in the header line with email and LinkedIn, on page 1, in the body of the document (not a header/footer element). If you tailor resumes per company, a per-company tracking parameter on that URL tells you afterwards which applications were actually read past page 1. Nothing else about the portfolio belongs in the resume. The resume proves scope; the site proves judgment.

6. Before / After · 13-Year Engineering Manager

Before (3 pages, 34 bullets): five roles since 2013, each with 5-8 bullets; a half-page skills matrix with proficiency bars; a "Selected Projects" appendix with three architecture diagrams; education with GPA and coursework; contact details in the document header.

After (2 pages, 18 bullets plus an Earlier Experience block):

Page 1
- Header, contact details in body, portfolio URL on the same line
- Summary (3 lines, four numbers)
- Engineering Manager, Payments Platform · 2022-present · 7 bullets, the top three:

"Led 3 teams (18 engineers) through migration of nightly reconciliation to event-driven streaming at 10M+ records/day, cutting end-to-end latency from 6.5h to sub-minute and infra spend ~30% YoY (~$180K)."
"Cut P1 incident volume 41% over 12 months by introducing service-ownership SLOs across 4 product teams; on-call load per engineer fell from 9 to 4 pages/week."
"Hired and ramped 11 engineers in 14 months (2 to Senior, 1 to Staff) while holding attrition at 6% against a 14% org average."

Senior Software Engineer / Tech Lead · 2019-2022 · 5 bullets, starts on page 1, continues on page 2

Page 2
- Tech Lead role continues (last 2 bullets)
- Software Engineer, Ledger · 2016-2019 · 3 bullets, each mapped to a JD must-have (Kafka, PCI scope, on-call redesign)
- Earlier Experience: two one-liners, 2013-2016
- Education (degree, institution, year; no GPA, no coursework)
- Skills (grouped: Languages · Infrastructure · Data · Practices), current stack only

What changed: the same career, same numbers. Sixteen bullets of duties and pre-2016 tooling were cut, the skills matrix became four lines of text, the three architecture diagrams moved to case studies on a personal site linked from the header, and the reader's first seven seconds now land on three quantified outcomes instead of a summary paragraph.

7. Cut Order · What Leaves First

When you are at two and a half pages and need two, cut in this sequence. Stop when you hit the page count.

Project appendices, work samples, diagrams, publication abstracts. They move to the portfolio site in full; the resume keeps the URL.
Duties ("Responsible for the payments roadmap"). A duty describes the job and proves nothing about how you did it.
Bullets with no number on any axis (people, money, time, volume, quality). If it cannot be quantified after an honest attempt, it is usually a duty in disguise. Method for finding the number: Bullet Quantification 101.
Tools and platforms you have not used in 5+ years, unless the JD names them.
The same achievement appearing under two roles (the project that spanned a promotion). Keep it under the role where you owned the outcome.
Education detail: GPA, coursework, honors older than a decade, a second bullet under the degree.
Objective statements, "References available on request", hobbies. None of these carry information the reader uses.
Bullets 5-7 on roles older than 5 years. Then bullets 3-4.
Only then, bullets on the current role. If you reach this step, the current role's bullets are probably too long; tighten to 22-30 words each before deleting any.

8. Five Mistakes That Turn a Strong Career Into a Weak Document

① Chronological completeness. Every role since 2009 with equal weight. The reader cannot tell which five years matter, so the document reads as a job history rather than a case for the role. Apply the compression table in section 2.

② The one-page squeeze. Fourteen years at 9-point type, 0.4-inch margins, line spacing at 0.9. Human readers skim less of a dense page, and dense layouts are also where parsing errors concentrate. Two clean pages beat one cramped one at every level above mid.

③ Contact details in the header element. Set in the template's header block because it looked tidy. A parser that skips headers files the record without an email. Put contact details in the body.

④ Three pages because of the skills section or a project appendix. A full-page skills matrix, a skills list that repeats every tool ever touched, or a "Selected Projects" page with diagrams. Skills belong in a four-to-six-line grouped block at the end of page 2, current stack only; the evidence for each skill is already in the bullets. Projects belong on the portfolio site, linked once from the header.

⑤ Page 2 that opens with Education. The reader turns the page, sees a 2011 degree, and stops. Page 2 opens with the continuation of your roles, and credentials close the document.

Automating the Repetitive Work

The compression rule is easy to state and tedious to maintain across 15-20 applications, because the right bullet count per role changes with each JD. The four Bullets tools handle the reassembly:

Bullet Creator · AI interview captures each achievement once as an impact-first bullet, numbers preserved verbatim across the five axes we call PMTVQ (people · money · time · volume · quality). Your full career goes into the library, including the year-8 achievement you only need for one in ten applications.
JD Clipper (Chrome extension) · Saves any posting with one click and extracts weighted keywords. This is how you find out which early-career bullet is a must-have for this JD and which can stay a one-liner.
Resume Generator · Configure bullet count per role block (current role 5-7, previous 4-5, older roles 2-3, or whatever the page budget allows) and it ranks your library against the saved JD to fill each block. The compression table in section 2 becomes a setting you configure once instead of an edit you repeat for every application.
Cover Letter Generator · Drafts the letter as an achievement-led 4-part narrative (result → context → action → value, 15/20/50/15%) from the same selected bullets, so the letter and the resume cite the same numbers.

Start with Bullet Creator → · 15-20 minutes per achievement. With a decade or more of work behind you, capturing 25-40 achievements is a weekend; every two-page assembly after that is minutes.

Where this fits

Library sizing and bullet count per role at each seniority level: Senior IC Triple-Artifact Workflow. Page limits and bullet counts by engineering tier, Entry through Principal: SWE Resume by Seniority.

Sources: ResumeGo simulated-hiring study (2018; 482 recruiters, hiring managers, and HR professionals; 7,712 resume selections; two-page resumes chosen 2.3x as often, with a stronger preference for managerial roles). Recruiter eye-tracking research on initial resume scan time (~7 seconds). Market CV-length conventions for US/UK/CA/AU/EU per international recruiter guidance, 2026. Bullets Editorial framework for the 10-year compression rule and cut order.

Multi-Page Resume for 10+ Year Careers: When Two Pages Win, What Page 2 Must Earn, and What ATS Does With It