One Page vs Two Page Resume: The Complete Breakdown

One page is almost always right if:

You have 0–10 years of experience. For individual contributors early in their careers, one page signals editing discipline. Recruiters for these roles often explicitly prefer one page and will note a two-page resume as a red flag.

You're applying for most individual contributor roles. Software engineer, marketing analyst, financial analyst, account executive, product designer — these roles typically have a strong one-page preference below the senior level.

You're applying in technology. Tech companies — especially FAANG and high-growth startups — have a strong cultural preference for one-page resumes at most levels below senior staff or principal. Google's own recruiting guidance explicitly recommends one page per ten years of experience.

You're a recent graduate. A new graduate with a two-page resume padded with coursework, student organisations, and internships reads as someone who doesn't know what's important. Cut to one page.

Two pages is appropriate when:

You have 10+ years of relevant experience. At this point, one page forces you to omit substantive career history that context-setters and career progression markers need to be present.

You're in a senior leadership role. Directors, VPs, and C-suite candidates typically need two pages to represent the breadth of scope, team leadership, and cross-functional work.

Your technical stack is extensive. Senior engineers, architects, and data scientists with deep technical expertise often need a full skills section that alone occupies significant space.

You're in finance, law, or consulting. These industries have different norms — two pages at the senior associate/manager level is standard and expected.

Regardless of whether you choose one or two pages, these rules don't change:

Never pad to fill two pages. If you're naturally at one-and-a-half pages and stretch content to fill two, reviewers will notice the padding. A one-and-a-half page resume that's honest reads worse than a tight one-page.

Never truncate important content to force one page. If forcing one page means cutting your most impressive achievements or omitting the job titles that demonstrate your career progression, the page constraint is hurting you. Go to two.

Every bullet point should earn its space. Whether you're on one page or two, each line should either demonstrate an achievement, establish context, or prove a skill. If you can remove a line without losing any real information, remove it.

Hiring managers in FAANG and major tech companies: strong preference for one page at non-senior levels. Google, Meta, and Amazon recruiting teams have been explicit about this publicly.

Hiring managers in finance, law, and professional services: less prescriptive about length — two pages at the associate/manager level is fine. The content quality matters more than the page count.

Executive recruiters: two pages is standard for director and above. Anything beyond two pages will typically be asked to be trimmed.

The consistent signal across all hiring managers: they care about content density, not page count. A one-page resume full of quantified achievements reads better than a two-page resume half-filled with vague responsibilities.

Certain fields operate entirely outside the one-to-two page norm:

Academia: Faculty CVs list every publication, conference paper, grant, teaching position, and service role. A junior professor's CV is commonly 5–10 pages. A full professor's CV can run 20+ pages.

Medicine: Physician CVs include medical school, residency, fellowship, board certifications, hospital privileges, publications, and presentations. Multi-page is standard.

Government: Federal resumes in the US often run 4–6 pages by requirement. Government applications have their own format requirements.

Research: Scientists and researchers maintain long-form CVs that document the full publication record.

If you're applying to any of these fields, standard resume length advice does not apply. Follow the conventions of your specific field.