One Page vs Two Pages: Engineering Resume Length by Experience Level

The “one page only” rule is the most over-cited piece of resume advice on the internet. It’s calibrated for a generic career audience and applied indiscriminately to engineers, where the actual rule is more nuanced. Senior engineers cramming two-pages-of-substance into one create unreadable density; junior engineers padding to two pages signal they don’t have enough to say. This guide covers the real rule by experience level, what genuinely justifies a second page, and how to make the length decision when you’re on the boundary.

The Real Rule

One page is the default. Move to two pages when:

You have 8+ years of experience, AND
Your second page contains substantive content, not padding.

Both conditions must hold. Eight years of weak content is still one page. Three years of phenomenal content is still one page. The decision is “do I have the substance” not “am I senior enough.”

By Experience Level

New grad (0 industry experience)

One page, always. You don’t have enough work history; padding to two pages signals you’re trying too hard. Strong content in one page beats weak content stretched across two.

What goes on the page: education (top), most-substantive internships, 2–3 substantial projects, skills section, optional teaching or research roles. Education is high; experience is light.

Junior (1–3 years)

One page. Your work history is recent enough that one page comfortably holds it. Two pages at this level signals padding. Recruiters notice.

What goes on the page: most-recent role with 4–6 strong bullets, 1–2 prior roles or internships with 2–3 bullets each, education, skills.

Mid-level (4–7 years)

Almost always one page. The temptation to spill to two is highest here — you’ve accumulated several roles, several projects, several technologies — but the work is rarely substantive enough yet to justify two pages of senior+ content.

The discipline: edit aggressively. Drop the third bullet of the role from 5 years ago. Drop the project from grad school. Compress the skills section. The exercise of forcing one page often improves the resume substantially.

Senior (8–12 years)

One or two pages, depending on substance. This is the genuine boundary level. Two-page-justifying signals:

Multiple roles where you owned major systems end-to-end
Cross-team or cross-org leadership
Specific scale numbers that need real estate to describe properly
Talks, publications, patents, or notable open-source work

One-page-justifying signals:

Most career time at one or two companies (less to summarize)
Domain depth without breadth (the work fits in narrower description)
Less notable side work (no talks, patents, OSS)

Staff / Principal (12+ years)

Two pages, comfortably. By this level, you have enough substance — multiple roles, cross-functional impact, technical leadership stories, public-facing work — that compressing to one page hurts you. Forced one-page resumes at staff level read as cramped and signal “this person doesn’t realize the rules changed.”

What goes on the second page: older roles in less detail, education and certifications, talks and publications, patents, notable open-source work, optional “selected projects” section if your work is portfolio-driven.

Engineering manager / director

Two pages from when you’re a manager onward, in most cases. Manager resumes need real estate to describe team scope, business impact, organizational changes — these don’t compress as well as IC bullets. A one-page manager resume often loses signal.

What Justifies the Second Page

If you’re on the boundary, ask whether your second page would have at least 60% fill rate (i.e., not mostly white space) with substantive content. If yes, two pages. If no, condense to one.

Common substantive content for the second page:

Older roles you don’t want to drop entirely (1–2 bullets each)
Education with depth (graduate degrees, theses for research-track roles)
Notable publications or research
Conference talks (with year and venue)
Patents (with patent number)
Major open-source contributions (with project name and your specific role)
Teaching, mentoring, advisory work
Selected speaking engagements

Things that do NOT justify a second page:

Hobbies, unless extraordinarily relevant
Generic “interests” sections
References (they go on a separate document on request)
Lengthy lists of every technology you’ve touched
Filler bullets repeating points from the first page

Compression Techniques When Forced to One Page

If you’re senior and pushing for one page anyway (say, applying to a particularly traditional firm that signals one-page preference), the techniques that compress without losing signal:

Cut older roles to one bullet. Your job from 9 years ago doesn’t need 4 bullets.
Combine related bullets. Two bullets describing the same project can become one stronger bullet with both points.
Remove low-signal items. A college internship at staff level is footnote material.
Tighter skill section. Group ruthlessly; cut anything you’d hesitate to be interviewed on.
Drop GPA / coursework. If you still have these on a senior+ resume, they’re cuttable.
Compress headers. Single-line role headers (Company — Title — Dates on one line) save vertical space.
Reduce font and margins. 10pt body text and 0.6″ margins fit substantially more without looking unreadable. Below 10pt or below 0.5″ margins begins to feel cramped.

Compression Antipatterns

Things that hurt more than they help when forcing one page:

Removing all white space. A wall of dense text makes recruiters skim faster, not deeper.
Using 8pt font. Reads as desperate and is hard to scan.
Quarter-inch margins. Same problem.
Removing dates or job titles to fit. Recruiters need both; cutting them creates rejection signals.
Dropping the most recent role’s detail. Recent work is what matters most; never compress it disproportionately.

If you’ve done all the appropriate compression and still spill, the answer is two pages, not extreme density.

What About Different Markets?

Conventions vary by region:

US tech: 1–2 pages, as described above. One page strongly preferred for new grads and juniors; two acceptable for senior+.
European tech: Similar conventions, with slightly more tolerance for two-page resumes at junior levels.
Academic CV (research labs, FAANG research, AI labs research): Multi-page CVs are standard, often 3–10 pages with publication lists. Different document type entirely.
Asian markets (Japan, Korea, India): Conventions vary; check locally.
UK / Europe non-tech: Two-page resumes (“CVs”) are more standard than US one-pagers.

For US tech specifically, the conventions in this guide apply.

Frequently Asked Questions

If I’m at exactly 8 years, should I go one or two?

Depends on substance, not the year count. If your work history is “8 years at three companies, two of them not well-known, modest scope,” one page is right. If it’s “8 years at three companies, including 4 years at FAANG with major systems work, plus one industry-recognized open-source project and two conference talks,” two pages serves you better. The substance test is the gate, not the year count.

Does the second page hurt me with recruiters who only read page one?

Slightly, but less than it would hurt you to compress senior content to one page. Recruiters who skim only page one will see your strongest content there anyway (most-recent role, top bullets) — that’s where they decide. Page two backs up and provides depth for the hiring manager. As long as page one is strong on its own, page two doesn’t cost you in the recruiter screen.

What if my resume is 1.3 pages — slightly over one page?

Cut to one page or pad to two; don’t leave 1.3 pages. A page-and-a-third with a half-empty second page reads as awkward. Compress, or expand a strong-but-brief role into more substantive bullets to fill the second page legitimately.

Should I include a “Selected Projects” section for senior engineers?

If you have substantive personal or open-source projects worth highlighting, yes — usually on page two. The trap is including hobby projects that don’t reach professional substance; those signal “I had to fill space.” A Selected Projects section is justified when projects are well-known, used in production, or have measurable adoption (stars, downloads, deployments). For a typical senior engineer at a typical company, the section is often unnecessary.

Does PDF page count include the gap between pages or only printed pages?

Printed pages. If your PDF is 1.05 pages, that’s two pages from the recruiter’s view. PDF viewers and ATS tools count the actual page count, not visual fullness. Make sure your “one page” resume actually fits one printed page.