DevsUnite Logo
devsunite
Free template, no signup to read

New grad software engineer resume example

This new grad software engineer resume example is built for a final-year student or recent graduate applying to a first full-time role.

The sample belongs to Marcus Bell, a fictional computer science graduate with two internships. Education sits at the top because it is recent and relevant; internships follow with concrete results.

Sample: Computer science new grad with two internships. Classic template. Marcus Bell is a fictional person.

Marcus Bell

New Grad Software Engineer

Education
B.S. in Computer Science, GPA 3.7
Pinecrest University (fictional)Seattle, WA
  • Relevant Coursework: Distributed Systems, Algorithms, Operating Systems, Compilers, Computer Networks.
Experience
Software Engineering Intern
Cobalt Cloud (fictional)Seattle, WA
  • Added cursor pagination and a Redis cache to a Spring Boot inventory service, cutting load time from 2.1 s to 0.6 s.
  • Wrote the design doc, presented it in review and rolled the change out behind a feature flag with no rollbacks.
  • Added load tests with k6 to the CI pipeline so latency regressions over 10% fail the build.
Software Engineering Intern
Harbor Analytics (fictional)Portland, OR
  • Built a Python validation step for a nightly ETL pipeline that caught 3 malformed vendor files in its first month.
  • Migrated 20 internal reporting jobs from cron scripts to Airflow DAGs with retries and Slack alerting.
  • Reduced a slow SQL report from 4 minutes to 25 seconds by rewriting joins and adding two composite indexes.
Projects
Raft key value store
Go
  • Implemented Raft in Go (leader election, log replication, snapshots) for a replicated key value store.
  • Passed 100% of the course's fault-injection tests, including partitions, message loss and node restarts.
  • Wrote a linearizability checker for client histories and used it to find and fix two stale-read bugs.
Campus Eats, dining hall finder
Kotlin, Firebase
  • Built an Android app listing open dining halls with live menus, used by 800 students in its first term.
  • Scraped menus with a scheduled Cloud Function and cached them in Firestore to keep the app usable offline.
  • Kept a 4.7 rating on the campus app store with crash-free sessions above 99.5%.
Skills
LanguagesJava, Python, Go, C++, Kotlin, SQL
Web TechSpring Boot, Flask, REST APIs, gRPC
DatabasesPostgreSQL, Redis, Firestore
DevOps & InfraDocker, AWS (EC2, S3), Airflow, Linux
ToolsGit, GitHub Actions, k6, IntelliJ
Coding Profiles
LeetCode400+ problems solved, contest rating 1850
AwardsDean's List (6 quarters), 2nd place at a 300-person university hackathon
Sample resume. Marcus Bell is a fictional person and every detail is made up for illustration.

Read Marcus Bell's matching cover letter: New grad software engineer cover letter example

How a new grad resume differs

New grad hiring compares candidates with similar degrees, so the deciding details are internships, the depth of your projects and how clearly you describe your own part in team work.

  • Lead with Education while you are a student or within a year of graduating.
  • Include GPA when it is 3.5 or higher, otherwise leave it out.
  • Describe internships like jobs: what you built, how, and the measurable result.
  • Pick projects with real complexity (a distributed system, a compiler, an app with users) over tutorials.

New grad software engineer resume, section by section

Marcus's resume opens with his degree, GPA and the coursework that matches backend and distributed systems roles. Both internships get three bullets: the change he shipped, how he proved it was safe (a design doc, a feature flag, load tests) and the measurable result.

His projects are the kind interviewers ask about: a Raft key value store with fault-injection tests and an Android app with real users. The last line combines his LeetCode record and awards, which signal practice and initiative without taking a full section.

How to write each section of your resume

Every sample on these pages uses the same five blocks, in the order recruiters scan them. Keep the section names standard so an ATS files each one correctly.

  • Header: name, phone, city, email, and two or three links (LinkedIn, GitHub, portfolio). No photo, no date of birth, no full street address.
  • Education: degree, school, years, and one line of relevant coursework. Add GPA only when it is strong. Students and new grads put this first; experienced engineers move it to the end.
  • Experience: role, company, location and dates on one line, then three bullets. Each bullet says what you built, with which tools, and what changed because of it.
  • Projects: name with a link to the code, the stack, and three bullets written like job bullets. Pick projects with real users, real data or real complexity.
  • Skills: grouped rows (Languages, Web Tech, Databases, DevOps and Infra, Tools, Others) using the exact names job descriptions use. Add a Coding Profiles line if your practice record is strong.

Weak vs strong resume bullets

A strong bullet follows one pattern: action verb, what you built, the tools, and a result someone can measure. Compare the pairs below; the strong versions are the style every sample on this page uses.

  • Weak: Worked on the backend. Strong: Built a shipment tracking API in Go and PostgreSQL serving 40 internal clients at a p95 latency under 120 ms.
  • Weak: Responsible for testing. Strong: Raised unit test coverage on the billing module from 41% to 78% with Jest before a major refactor.
  • Weak: Made the website faster. Strong: Cut dashboard load time from 2.1 s to 0.6 s by adding pagination and a Redis cache.
  • Weak: Helped the team with deployments. Strong: Moved nightly batch jobs to scheduled containers on Kubernetes, reducing monthly cloud spend by 18%.

Common software engineer resume mistakes

Most rejected resumes are not missing skills; they hide them. Check yours against this list before you apply.

  • Two-column layouts, tables, text boxes or skill bars that ATS software cannot read in order.
  • Bullets that list duties (responsible for, worked on) instead of results.
  • A long skills list with tools you used once. Recruiters ask about every item in interviews.
  • No links, or links to empty GitHub profiles and unfinished repositories.
  • Spelling a technology differently from the job description (Postgres DB vs PostgreSQL), which can cost you the keyword match.
  • Sending the same resume to every job. Reorder bullets and skills for each posting, then check the match with an ATS resume checker.

New grad software engineer resume template

This example uses the Classic template: centered header, ruled section titles and one column, which is the format most new grad hiring teams expect and every ATS parses cleanly. Use this template opens the same layout in the Resume Builder, ready to fill with your own details.

More software engineer resume examples

Frequently asked questions

Should a new grad software engineer resume be one page?
Yes. One page is the norm for new grad roles, and recruiters reviewing hundreds of applications expect it. Cut older or weaker projects before shrinking the font.
Where can I find a good software engineer resume sample for new grads?
The sample on this page is one. It follows the structure most new grad hiring teams expect, and you can open it as a template. The other examples on DevsUnite cover entry level, senior and embedded roles.
How do I use this new grad software engineer resume template?
Click Use this template. You sign in or create a free DevsUnite account, the Resume Builder opens with the same layout, and you fill it with your own resume or start blank. You can download it as a PDF that ATS software reads top to bottom.
Is the person on this resume real?
No. Every name, company, school, number and link on these sample resumes is made up for illustration. Use the structure and the kind of detail, then replace everything with your own real experience.