New Grad Software Engineer Resume: Example and Guide (2026)

A new grad software engineer resume is one page, single column, with Education at the top, then internships, then two or three projects, then a short Technical Skills block. Education goes first because new grad roles are tied to a graduation window, and the recruiter needs to see your date in the first few seconds. Everything below it should show you can write and ship code: each bullet names what you built, the tools, and a result someone could verify.

Here is the default layout and roughly how much space each part gets:

This page is about students and recent CS grads in campus recruiting. If you are a bootcamp grad, a career switcher, or more than a year out of school, the entry level software engineer resume examples page has full examples for those situations.

Apply as soon as a posting you want goes live, with a resume that already includes your most recent internship. Many large tech companies open new grad software engineer roles in late summer and early fall and review applications as they come in, so applying in the first week or two of a posting usually beats applying a month later. If you are reading this in October, you are not late, but stop polishing and start sending.

What to do with your resume right now:

• Add your summer internship while the details are fresh. Write down the numbers now (latency, test coverage, tickets closed, users) and check with your manager what you are allowed to share.
• Match the graduation window in the posting. New grad roles usually state which graduation terms they accept. Write your date the way they will look for it, for example "Expected May 2027" or "Expected December 2026".
• Keep one strong base version. Then change only the top few bullets and the skills order for each role (backend, frontend, mobile, infra). Rewriting the whole page per application is a good way to send nothing.
• Plan around any return offer deadline. If you hold a return offer that expires, apply to the other companies you care about early so their interview timelines have a chance to finish before you have to decide.
• Print a few copies for campus career fairs. Use the same one-page PDF you submit online so the versions never drift apart.

Exact open and close dates vary by company and change every year, so check each company's careers page instead of relying on last year's timeline.

This example is a CS senior applying in fall 2026 for roles starting after graduation. She has one software internship (with a return offer), one earlier technical job, and two projects. Copy the structure and replace every claim with your own.

List your degree, school, and expected graduation month and year on one line, then add GPA (if it helps), 4 to 6 upper-level courses, and any TA role or academic honor. That is usually three or four lines. Recruiters for new grad roles filter by graduation term, so the date should be easy to find and in a standard format.

• Graduation date: write "Expected May 2027", not "2023 - 2027" or "Class of '27". If you finish early or in December, use the real month.
• Coursework: pick classes that match the job. Operating Systems, Databases, Distributed Systems, Compilers, Computer Networks, Machine Learning, and Computer Security are useful. Intro to Programming and Calculus are assumed and waste space.
• TA or course assistant roles: list them here in one line, or under Experience with a bullet if you also built grading tools or ran sections.
• Honors: Dean's List, named scholarships, or selective programs fit on one line. Skip high school entirely.
• Master's students: list the master's first, then the bachelor's, each with its own date. If you are in a combined BS/MS, show the expected date for each degree.

Once you have a full-time job and a year or more of experience, move Education to the bottom and shrink it to one line.

List your GPA if it is 3.5 or higher, or if a posting asks for it. If it is lower, leave it off; an application form that asks for GPA will collect it anyway, and the line on your resume is better used for a project. If your major GPA is clearly higher than your overall GPA, you can list it as "Major GPA: 3.7/4.0" as long as you label it.

GPA matters less than it used to. In NACE's Job Outlook employer surveys, the share of employers who screen candidates by GPA has fallen from about 73% in 2019 to under half in recent reports, and fewer than 40% said they would screen by GPA in the 2025 spring update. The same surveys rank academic major and internship experience above GPA as hiring factors.

Put internships under Experience in reverse order, with your title, company, and dates, and give your most recent software internship 3 or 4 bullets. If you received a return offer, add it as a short final line ("Received a full-time return offer"). It tells another company that a team who watched you work for 10 or 12 weeks wanted to hire you.

Return offers are common enough that recruiters know what they mean. NACE's 2026 Internship and Co-op Survey reported a 63.1% conversion rate (interns who became full-time hires) for the 2024-25 intern class. That also means a missing return offer is not unusual, so never write that you didn't get one.

