One Page Resume Tech: Everything to Cut (Ranked by How Little It Matters)
Published ยท Finch Team
Updated
If your one page resume tech format feels impossible to achieve, you're probably holding onto stuff that nobody reads. I've seen resumes from CS students that are two pages long and somehow say less than a tight single-pager. The problem is never that you have too much experience. The problem is that you're keeping the wrong things.
This is the prioritized kill list. We're going from "delete this immediately" to "okay maybe keep this if you have room." By the end, your resume fits on one page and actually says more than it did before.
Why One Page Matters (It's Not Just a "Rule")
Recruiters at tech companies spend 6-8 seconds on an initial resume scan. That's not a made-up stat from some career blog. Talk to anyone who's done campus recruiting at a Big N company and they'll confirm it. Two pages means half your resume literally doesn't get seen.
But there's a more practical reason: ATS parsing. When your resume gets uploaded to Greenhouse or Lever, the parser extracts text and assigns it to fields. Multi-page resumes with complex formatting cause more parse errors. A clean one-page PDF gives the parser less to screw up.
The only people who should have multi-page resumes are senior engineers with 10+ years of experience, and even then, two pages max. If you're a student or new grad, one page. No exceptions. No "but I have a lot of projects." One page.
The Kill List: What to Remove First
Here's every common resume section ranked by how safe it is to cut. Start from the top and work down until you fit on one page.
1. Objective statement: cut immediately. "Seeking a challenging software engineering internship where I can apply my skills..." Nobody reads this. It takes up 2-3 lines and says nothing the recruiter doesn't already know from the fact that you applied. Delete it. If you want to target your resume, do it through your bullet points, not a generic paragraph at the top.
2. References line: cut immediately. "References available upon request" is a relic from the 1990s. Everyone knows you'll provide references if asked. This line wastes a full line of space for zero information.
3. Full address: cut to city/state only. Your street address doesn't matter for applications. City and state tell the recruiter your location and timezone. That's all they need. You just saved a line.
4. Coursework lists longer than 4 items. "Data Structures, Algorithms, Operating Systems, Computer Architecture, Discrete Math, Linear Algebra, Calculus III, Physics II..." Stop. Keep 3-4 courses that are directly relevant to the role. A backend job? Keep Databases, Distributed Systems, OS. A data role? Keep ML, Statistics, Algorithms. Cut the rest. Everyone takes Calc and Physics.
5. Soft skills section. "Team player, strong communicator, detail-oriented, fast learner." These mean nothing on paper. Every single applicant claims these. Demonstrate them through your bullet points instead. "Led a 4-person team to ship a React dashboard in 3 weeks" says "team player" and "fast learner" without wasting a dedicated section.
6. Irrelevant work experience. Your summer job at Dairy Queen doesn't need three bullet points. If you have enough technical experience to fill the page, cut non-technical jobs entirely. If you don't, keep them but trim to 1-2 bullets max and focus on transferable stuff. "Managed inventory tracking for 200+ SKUs using custom Excel formulas" is better than "Provided excellent customer service."
7. Redundant project descriptions. If you built three CRUD apps with different tech stacks, pick the best one. Three variations of "Built a full-stack web app with React and Node.js that lets users create, read, update, and delete items" tells the recruiter you did the same thing three times. Show range instead.
Space Efficiency Tricks That Actually Work
Once you've cut the dead weight, there are formatting moves that buy you real estate without making your resume look cramped.
Shrink your margins to 0.5 inches. The default 1-inch margins in Google Docs waste a huge amount of space. 0.5 inches is the sweet spot. It's readable but gives you significantly more room. Don't go below 0.5 though or it looks like you're trying too hard.
Use a two-column skills section. Instead of listing skills in a single line that wraps, format them as "Languages: Python, Java, C++ | Frameworks: React, Flask, Django" on one or two lines. This can save 3-4 lines compared to a vertical list.
Drop the "experienced in" prefix from skills. Just list them. "Python, Java, C++" not "Experienced in Python, Java, and C++." The section header already says "Skills."
Combine your name and contact info into one line. Your name, email, phone, GitHub, and LinkedIn can all fit on 1-2 lines at the top instead of a big centered header block that takes up 4-5 lines.
Use 10-11pt font. Don't go below 10pt. But if you're at 12pt, dropping to 11pt buys you a surprising amount of space. If you're using LaTeX with a good template, 11pt with tight spacing is the standard.
How to Write Tighter Bullets
The biggest space hog on most resumes isn't a section you can cut. It's the bullets themselves being too wordy. Here's how to tighten them.
Kill "Responsible for" and "Worked on." These are filler phrases. "Responsible for developing a REST API" becomes "Developed a REST API." You just saved 2 words per bullet, which across 15 bullets saves you multiple lines.
Start every bullet with a strong past-tense verb. Built. Designed. Implemented. Reduced. Automated. Migrated. This isn't just a style thing. It forces you to lead with the action, which naturally makes bullets shorter. Check out our bullet examples guide for more patterns.
Merge weak bullets. If you have "Set up CI/CD pipeline using GitHub Actions" and "Wrote unit tests achieving 85% coverage," combine them: "Built CI/CD pipeline with GitHub Actions and wrote unit tests achieving 85% code coverage." Two lines become one.
Cut obvious context. "At my internship at Amazon, I was part of the payments team where I built a service that processed refunds" becomes "Built a refund processing service handling 50K daily transactions." The company name is already in your experience header. The team name doesn't matter.
The Things You Should Actually Keep
I don't want you to over-cut. Some stuff belongs on a one page resume for tech roles even if space is tight.
Keep your GPA if it's above 3.3. Below that, leave it off and nobody will ask during the resume screen. Above that, it's a quick signal, especially for internships where you don't have much work experience yet.
Keep 2-3 projects with real metrics or users. Projects are what separate you from other students who took the same classes. But they need to show impact. "Built a Chrome extension for tab management" is meh. "Built a Chrome extension for tab management with 200+ weekly active users" tells a story.
Keep technical skills, always. This is what ATS systems scan for keyword matches. If you cut your skills section to save space, you'll fail keyword filters before a human ever sees your resume. We wrote a whole post about getting the right keywords on your resume if you want to go deeper.
Keep the most recent and relevant experience. Even if you need to trim bullets, keep the entries. A gap in your timeline raises more questions than a job with fewer bullet points.
When Your Resume Is Too Short After Cutting
Here's something nobody talks about: sometimes you cut everything you should, and your resume looks... empty. A half-page resume is worse than a two-page resume because it screams "I have nothing to show."
If you're under 75% page fill after cutting, you need to expand, not add fluff back. Add more detail to your strongest bullets. Include a project you were on the fence about. Add a brief "Leadership" or "Activities" section if you have legitimate involvement.
The goal is a resume that fills the page without padding. That's a harder problem than just cutting, and it's one we had to solve when we built Finch's first version, a resume generator. It shortened in tiers, recompiling after each one until the PDF fit exactly on one page. If the result came out under 75% page fill, it expanded bullet points and added detail back until the page looked full. You can follow the same order by hand: cut until it fits, then check the fill, then add detail back to your strongest bullets.
The Real Test
Print your resume. Seriously, print it. Hold it at arm's length. Can you identify every section in under 3 seconds? Is there clear white space between sections? Does your eye naturally flow from top to bottom?
If yes, you're good. If it looks like a wall of text, you've gone too far with the cramming. Back off on the margins or cut another bullet.
A one page resume for tech roles isn't about fitting the most words onto a page. It's about fitting the right words. Cut the things that don't earn their space, keep the things that make a recruiter pause, and format it so the important stuff jumps out.
Once your one page is ready, Finch can point it at the right roles: each week it picks the 3 internships or new-grad roles that fit your major best and says why. Its board lists more open roles. Less time fighting Google Docs margins at 2 AM, more time applying.
For more on getting your technical skills section right, check out our formatting guide.