New Grad Software Engineer Resume: Projects and Checklist

Show what you can build and explain

A new-grad software engineer resume should connect languages and tools to working code. Put your degree and graduation date, relevant internships, a small set of substantial projects, and demonstrated technical skills where they are easy to find.

Choose projects you can discuss beyond the tutorial. Be ready to explain a data model, a failure case, a test, and a tradeoff. A small application with clear ownership can provide more interview material than a long list of frameworks.

Example: a fictional campus booking application

Label this kind of work as an academic or personal project. These bullets are illustrative and contain no invented user growth or production scale.

• Built a room-booking API with TypeScript and PostgreSQL; modeled rooms, reservations, and booking owners.
• Added a database constraint and conflict response to prevent overlapping reservations for the same room.
• Wrote integration tests for concurrent booking attempts and unauthorized cancellation; documented local setup and test commands.

Replace technology lists with evidence

“Python, React, Docker, AWS, Kubernetes” gives little context on its own. Group the tools you have used, then make your experience or project bullets show how. If Docker was used only to run a local database, do not imply that you designed a container platform.

For a tutorial project, explain what you changed independently: adding pagination, handling a failed network request, writing missing tests, or replacing a storage layer. Credit the starting tutorial in the repository. A copied starter with a new name is not evidence of original system design.

Review the resume like a code handoff

Open repository links in a signed-out window. Check that the readme explains how to run the code and that screenshots match the current version. Never publish employer code or secrets to support a bullet.

Use measured performance claims only when you can name the benchmark and conditions. “Reduced local query time from X to Y on a fixed test dataset” is narrower and more defensible than claiming to have scaled a classroom project for millions of users.

• Keep degree and expected graduation dates explicit.
• Distinguish internship work, personal projects, and coursework.
• Make your contribution visible on team projects.
• Keep tools you can explain; remove decorative proficiency bars.