• Accepted or holding an offer: "Received a full-time return offer" is enough. You don't need to say whether you accepted it.
• Offer for another internship instead of full-time: "Received a return offer for Summer 2027" is accurate and still useful.
• No offer, or headcount was frozen: say nothing. Let the bullets carry the role.
• Currently on a fall co-op: use "Sep 2026 - Present" and write bullets about work already shipped, not plans.
• Three or more internships: keep full bullets for the two most relevant and cut older ones to one bullet or drop them.

Applying for internships rather than full-time roles? The software engineer internship resume guide covers that version of the page.

Two or three projects are enough. Pick the ones with the most real engineering in them: something deployed, something other people used, or something technically hard (concurrency, a database you designed, a performance problem you measured). With a strong internship, two projects is fine. With no internship, use three and give each one more bullets.

1. Projects with users or a deployment beat everything else, even if they are small. "Used by 40 people in my dorm" is a real result.
2. Hard course projects (an OS kernel, a compiler, a Raft implementation) are worth listing if you label them as coursework.
3. Hackathon projects work if you can say what you personally built.
4. Tutorial clones (a to-do app, a weather app) are what to cut first.

Put the stack in the project's title line so it is easy to scan, and link the GitHub repo if the README explains how to run it. For more project write-ups, see software engineer resume projects.

Move Projects directly under Education and treat any technical work as experience: research assistant roles, TA jobs, paid freelance sites, open source pull requests, or IT and lab jobs where you wrote scripts. A recruiter reviewing new grad applications wants proof that you can build working software with some independence, and those roles can show it if the bullets are specific.

• Give your best project 3 bullets and put it first, even above a non-technical job.
• Merged open source PRs count. Link them and say what changed ("fixed a race in the cache invalidation path, merged into v2.4").
• Non-technical jobs (retail, food service) can stay as one line each to show reliability, below your technical sections.
• A small tool you built for a club, a lab, or a part-time job counts as a project with users. Say who used it and how often.

For a full layout built around projects, see the entry level resume example with no internship, and the longer resume with no experience guide.

List 3 to 6 languages you could use in a coding interview, then the frameworks and tools that match the job, grouped on two or three labeled lines. Every item should appear in at least one bullet above it; a skill that shows up only in the list is easy for an interviewer to probe and hard for you to defend.

• Order by the job. For a backend role, lead with Go or Java and SQL. For a frontend role, lead with TypeScript and React.
• Cut filler: Microsoft Office, "problem solving", HTML listed as a programming language, and anything you used once in a lab.
• Don't split skills into "proficient" and "familiar" unless the posting asks. If you are only familiar with something, it probably belongs off the list.
• Skip proficiency bars or percentages. They don't parse well and nobody knows what 80% Python means.

• Graduation date missing or vague. "2023 - Present" makes a recruiter guess whether you fit the role.
• Opening with an objective ("Motivated CS student seeking..."). It says nothing the role title doesn't.
• Bullets that only list the stack instead of what you built and what changed.
• A coursework list of 12 classes, including intro courses.
• Two pages. New grad resumes fit on one; if yours doesn't, cut weaker projects first.
• Two-column or graphic templates that some applicant tracking systems read out of order.
• Broken GitHub or portfolio links, or repos with no README.
• Claiming team results as your own. Interviewers will ask what you did; write the bullet so the answer matches.

These are hard to spot on your own page. Your university career office will review it for free, and how to get your resume reviewed by a recruiter explains other options.

Run through this list before each application batch:

• ✓One page, one column, standard headings: Education, Experience, Projects, Technical Skills.
• ✓Expected graduation month and year on the Education line, matching the posting's window.
• ✓GPA shown only if 3.5+ (or requested), with the /4.0 scale.
• ✓4 to 6 upper-level courses, no intro classes.
• ✓Most recent internship has 3 or 4 bullets with numbers, and a return offer line if you have one.
• ✓Two or three projects, stack in the title line, links that work.
• ✓Every listed skill appears in at least one bullet.
• ✓No summary, objective, photo, or skill bars.
• ✓Exported as a text-based PDF; paste it into a plain-text editor and check the reading order.
• ✓File named like maya-chen-resume.pdf, not resume_final_v7.pdf.

When it's ready, upload your draft below to get a full check and move it into a clean single-column template.