Is one page still the rule for CS resumes in 2026?

Yes for new grads and under-five-years experience. After roughly five years and multiple notable roles, two pages is acceptable. Anything beyond that should be tightened — three-page CS resumes almost always get filtered before a human reads page two.

What font size is too small on a one-page resume?

Body text under 10pt and headers under 11pt get hard to scan. Most ATS scanners parse 10-12pt cleanly; below 9.5pt risks parse errors. If you're shrinking type below 10pt to fit, you have too much content — cut, don't compress.

Should I drop projects or work experience to make it fit?

Cut the oldest, least-relevant bullets first — never whole sections. Trim a 5-bullet old internship to 2 bullets before you remove a recent project. Projects often carry more signal than old experience for new grads.

Are two-column resumes a good way to fit more on one page?

Mixed. They look modern but parse poorly on some ATS systems, which scan left-column-first and can misorder dates. If you use two columns, keep all chronological data (experience, education) in the main column and put skills/links in the sidebar.

Guide · resume

How to Fit a CS Resume on One Page in 2026

Cut bullets ruthlessly, drop the objective section, shrink margins to 0.5 inch, and let the body breathe at 10-10.5pt. One page is a discipline, not a format — every line that doesn't earn its space gets removed.

By Alex Chen, Founder, InterviewChamp.AI · Last updated 2026-05-19

How do you fit a CS resume on one page in 2026?

Cut bullets ruthlessly, drop the objective section, shrink margins to 0.5 inch on all sides, and let the body breathe at 10-10.5pt. One page is a discipline, not a layout. Every line that doesn't push you closer to an interview gets removed — including pretty headers, a skills wordcloud, and any bullet that starts with "responsible for."

What to cut first

The fastest way from 1.4 pages to 1.0 pages — without losing real signal — is to delete in this order:

1. The objective statement. Replace with a summary only if the summary carries a number; otherwise drop it. See the guide on the CS resume summary section.

2. "References available upon request." Universal advice for two decades — drop it.

3. Every soft-skill claim without a story. "Strong team player" without a project where teamwork mattered is filler.

4. Coursework lists longer than five items. Pick the four to six classes most relevant to the target role; cut the rest. Linear Algebra and Discrete Math don't need to compete with your actual projects for space.

5. Old internship bullets you've since improved on. A four-line bullet from a 2022 summer is taking space from a three-line shipped result from 2025. Trim the older one to a single line, or drop it.

6. Stack listings that repeat across sections. If "Python, Go, Postgres" appears in the summary and in three job entries, list it once in a Skills line and let the bullets carry the verbs.

Adjust the layout, not the type size

Most candidates shrink font to 9pt as a last resort. Don't. Recruiters scan visually; sub-10pt body type slows the scan and triggers a "this is desperate" read. Adjust these instead:

Margins. 0.5 inch on all four sides is the standard floor for ATS-safe resumes. Going to 0.4 inch is fine in practice but risks edge clipping on some printers — keep 0.5 inch as the default.

Line height. 1.05-1.15 line height (vs. the default 1.5) recovers two to three vertical inches on a typical CS resume. Bullets stay readable if you give them 4-6pt of space before/after instead of the default 12pt.

Header bloat. Center-aligned phone, address, email, LinkedIn, GitHub, portfolio, and Twitter is 4-5 wasted lines. Keep four contact items on one line, separated by middle dots: email · phone · github.com/yourhandle · linkedin.com/in/yourhandle.

Section dividers. Replace fat horizontal rules with a single 0.5pt line. Drop subsection icons. Pretty resumes lose to scannable resumes when the JD-to-application ratio is north of 50:1.

What "earns its space" means

According to a Ladders eye-tracking study on resume scanning, recruiters spend roughly 7.4 seconds on the first scan of a resume. They fixate on titles, dates, companies, and the top bullet under each role. Everything else competes for whatever attention is left.

A bullet earns its space if it does at least one of these:

Names a shipped artifact (with link if possible)
Carries a quantified result
Demonstrates a specific technical decision (the "why X over Y" sentence)
Maps directly to a requirement in the JD you're applying to

If a bullet does none of those, it's filler. Filler is the most common reason CS resumes spill past one page.

ATS-safe formatting at one page

Per the Indeed Career Guide on ATS resumes, the formats that parse most reliably across the major ATS systems share these traits:

Single column for chronological data (experience, education, projects)
Standard section headers ("Experience," "Education," "Projects," "Skills") — not creative substitutes
No images, icons, or text inside graphics
No header/footer text (some ATS strips it)
Standard fonts that ship with the system (no custom font files embedded)

You can have a great-looking one-page resume that parses badly. Test by uploading to one of the free ATS-parse tools before sending — if your dates show up in the wrong order, the column layout is the problem.

When two pages is the right call

After roughly five years and multiple notable roles, the one-page rule loosens. The bar for moving to two pages: page two must be at least 60% full and contain content that would force a cut on page one. A 1.1-page resume is the worst length — better to trim back to 0.95 pages or expand to 1.6 with real content.

About the author: Alex Chen is the founder of InterviewChamp.AI and writes about the modern tech interview from the inside — what changed, what works for new grads, and where the old playbook fails.

Frequently asked questions

Is one page still the rule for CS resumes in 2026?: Yes for new grads and under-five-years experience. After roughly five years and multiple notable roles, two pages is acceptable. Anything beyond that should be tightened — three-page CS resumes almost always get filtered before a human reads page two.
What font size is too small on a one-page resume?: Body text under 10pt and headers under 11pt get hard to scan. Most ATS scanners parse 10-12pt cleanly; below 9.5pt risks parse errors. If you're shrinking type below 10pt to fit, you have too much content — cut, don't compress.
Should I drop projects or work experience to make it fit?: Cut the oldest, least-relevant bullets first — never whole sections. Trim a 5-bullet old internship to 2 bullets before you remove a recent project. Projects often carry more signal than old experience for new grads.
Are two-column resumes a good way to fit more on one page?: Mixed. They look modern but parse poorly on some ATS systems, which scan left-column-first and can misorder dates. If you use two columns, keep all chronological data (experience, education) in the main column and put skills/links in the sidebar.