How to Write Projects on a New Grad Resume

Your projects section can make or break your resume as a new grad. Here's how to write project descriptions that recruiters actually read — with STAR structure, quantification, and real before/after examples.

Why Projects Matter for New Grads

When you don't have years of work experience, recruiters look at your projects to assess whether you can actually code. A well-written projects section shows:

Technical competence — You can build real things, not just pass exams
Problem-solving ability — You identified a problem and built a solution
Initiative — You went beyond coursework requirements
Tool/tech exposure — You've used languages, frameworks, and tools in practice

The 3-Part Project Description Formula

Every project on your resume should have three components:

Project name + tech stack — One line. Example: "Campus Marketplace | React, Node.js, PostgreSQL"
Context (what + why) — One sentence of context. What does the project do? Why did you build it?
Bullets (STAR + quantified) — 2-4 bullets describing your specific contributions with results.

STAR Method Applied to Projects

Situation

What problem existed? What was the context?

Task

What needed to be done? What was your role?

Action

What did you specifically do? What tools did you use?

Result

What happened? Use numbers: users, %, time saved

Quantification: The Difference Between Generic and Strong

Numbers turn vague claims into concrete evidence. Here's the difference:

❌ Weak

Built a chat application using WebSockets

✅ Strong

Built a real-time chat app using WebSockets supporting 200+ concurrent users with <50ms message delivery latency

❌ Weak

Optimized database queries to improve performance

✅ Strong

Optimized PostgreSQL queries by adding composite indexes, reducing average query time from 2.1s to 180ms for 50k+ row tables

Even if you don't have exact numbers, estimate honestly. "Served 500+ users" is better than "many users." "Reduced load time by ~40%" is better than "improved performance."

Action Verbs to Use

Start every bullet with a strong action verb. Here are the most effective ones for software engineering projects:

DevelopedBuiltDesignedImplementedEngineeredArchitectedOptimizedReducedImprovedAutomatedIntegratedDeployedMigratedRefactoredScaled

Common Mistakes

"Worked on" or "Helped with" — Too vague. Say exactly what you did.
Team project without your role — "Built as part of a 4-person team" is meaningless. Specify what YOU built.
Too many projects — 3-5 detailed projects beat 8 one-liners.
No GitHub link — If the code is public, link it. Recruiters do click through.

All examples on this page are fictionalized for educational purposes.

Analyze Your Bullets with STAR Tool →

Paste your bullets and get instant feedback