When a One-Page Resume Hurts You in Tech
The one-page resume rule survives because it contains a useful instinct: cut weak material, keep the signal high, and make the document easy to scan. The trouble starts when that instinct hardens into a rule. In tech, forcing everything onto one page can hide the evidence that shows scope, progression, and impact.
A recruiter or hiring manager is not rewarding you for restraint by itself. They want a resume they can scan quickly and trust. Harvard Career Services and the University of Washington both emphasize the same basics: be concise, specific, and tailored to the role.[1][5] MIT adds a practical constraint: recruiters spend only a few seconds on an initial pass, so formatting needs to stay familiar and readable.[2] If staying on one page forces tiny type, shaved margins, or vague bullets with no outcomes, you are protecting the rule instead of helping the reader.
Why the one-page rule sticks
For students and early-career candidates, one page is often good advice. Many people at that stage simply do not have enough relevant experience to justify more space, and the limit forces better choices. The Muse presents experience level as a rule of thumb rather than a hard cutoff, and Jobscan offers similar guidance: shorter resumes often make sense early on, while two pages become more common as relevant experience grows.[3][4]
The problem is what happens when that advice gets repeated without the context. A junior developer with one internship and two strong projects should avoid padding a second page. A senior engineer with multiple relevant roles, promotions, architecture work, and operational ownership has a different risk: not being too long, but being too compressed.
Where one page still works well
One page still works when the story is naturally tight. That is often true for early-career candidates, career changers who need to foreground only the most transferable material, or applicants with a narrow and coherent work history. In those cases, brevity improves focus. It helps the reader see the strongest projects, the clearest skills, and the most relevant experience without extra noise.
What one page should not do is create the appearance of simplicity by stripping out useful detail. If the document is short because it is well edited, that is a strength. If it is short because your accomplishments have been flattened into generic claims, it is probably too short.
Signs the one-page limit is hurting you
The best test is not your exact year count. It is whether important evidence disappeared during compression.
A common warning sign is generic language. Phrases like "built backend services" or "worked with cross-functional teams" may be true, but they do not tell a reader much about level. Specificity is what signals seniority: system scale, constraints, ownership, and measurable outcomes. Harvard explicitly recommends fact-based writing and quantifying where possible.[1]
Another warning sign is missing progression. Promotions, expanding scope, mentoring, incident leadership, hiring, and architecture decisions often separate a mid-level resume from a senior one. If those details vanish so the resume can stay on one page, the format is distorting the story.
A third sign is layout stress. Once you are shrinking text, trimming margins, or packing too much into each bullet, readability starts to drop. MIT advises familiar formatting, readable type, and enough space for information to be scanned quickly on first pass.[2]
If one page forces generic bullets or cramped layout, the document is probably hiding useful evidence.
When two pages are justified
Two pages are justified when the extra space carries proof rather than padding.
That is often the case if you have several relevant roles, a visible promotion path, or work that spans multiple layers of the stack. It can also make sense when your experience includes projects that cannot be summarized honestly in a single line, such as a cloud migration, reliability turnaround, security remediation, or major product launch with measurable business impact.
In practice, the missing details are usually things like scale, ownership, technical judgment, and outcomes. A second page gives you room to show what you owned end to end, what got better because of your work, and how your responsibilities changed over time. That is different from using more space to list every tool you have touched since college.
This is also where the article differs from the broader "one page or two" debate. The real issue is not whether two pages are allowed. It is whether forcing one page causes you to undersell yourself.
How to expand without bloating
If you decide a second page is warranted, page one still has to do most of the work. Your strongest and most recent evidence should appear there, because that is where the first judgment forms.
After that, the goal is selective expansion. Use the extra space for older but still relevant accomplishments, a clearer promotion story within one company, or a few projects that show technical judgment and business effect. Keep older roles shorter unless they remain directly relevant. Prefer outcomes over task lists. Cut stale technologies, coursework, weak summaries, and soft-skill filler before you cut evidence that proves level.
Jobscan is useful here as supporting corroboration, not because it sets a universal rule, but because it frames length around relevance and experience depth rather than ideology.[4] The Muse makes the same point from another angle: a longer resume is defensible when the extra material is relevant and earned.[3]
If you keep a structured master resume and create role-specific versions from it, tools like CoreCV can help you preserve detail without maintaining several bloated documents by hand.
A practical decision rule
If you can fit your best and most relevant evidence on one page without shrinking the text, flattening your progression, or deleting meaningful outcomes, stay on one page.
If getting to one page requires you to hide seniority signals, compress multiple roles into vague bullets, or trade readable layout for density, use two pages and make both pages earn their keep.
The goal is not to satisfy a page-count rule. It is to make your level and fit easy to understand. In tech, that sometimes fits on one page. Sometimes it does not.
Use the shortest version that still preserves the evidence a reader needs.
Sources
- Harvard FAS Career Services. "Create a Strong Resume." https://careerservices.fas.harvard.edu/resources/create-a-strong-resume/
- MIT Career Advising & Professional Development. "Resumes." https://capd.mit.edu/resources/resumes/
- The Muse. "How Long Should Your Resume Actually Be? Here’s an Easy Guide to Follow." https://www.themuse.com/advice/how-long-should-a-resume-be
- Jobscan. "How Long Should a Resume Be in 2025?" https://www.jobscan.co/blog/how-long-should-a-resume-be/
- University of Washington Career & Internship Center. "Resumes." https://careers.uw.edu/channels/resumes/