One-Page vs Two-Page CV: When Each Makes Sense (2026 Guide)

Quick answer: One page works best for early-career roles and tightly scoped experience. Two pages are often better once you have 7–10+ years, multiple relevant projects, or specialized impact that would be lost by aggressive trimming.

The Real Rule (And Why "Always 1 Page" Is Outdated)

Hiring teams don't reject CVs because they're two pages — they reject them because they're hard to scan and low-signal.

Your goal isn't a page limit. Your goal is:

• ▸Fast readability (10–20 seconds)
• ▸Clear relevance to the role
• ▸Proof of impact — metrics, scope, outcomes

If one page forces you to remove the proof, keep the second page.

When a 1-Page CV Makes Sense

Choose 1 page if most of these are true:

• ▸0–5 years of experience (or you're changing careers and only part is relevant)
• ▸You're applying for roles where the scope is narrow and measurable
• ▸You can show your best work with 6–10 strong bullets total
• ▸Your experience is concentrated across 1–3 roles

Best for: internships, graduate roles, junior-to-mid positions, entry-level marketing, sales, support, ops, and junior/mid software roles with concise projects.

What a great 1-page CV includes:

• ▸Strong headline + target role
• ▸1–2 line summary (optional but useful for specialists)
• ▸Skills and tools — only what you can demonstrate
• ▸2–3 most relevant roles with quantified bullets
• ▸1–2 standout projects if experience is limited

When a 2-Page CV Makes Sense

Choose 2 pages if any of these are true:

• ▸7–10+ years of experience with relevant progression
• ▸Multiple high-impact projects or measurable achievements
• ▸You work in a specialist domain — data, security, ML, growth marketing, enterprise sales, product — where context matters
• ▸You've held roles where scope must be explained (team size, budgets, stakeholders, scale)

Best for: senior specialists and managers, technical roles with complex ownership, marketing and growth roles where results require context (channels, budgets, attribution, experiments).

What a great 2-page CV does differently:

• ▸Page 1: the "interview-maker" — most relevant wins, strongest metrics
• ▸Page 2: the "proof layer" — additional projects, publications, certifications, deeper experience

A Simple Decision Framework (60 Seconds)

Ask yourself three questions:

1. ▸Can someone understand my level and impact in 15 seconds on page 1?
2. ▸Would cutting to 1 page remove outcomes, metrics, or credibility?
3. ▸Is the extra content highly relevant to THIS role (not just "nice to have")?

If you answer yes to (2) and (3) — keep 2 pages.

Common Mistakes That Make 2 Pages Look Bad

Two pages fail when page 2 is:

• ▸A dump of old, irrelevant roles
• ▸A wall of text with no metrics
• ▸Long lists of tools without evidence
• ▸Duplicated responsibilities that don't show growth

Fix: make page 2 a curated proof layer — not a history archive.

ATS Reality: Does ATS Prefer 1 Page?

ATS systems don't care about page count. They care about:

• ▸Clean structure — headings, consistent dates
• ▸Readable PDF or DOCX
• ▸Clear job titles
• ▸Relevant keywords in context

A 2-page CV with strong structure is often more ATS-friendly than a 1-page CV compressed into tiny fonts and dense blocks.

Formatting Rules (So Either Length Works)

• ▸Font size: 10.5–12 pt (avoid 9 pt)
• ▸Margins: 0.5–0.75 in
• ▸Bullets: 1–2 lines each, lead with the outcome
• ▸Avoid: tables for core content (can break ATS parsing), icons in section headers, two-column layouts for ATS-heavy pipelines

What to Cut vs What to Keep

Cut first:

• ▸Generic responsibilities ("Responsible for…")
• ▸Long education details once you have substantial experience
• ▸Outdated tools irrelevant to your target role
• ▸Early roles that don't connect to your current career track

Keep (even if it adds a second page):

• ▸Measurable outcomes — %, $, time saved, scale
• ▸Leadership scope — team size, cross-functional ownership
• ▸Major projects tied to the job description

1-Page vs 2-Page Checklist

• ▸Page 1 tells a complete story in 15 seconds
• ▸Bullets lead with outcomes, not tasks
• ▸Skills reflect what appears in the experience section
• ▸No tiny fonts or cramped spacing
• ▸Page 2 is curated and role-relevant (if used)