Most resumes should be one page; two pages is appropriate once you have roughly ten or more years of relevant experience. The page count itself is not a rule a recruiter enforces — it is a proxy for whether every line earns its place. A tight one-page resume almost always beats a padded two-page one, because the reader spends their first few seconds deciding whether to keep going. Three pages is for academic CVs and senior executives with a genuinely long record, not for most candidates.
The real rule: every line earns its place
Page count is the wrong thing to optimize. The question is never "can I fill two pages?" — it's "does each line here make me more hireable for this specific role?" If a bullet doesn't, it's costing you, because it dilutes the bullets that do. A recruiter giving your resume its first pass is reading fast and looking for reasons to keep going. Filler gives them a reason to stop.
That framing resolves most length anxiety. You don't pad to reach a second page, and you don't amputate strong content to force a single page. You write everything worth saying, ruthlessly cut what isn't, and the right length falls out of that process.
Recommended length by experience level
These are defaults, not laws. Adjust based on how much of your experience is genuinely relevant to the role in front of you.
| Experience level | Recommended length | Why |
|---|---|---|
| Student / new grad | One page | Limited professional history; depth comes from projects, internships, and coursework, not volume. |
| 1–10 years | One page | Enough to show a clear trajectory; rarely enough strong, recent material to justify a second page. |
| 10+ years | One or two pages | A second page is earned only if it holds strong, relevant bullets — not older roles or a skills dump. |
| Senior leadership / executive | Two pages | Longer track record of scope and impact that a recruiter genuinely needs to see. |
| Academic / research (CV) | As long as needed | Publications, grants, and teaching are expected in full — a different document with different norms. |
What to cut first
When a resume runs long, the fat is almost always in the same places. Trim in this order:
- The objective statement. "Seeking a challenging role where I can grow" tells the reader nothing. Replace it with a two-line summary of what you do and your biggest result, or drop it entirely.
- "References available on request." Assumed by default. It only takes up a line that could hold an accomplishment.
- Jobs older than 10–15 years. Collapse them into a single "Earlier experience" line, or remove unrelated ones. Recency is what the reader weights.
- Generic responsibilities. "Responsible for managing projects" describes a job, not your performance in it. Cut it or rewrite it as a result.
- Skills nobody is hiring for. Microsoft Word, email, "team player." If it's assumed or unrelated to the role, it's noise.
Tightening a bullet without losing substance
Most length problems aren't too many bullets — they're bloated ones. The same achievement often reads stronger in half the words once you cut the throat-clearing and lead with the result. Same truth, less space, more impact:
Was responsible for overseeing the management of a team that worked on various projects related to improving the performance of the company website over time.
Led a 5-person team that cut homepage load time from 4.1s to 1.3s, lifting conversion 18%.
Cut the hedging, added scope and two metrics — and it is shorter.
Helped to assist with the process of onboarding new customers and ensuring they had a good experience during their first few weeks.
Rebuilt customer onboarding, raising 30-day activation from 52% to 71% across 400+ accounts.
A vague "helped" becomes an ownable, measured outcome.
A note on formatting and length
Length lives or dies on layout. A clean, single-column resume with sensible margins and a readable font fits more real content per page than a design with wide gutters and oversized headers. Don't shrink the font below 10.5pt or crush the margins to claw back space — if you're fighting for millimeters, you have a content problem, not a formatting one. Cut a weak bullet instead.
The short version
Default to one page; earn the second page with strong, relevant, recent content rather than seniority or padding. Cut the objective, the references line, ancient roles, and generic duties first. Tighten bloated bullets into measured results. The ATS doesn't care how long your resume is — but the human who reads you next does, and a resume where every line earns its place is the one that holds their attention long enough to call you.
Common questions
- Is a one-page resume too short for a senior role?
- Not necessarily, but senior candidates usually have enough relevant, recent accomplishment to justify two pages without padding. The test is content, not seniority: if a second page is full of strong, specific bullets the role cares about, use it. If the second page is older roles, a skills dump, and references, cut back to one.
- Do recruiters actually reject resumes for being too long?
- Rarely as a hard rule, but length signals editing judgment. A recruiter who opens a three-page resume for a mid-level role reads it as someone who could not prioritize. The cost of going long is not an automatic rejection — it is that your strongest points get diluted by weaker ones the reader has to wade through.
- Should I cut old jobs to save space?
- Yes — collapse or drop roles older than about 10 to 15 years, especially if they are unrelated to the job you want. You can keep a brief "Earlier experience" line listing titles and companies without bullets. The space is better spent expanding your last two or three roles.
- Does the ATS care how long my resume is?
- No. Applicant tracking systems extract text regardless of length and do not score on page count. Length is purely a human-readability concern — it matters to the recruiter who reads you after you clear the parser, not to the software itself.
Sources
Keep reading
What does an ATS-friendly resume look like?
An ATS-friendly resume is single-column and plain-text, with standard headings, readable dates, and no tables or graphics. Here is the exact anatomy.
Why is my resume getting rejected by ATS?
ATS rejection has two causes: parse failures from bad formatting and keyword gaps against the job description. Here is how to diagnose and fix yours.
Why is my job application getting ghosted?
Most applications get filtered out by an ATS before any human reads them. Here's what actually happens, why, and how to know if your resume is the bottleneck.
Why am I not hearing back from job applications?
Not hearing back is usually the funnel, not you: ATS filtering, recruiter triage, pre-filled roles, and the channel gap. Here is how to fix what you control.