The new grad software engineer resume

One page, and the top third decides

For a new grad, one page is not a guideline, it is the format. More than that signals padding, and padding is the specific thing a reviewer is scanning for. Within that page, the top third - roughly everything above the fold of a quick glance - carries the decision. Put your strongest evidence there and accept that the bottom may never be read.

Project bullets, which are the whole argument

With no job history, your projects carry the resume. The difference between a weak and a strong project entry is almost entirely in the bullets. A weak one describes what the thing is. A strong one describes what you did, how, and what resulted.

• Weak: "A web app for tracking expenses built with React."
• Strong: "Built an expense tracker in React and Postgres; added an indexed query layer that cut dashboard load from 2.4s to under 300ms for 5,000-row accounts."
• The pattern is what you built, the technology, and a specific result. The result does not have to be impressive. It has to be specific.
• If you genuinely have no numbers, use scope instead: rows handled, users, endpoints, test coverage, how long it has been running.

Two or three projects described this well beat six described vaguely. If a project cannot survive a follow-up question about why you built it that way, leave it off - it will come up in the interview, and the questions are in new grad software engineer interview questions.

The screening layer before a human

Many applications pass through automated parsing before anyone looks. You cannot reverse-engineer a specific system, and most advice claiming to is guesswork, but a few things are safely true:

• Use a single-column layout. Multi-column resumes parse unpredictably.
• Submit a PDF unless another format is explicitly requested.
• Put skills in plain text, not in graphics, icons or skill-level bars - those carry no parseable information.
• Use the words from the job description where they are honestly true of you. If it says TypeScript and you know TypeScript, write TypeScript, not just JavaScript.
• Skip the photo, the age and the address. A city is enough.

What to cut

• Objective statements. "Seeking a challenging role" uses prime space to say nothing.
• Skill rating bars. Nobody can calibrate your self-assessment, and they waste the width.
• Long coursework lists. Two or three relevant courses, if any. A reviewer assumes a CS graduate took data structures.
• Unrelated jobs, in detail. One line is fine and shows you have worked. Three bullets about a retail shift is space taken from your projects.
• Anything you cannot discuss for two minutes. Everything on the page is fair game in the interview.

Where CoPilot Interview fits

Disclosure: we build an interview assistant, so treat this as a disclosed pitch. The resume gets you the interview; it does nothing once you are in the room. CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about four seconds during live rounds, with a permanent free tier that needs no credit card. On the resume itself, our AI resume builder is the relevant tool, and the honest limits of letting AI write it are in should you use AI to write your resume.

Frequently asked questions

How long should a new grad software engineer resume be?

One page. For a candidate without professional experience, going longer reads as padding, and padding is exactly what a reviewer is scanning for. Fitting on one page also forces the editing that makes the page work.

Should education or projects come first on a new grad resume?

Projects, in almost every case. Your degree is the reason you are in the applicant pile rather than the reason you get picked out of it, so the top third of the page should carry the evidence that distinguishes you.

How do I write resume bullets with no work experience?

Use the pattern of what you built, the technology you used, and a specific result. The result does not need to be impressive - it needs to be concrete. If you have no numbers, use scope instead: rows handled, users, endpoints, or how long the thing has been running.

Do I need a different resume for every application?

Not a rewrite, but do adjust the skills section and the ordering of projects to match the job description where it is honestly true of you. A full custom rewrite per application is rarely worth the time compared with asking for a referral.