How to Write Projects on a Resume That Actually Get Noticed

For new grads, the Projects section decides whether you get an interview. Here's the structure that passes ATS screens and catches recruiter attention — with real before/after rewrites.

Why Projects Matter More Than You Think

A recruiter spends about 6 seconds on a first scan. For a new grad resume, they're looking for one thing: can this person build software? Your degree says you studied it. Your projects are the only proof you can do it.

Yet most new grad projects sections waste that opportunity with descriptions like "A web app for managing tasks" — which describes the app, not you. Recruiters don't care what your app is. They care what you did and how well it worked.

The Structure of a Strong Project Entry

Each project needs exactly four elements:

1. Name + stack: "Splitwise Clone — React, Node.js, PostgreSQL, Redis"
2. Link: GitHub repo (clean README) or live demo URL
3. 2–4 achievement bullets: what you built + how well it works
4. Scale signals: users, data volume, performance numbers, test coverage

Writing Bullets: The Before/After Test

Every bullet should pass this test: does it contain an action AND a result? Compare:

Example 1 — Web App

• ❌ Before: "Made a recipe sharing website where users can post recipes"
• ✅ After: "Built a recipe-sharing platform with full-text search and image uploads, serving 300+ registered users with sub-200ms API responses"

Example 2 — Algorithm Project

• ❌ Before: "Implemented sorting algorithms in Java for class assignment"
• ✅ After: "Benchmarked 5 sorting algorithms on 1M-element datasets in Java; hybrid quicksort implementation ran 34% faster than standard library sort on partially sorted data"

Example 3 — Team Project

• ❌ Before: "Worked in a team of 4 to build a mobile app"
• ✅ After: "Led backend development of a 4-person Flutter app; designed REST API with JWT auth handling 15 endpoints, documented with OpenAPI"

Notice the pattern: strong verb, specific tech, concrete scale. Paste your own bullets into the STAR Bullet Analyzer to get this rewrite done for you.

Where to Find Numbers When You Have "No Users"

Personal projects feel unquantifiable. They're not. Measure what's measurable:

• Performance: response time, load time, memory usage, algorithmic complexity
• Scale: records in the database, requests handled in load testing, lines of code, test coverage %
• Scope: number of endpoints, components, features shipped, pages
• Reliability: uptime if deployed, error rates in testing

Run a load test with a free tool, get real numbers, put them on your resume. "Load-tested to 500 req/s" beats "fast backend" every time.

How Many Projects?

2–4. More than 4 dilutes attention; fewer than 2 looks thin. Order by impressiveness, not chronology. Your best project goes first — recruiters may not read the third.

Common Project Section Mistakes

• Tutorial clones without modification — if you followed a tutorial, extend it in a way you can describe as your own work
• Describing features instead of achievements — "has login and dark mode" vs. "implemented JWT auth with refresh token rotation"
• No links — a project without a GitHub link reads as unverifiable
• Dead repos — pinned project repos should have a README with screenshots and setup instructions
• Listing every class assignment — only include work you'd be excited to discuss in an interview

Projects vs. Experience: Where Do They Go?

If you have internship or work experience, Projects goes below Experience. If you don't, Projects goes at the top — see our no-internship resume guide. Either way, use the same bullet rules.

Final Check

Run the finished resume through the ATS Resume Checker to confirm your Projects section is detected correctly and your keywords register. Then grab a matching layout from our free templates.