The One-Page Resume Rule: When It Applies—and When to Break It

The one-page resume is one of those rules people repeat without context—like "never wear brown shoes with a navy suit." In reality, length is a proxy for focus. Most readers are not counting inches; they are judging whether you respect their attention and whether every line increases their confidence that you can do this job.

A tight two pages from a principal engineer with fifteen years of relevant launches is not the same as two pages from a new grad who is repeating coursework and club memberships. The question is not "How long is my career?" It is "How dense is the signal on each page?"

Why one page is still the default for early career

If you have fewer than eight to ten years of experience—or fewer years in the field you are applying to—one page is usually the right container. Readers expect it, and brevity forces you to kill redundancy. When a junior resume spills onto page two, it is often padding: every course, every hackathon, twelve "skills" you used once.

That does not mean you should hide impressive work. It means you should compress early roles into a line or two, merge overlapping bullets, and move deep technical detail to a portfolio or GitHub link if needed.

Mid-career: the danger is museum curation

Around the eight-to-twelve-year mark, many candidates become archivists. They keep every legacy system they ever touched because leaving something off feels like erasing history. Recruiters do not need your complete museum; they need the last five to seven years in high resolution and the older years in summary form.

Try this exercise: for each job older than seven years, allow yourself one line of company, title, and dates, plus at most one bullet unless that role is directly relevant to the posting. If you cannot explain why a bullet helps you win this interview, cut it.

When two pages is not only acceptable but expected

Senior IC and leadership candidates in technical, product, and program roles often need two pages because the proof is layered: multiple flagship launches, cross-company initiatives, patents or publications, board exposure, or P&L scope. Academia and research paths may use longer CVs entirely—that is a different document culture.

If you use two pages, front-load relevance. Page one should stand alone as a compelling snapshot: headline fit, strongest roles, strongest metrics. Page two should deepen—not introduce—your story.

How to tighten without dumbing down

• Collapse older roles into a single "Earlier experience" line block if needed.
• Remove skills you would not want a technical screen on.
• Merge bullets that describe the same project from slightly different angles.
• Move lists (publications, talks, patents) to an addendum or link if they dominate space.

Interviewers forgive length when every paragraph earns its place. They rarely forgive boredom on page one.

A practical rule of thumb

If you are on the fence, print your resume—or view it on a laptop screen without scrolling—and read only the top half of page one in sixty seconds. If you cannot articulate why you are a strong yes for the role from that half alone, fix that before you debate margins on page two.