How to put projects and coursework on your resume
Give projects their own section near the top. Write each one like a job: state the goal, what you built, the tools you used, and the result with a number. Add relevant coursework only when it maps to the job. Name your role honestly on group work, and keep it to one page.
Where do projects go on a resume?
Give them their own section called Projects, and put it near the top, right under Education. When you have little paid work, projects are the closest thing to real experience you have, so do not bury them at the bottom.
Pick two or three of your strongest. A short, sharp section beats a long list of half-finished work. For each project, include:
- A clear name, plus your role if it was a group project
- One line on what it does and who it was for
- Two or three bullets on what you built and what happened
- The tools and skills you used, named exactly
- A link, if the work lives somewhere a hiring team can see it
How do you write a project bullet that reads like real work?
Use one shape for every bullet: the goal, what you built, the tools, and the result. Lead with the outcome and put a number on it whenever you can, even a rough one.
Notice the scope: a real tool, real users, a real before-and-after. Drop "for my class" and just describe the work. Hiring teams care that you can scope a problem, build something, and explain what changed.
We made a website for our final project and I did a lot of the work on how it looked and how it functioned.
Built a course-scheduling web app in React and Firebase so 40 classmates could swap sections, cutting their planning time from an hour to a few minutes.
How do you talk about group projects honestly?
Name what you personally did. A group project is fair to claim, but the bullet should make your part clear so it holds up when they ask about it in the interview.
Say "Led a 4-person team" or "Owned the backend on a 5-person project," not a vague "we built." If you led, say so. If you handled one slice, name that slice and own it well. A specific, smaller claim beats a big one you cannot back up.
The test is simple: could you walk a stranger through every line for ten minutes? If not, rewrite it until you can.
When should you include relevant coursework?
Add coursework only when it maps to the job and you are short on other proof. It is most useful for new grads applying to technical or specialized roles where the classes signal real skills.
Keep it tight and relevant:
- List four to six courses by name, not your whole transcript
- Pick courses that match the job: "Database Systems," not "Intro to College"
- Put it as one line under Education, not its own big section
- Once you have internships or strong projects, cut it for the space
What counts as a project worth listing?
More than you think. A project is anything where you set a goal, built something, and can speak to the result. It does not need to be assigned, finished, or perfect.
Good sources, if you can explain the work behind them:
- Course and capstone projects, especially team ones with a real scope
- Personal builds: an app, a script, a dataset, a small game
- Hackathon projects, even a 24-hour one, with what you shipped
- Analysis or research you did for a club, a contest, or yourself
- Freelance or volunteer work you built for a real person or group
Mistakes that make a projects section fall flat
A few habits quietly cost interviews:
- Listing the tool but not the result. "Used Python" tells them nothing
- Vague team language that hides what you actually did
- Five tiny tutorial clones instead of two real projects
- A dead or broken link, which reads worse than no link at all
- Claiming a project you cannot explain end to end
Asked.
Answered.
Two or three strong ones. A hiring team would rather see two projects you can explain in depth than six you cannot.
Usually no. Once you have real work to show, use the space for it. Keep a class only if it covers a skill the job asks for that your experience does not.
Yes, if you describe what works today, not what you hoped to ship. "Built the core search feature" is honest. Claiming a finished product you cannot demo is not.