How Long Should a Resume Be? 1 Page vs 2 Pages

The Short Answer

One page if you have fewer than 8 years of relevant experience. Two pages if you have more and every line earns its space. Never three pages. That's the rule - and the rest of this article explains the nuance behind it.

Rules of Thumb by Experience Level

New graduates and career starters (0-2 years)

One page. No exceptions.

You don't have enough professional experience to justify two pages. Stretching thin content across two pages signals that you can't prioritize - which is exactly the wrong impression to give. Include internships, relevant projects, education, and a focused skills section. That's enough.

Early to mid-career (3-7 years)

One page, strongly preferred.

Most professionals in this range can fit their relevant experience on one page. The key word is "relevant." You don't need every job you've ever held. If your first role was unrelated to your current career path, condense it to one line or drop it entirely. If you're pushing past one page, cut before you expand.

Senior professionals (8-15 years)

One to two pages.

This is where the decision gets real. If you've held 3-5 significant roles with meaningful achievements at each, two pages may be justified. But "justified" means every bullet on page two is strong enough to make a recruiter keep reading. A weak second page is worse than no second page.

Executive and leadership (15+ years)

Two pages.

At this level, you have the depth to fill two pages with genuinely relevant content: multiple leadership roles, cross-functional impact, org-level decisions, P&L responsibility. Two pages is expected. But still - never three.

When Two Pages Is Justified

A second page earns its place when:

• You have 4+ roles with substantive, quantified achievements at each
• You've worked across different domains or tech stacks and each adds relevant context
• You have significant leadership, mentoring, or architectural contributions that don't fit alongside your IC work
• You hold patents, publications, or speaking credits directly relevant to the role
• The job posting explicitly asks for detailed project descriptions

When Two Pages Hurts You

A second page works against you when:

• Page two is mostly padding - coursework, hobbies, or filler bullets
• You're repeating the same achievements in slightly different wording across roles
• Your most recent and relevant role is on page one, and page two contains decade-old positions with outdated tech
• You're using a large font, wide margins, or excessive spacing to stretch content - recruiters notice
• The second page has only 3-4 lines of content - this looks unfinished, not thorough

The danger of two pages isn't length - it's dilution. Every weak bullet drags down the strong ones around it. Recruiters form impressions quickly, and a forgettable second page can overshadow a strong first page.

Tech-Specific Guidance for Software Engineers

Software engineering resumes have unique considerations:

The skills section is dense by nature

Languages, frameworks, databases, cloud providers, tools, testing libraries - a comprehensive tech stack takes real estate. This is fine. A well-organized skills section (grouped by category, not a wall of comma-separated terms) is one of the highest-value sections on a SWE resume. Don't compress it to save space.

Projects can substitute for experience

For junior and mid-level engineers, a projects section with GitHub links and tech stack details can be as valuable as work experience. But this section should shrink as your professional experience grows. By year 5, your work experience should speak for itself.

System design and architecture don't fit in one bullet

If you designed a distributed system, led a major migration, or built a platform used by multiple teams, that achievement might need 2-3 bullets to convey its scope. This is a legitimate reason to use more space - as long as the detail is specific and quantified, not vague and padded.

Don't list every technology from every role

You don't need "Technologies used: React, Redux, TypeScript, Jest, Webpack, ESLint, Prettier, Git, GitHub, Jira, Confluence" under every single position. Put your complete tech stack in the skills section once. In experience bullets, mention technologies only when they're part of the achievement narrative.

What to Cut

What to Keep

The "Page Two Test"

If you're debating whether to go to two pages, run this test: cover page one entirely and read only page two. If page two on its own would make you want to interview this person, keep it. If it reads like filler, cut it down and stay at one page.

How Length Affects Your ATS Score

ATS systems don't penalize length directly - a two-page resume gets parsed the same way as a one-page resume. But length affects your score indirectly:

• Keyword density drops - more content means your relevant keywords are diluted across more text. Your resume score baseline can actually decrease if you add content that doesn't contain relevant terms.
• Formatting matters more - longer resumes have more opportunities for formatting to break. Page breaks, inconsistent spacing, and section ordering issues become more likely.
• Recruiter attention spans - even after passing ATS, a human reviews your resume. Research consistently shows recruiters spend 6-8 seconds on the first scan. If your strongest achievements are buried on page two, they may never be read.

The ATS-friendly resume approach isn't about minimum length - it's about maximum relevance per line.

The Bottom Line

Resume length is not a goal - it's a constraint. The goal is to present your strongest, most relevant qualifications as concisely as possible. For most people, that's one page. For some, it's two. For no one, it's three.

When in doubt, shorter is better. A tight one-page resume that leaves the recruiter wanting more is always stronger than a bloated two-page resume that leaves them skimming.

Related Resume Examples

Browse all 400+ resume examples →