How long a resume should be comes down to experience level. With under roughly eight years of experience, one page is still the right default and what most recruiters expect for entry-level and early-career roles. Senior professionals (eight-plus years, multiple roles, or leadership experience) usually need two pages to show the scope honestly, and a second page is widely accepted for those levels. Academic, research, and medical CVs are the standing exception: they can run several pages because the convention is to list every publication, grant, and talk. The guiding rule isn't a page count — it's relevance density. Every line should earn its place, whether the resume is one page or three. Tailor the content to the role first; length is a downstream consequence of what's worth including.
The one-page rule and when it's outdated
The one-page resume rule was a constraint of an earlier era, when resumes were faxed and a single sheet was a physical convenience. It stuck because for most early-career candidates it's still good advice — a one-page resume forces you to cut fluff and lead with your strongest material, which is exactly what a recruiter scanning for six to eight seconds needs. If you're a new graduate, switching fields, or applying to your first few roles, aim for one page and treat the constraint as a discipline rather than a ceiling.
The rule becomes outdated as soon as you have enough relevant experience that cutting to one page means cutting genuinely relevant content. A senior engineer with four meaningful roles, quantified impact at each, and a stack of relevant certifications can't honestly fit it on one page without hiding the very proof a recruiter wants to see. Forcing two pages of relevant material onto one page — by shrinking fonts to 8pt, dropping margins to nothing, or gutting bullets into fragments — produces a worse resume than two clean pages ever could. The rule to retire isn't length; it's the assumption that shorter is always better. Shorter is better only when it removes noise.
Length by experience level
Here's a practical breakdown of how long a resume tends to be at each stage of a career. The bands are guidelines, not laws — a content-dense one-pager can beat a padded two-pager, and a focused two-pager can beat a cramped one-pager. Match the length to the volume of relevant material you have, not to a rule of thumb.
| Experience level | Typical length | Why |
|---|---|---|
| Student / intern / new grad (0–2 yrs) | 1 page | Limited relevant work; one page forces you to lead with internships, projects, and coursework that map to the role |
| Early career (2–8 yrs) | 1 page, sometimes 2 | One page usually fits; go to two only if you have several relevant roles with quantified impact worth showing |
| Senior individual contributor (8–15 yrs) | 2 pages | Multiple substantive roles, leadership scope, and quantified outcomes that one page can't carry honestly |
| Manager / director / executive (15+ yrs) | 2 pages, occasionally 3 for executive | Strategic scope, team size, and multi-role arc need room; 3 pages only for genuine executive-level depth |
Academic, research, and medical CVs sit outside this table entirely. The convention there is a long-form CV that lists publications, grants, conference talks, teaching, and committee work — these routinely run three to ten pages and reviewers expect that. If you're applying for an academic or research position, follow the field's CV convention; if you're applying for an industry role with an academic background, convert to a resume format (one to two pages) and fold publications into a concise section rather than listing every one.
What actually determines length
Content density matters more than page count. A one-page resume padded with five generic skills bullets and an objective statement that says nothing is longer in the sense that counts: it wastes the recruiter's attention. A two-page resume where every bullet is quantified, every role demonstrates scope, and every section earns its place is shorter in effective reading time because the recruiter can extract signal faster. Decide what to include by asking whether each line would survive a 'so what?' challenge — if you can't say what the line proves and why it matters to this role, it's padding, and padding is what makes a resume feel long regardless of its physical length.
The highest-leverage move is quantification. 'Led a team' is padding; 'Led a team of 6 engineers, shipping the payments platform 2 weeks early and cutting p99 latency 35%' is signal. Quantified bullets carry roughly twice the information density of vague ones, which means a resume full of quantified bullets can fit more relevant material in less space — the opposite of the usual assumption that numbers bloat the resume. The tailoring guide walks through how to quantify each bullet against the job description; the role-specific guides give you the metrics each job family actually cares about.
ATS and resume length
Applicant tracking systems do not penalize length. An ATS extracts keywords and ranks by coverage; whether those keywords live on page one or page two makes no difference to the algorithm. The widely-repeated claim that 'ATS only read the first page' is a myth — modern parsers read the entire document, top to bottom, and surface content by section and keyword. If your resume is two pages because it has genuinely relevant content, the second page is read and scored the same as the first.
What does matter for ATS is the format of the content, not the page count. A two-page resume with a single column, standard section headers (Experience, Education, Skills), and real text parses cleanly; a one-page resume laid out as a two-column template with text boxes and icons in the sidebar misparses and loses keywords. Optimize for parser-friendly format first, length second — the ATS-friendly format guide covers the format rules that actually affect parsing.
The one place length does affect outcomes is the human review, and it's a softer factor than people think. Recruiters spend roughly six to eight seconds on an initial scan, but that scan is for relevance signals — title match, scope, proof of impact — not for a page count. If the most relevant material sits in the top third of page one (your summary, your lead role, your first bullet), a recruiter will catch it whether the resume is one page or two. Burying the matching content on page two is the real failure mode, and it has nothing to do with length — it's a relevance-ordering problem. Reorder by relevance within each role entry and lead with the role most relevant to the JD; see the tailoring guide for the method.
How to cut a resume down
If you're targeting a one-page resume and need to cut, the order in which you cut matters — you want to remove noise first and signal last. Work through this list in order until you hit the target length:
- Drop the objective statement — replace it with a tailored 2-line summary that maps to the role, or remove it entirely if the summary isn't earning its space
- Cut any bullet that doesn't touch a keyword the job description asks for and isn't a credibility anchor (recent title, recognizable company)
- Combine bullets from the same role that describe the same project — 'Led migration of 12 services to Kubernetes' is stronger than three bullets about the same migration
- Remove roles older than roughly 10–15 years unless they're directly relevant; summarize early career as a single line ('Various engineering roles, 2008–2015') if you want continuity
- Trim the Skills section to the terms the JD actually names — a 40-item skill wall reads as padding and most matchers deduplicate anyway
- Tighten fonts to 10–11pt and margins to 0.5in only as a last resort; if you're shrinking type to fit, you've usually kept too much content
Cutting should never remove relevant, quantified material. If after the cuts above you still have two pages of genuinely relevant content, submit two pages — a clean two-page resume beats a cramped one-page resume at every experience level above early career. Get an instant read on whether your resume carries enough relevance per page with the JDMatcher matcher — upload the resume and the JD, get a match score, and see whether the content that's earning its place is the content you kept.