The one thing is this: does the second page contain anything a hiring manager for this role would be sorry to miss?
If yes, use two pages. If no, use one. Years of experience is a rough proxy for that, which is why you will hear "one page under five years, two above", but the proxy is not the rule. Plenty of people with eight years fit honestly on one page, and a few people with three years have genuinely earned a second.
The rough guide anyway
Since you came here for an answer:
- Freshers and up to about three years: one page. There is almost no situation where a fresher needs two, and a second page at this stage nearly always means projects from first year, coursework lists or a skills section that has got out of hand.
- Three to eight years: one page is still the default. Two is acceptable if you have changed roles or domains and the earlier work is relevant to what you are applying for.
- Eight years and up, or leadership roles: two pages is normal and nobody will blink.
Never three, unless you are applying for academic or research positions, where a full CV with publications is expected and different rules apply.
Why the advice is so contested
Recruiters genuinely disagree on this, and both sides have a point.
The one-page camp says that a resume is screened quickly and the first half of page one does most of the work. Anything below that is read only if the top earns it. A tight page forces you to cut weak bullets, which makes the strong ones easier to see.
The two-page camp says that an applicant tracking system doesn't care about pages, and a hiring manager who is interested will read the whole thing. Cramming eight years into one page with 9pt font and no margins is worse than giving it room.
Both are right about different things. The real risk with a longer resume is the weak material that extra room lets in. A two-page resume where every bullet is strong is fine. A two-page resume where the second page is a list of tools you used in 2017 is a one-page resume with padding.
What a "too long" resume usually has in it
When someone with four years sends a two-page resume, the second page is usually some mix of these:
- A summary at the top that repeats the job titles below it.
- The first job written in as much detail as the current one.
- A skills section listing every library ever imported.
- Certifications from online courses, each on its own line.
- Responsibilities ("Responsible for code reviews") instead of results.
None of that is wrong exactly. It just doesn't earn the space. Cut it and most four-year resumes fit on a page with normal margins.
How to cut a resume down without losing the good parts
Start from the oldest material and work up. The work you did three jobs ago should get two bullets, maybe one. Your current role should get the most space, because it is the closest match to what you are applying for and the thing an interviewer will ask about first.
Then go bullet by bullet and ask what the reader learns from it. "Worked on microservices using Spring Boot" teaches nothing a skills line couldn't. "Split the payments module out of the monolith so it could be deployed on its own; release cycle for that team went from fortnightly to several times a week" teaches a lot. Keep that kind; cut or merge the first kind. There is more on rewriting these in the post on resume bullet points.
Merge similar bullets. Three bullets about three different dashboards can usually become one bullet about the reporting work, with the most impressive dashboard named.
Shrink the skills section to what is relevant for the role you are applying to. A backend role does not need your Figma experience listed; a design role does not need your SQL.
Don't cheat with formatting. Shrinking the font below 10pt, cutting margins to nothing, or switching to two columns to squeeze more in all make the resume harder to read, and two-column layouts often parse badly in an ATS. The ATS-friendly format guide has the details on what survives parsing.
If you are moving from a service company to a product company
This is a common case in India and it changes the calculation slightly. Someone four years into a large services firm may have worked on three or four client projects, and it is tempting to give each project its own block with technologies and responsibilities.
Product company recruiters mostly care about what you built and how it went, not the list of clients. Fold the projects under one employer heading, keep two or three strong bullets for the project closest to the role, and give the others a line each. That alone often takes a resume from two pages to one. The post on moving from service to product companies goes further into what to emphasise.
Does the ATS care?
No. An applicant tracking system reads text, not pages. A two-page PDF and a one-page PDF with the same content parse the same way. What matters to the parser is structure: clear headings, one column, real text rather than text inside images.
Page length is a question for the human who reads it after the filter, and that human is usually a recruiter going through a large pile. Write for them.
What I'd do
If you are unsure, make the one-page version. Cutting is hard and it improves the writing in a way that adding never does. Then look at what you removed. If something in that pile would genuinely change a hiring manager's mind about you for this specific role, add it back and let it run to a second page.
If nothing in the pile would change their mind, you have your answer.