Is a two-page resume bad for a software engineer?

Not always. For senior engineers with a long, relevant history it's fine. For new grads and early-career engineers, a second page usually holds weaker material that should be cut.

Should my resume be one page for big tech companies?

One page is the safe choice for anyone below senior level. Senior candidates can use two if every line is relevant.

Does an ATS care about resume length?

An ATS reads both pages. Length matters to the person reading the result, which is why one page usually works better.

Can a resume be 2 pages?

Yes, with about ten or more years of relevant experience, or a research record. For everyone else, one page is expected in tech, and a second page usually means it needs editing.

Does a resume have to be one page?

No rule says so, but for software engineers with under ten years of experience, one page is the norm and what recruiters expect to skim.

How many pages should a software engineer resume be?

By Mubeen Jawed, founder of ResumeForDev · Updated November 7, 2026

Short answer

One page for most software engineers, including anyone with under about ten years of experience. Recruiters skim, and a single page forces you to keep only your strongest, most recent work. Two pages are reasonable for senior, staff and principal engineers with long, relevant histories, as long as the first page can stand on its own. Don't reach two pages by adding older or weaker bullets; cut those first.

Key points

Under about 10 years of experience: one page.
Senior and staff engineers with a long, relevant history: two pages is fine.
Either way, page one carries your best work.
Cut old roles, weak bullets and the summary before shrinking the font.

The rule by experience level

Resume length for software engineers by experience
Experience	Length	What to focus on
Student or new grad	One page	Education, internships, projects
1 to 5 years	One page	Recent roles with 3 or 4 strong bullets each
5 to 10 years	One page, sometimes a tight two	The last two or three roles in depth, older ones shortened
10+ years, senior or staff	One or two pages	Scope, leadership and impact in recent roles

What to cut first

The summary or objective, unless you're changing careers.
Bullets under roles older than about ten years. Keep the company, title and dates.
Bullets with no result, or that repeat something shown elsewhere.
Skills you couldn't be interviewed on.
Coursework, once you have a year or two of experience.

Shrink fonts and margins last. Below about 10pt text and 0.5in margins the page gets hard to read, and reviewers notice.

When two pages is the right call

If you've led systems or teams across several companies and each role has distinct, measurable results, a second page is fine. Put the best of it on page one: your current role, your biggest result and your skills. See how to write a senior software engineer resume.

ResumeForDev fits every resume to one Letter page by tightening spacing, and when the content is too long, its score tells you about how many lines to cut.

Frequently asked questions

Is a two-page resume bad for a software engineer?: Not always. For senior engineers with a long, relevant history it's fine. For new grads and early-career engineers, a second page usually holds weaker material that should be cut.
Should my resume be one page for big tech companies?: One page is the safe choice for anyone below senior level. Senior candidates can use two if every line is relevant.
Does an ATS care about resume length?: An ATS reads both pages. Length matters to the person reading the result, which is why one page usually works better.
Can a resume be 2 pages?: Yes, with about ten or more years of relevant experience, or a research record. For everyone else, one page is expected in tech, and a second page usually means it needs editing.
Does a resume have to be one page?: No rule says so, but for software engineers with under ten years of experience, one page is the norm and what recruiters expect to skim.