How to List Projects on a Resume: Coursework, Side Projects, OSS, Bootcamp, Portfolio
Projects can carry as much weight as jobs when framed well. Learn where to place them, how to title academic and bootcamp work, and how to list open source without drowning in links.
Key takeaways
- •Use a Projects section when work is relevant and not fully captured under Experience.
- •Each project needs: name, role, tech or method, one or two outcome bullets, dates optional but helpful.
- •Coursework projects belong under Education or Projects — not both — unless one is summary and one is detail.
- •Open source: link to repo or PRs; name the impact (users, contributors, merge rate) when possible.
- •Cut portfolio filler that doesn’t match the target role.
When to add a Projects section
Add one when you have proof that doesn’t fit cleanly under a job: capstones, OSS, apps you shipped nights and weekends, research builds, or competition work. Skip it if Experience already tells the story.
Placement: above or below Experience
| Profile | Placement |
|---|---|
| Student / new grad with strong builds | Projects can sit above Experience if they’re the best evidence |
| Bootcamp career changer | Capstone + OSS under Projects; pair with any internship or contract in Experience |
| Mid-career with a few side proofs | Keep Projects short, after Experience — only top 2 relevant builds |
Line format that reads like real work
For each project: title (specific, not 'Python project'), your role, tools, and 1–2 bullets with outcomes.
Weak vs strong project line
Before
Todo app — Python
After
Task API (FastAPI, PostgreSQL) — personal project, 2024 • Deployed on AWS; added auth and rate limiting; ~500 test users in beta feedback round
Coursework and bootcamp capstones
Rename for outcomes: 'Full-stack capstone: scheduling tool for clinics' beats 'Bootcamp final'. Mention program name once in Education; let the project entry focus on impact.
Open source and community work
- Link GitHub once — not after every bullet
- Quantify: commits merged, issues triaged, release you shepherded, download growth
- If contribution was small, say so accurately: 'Documented API; 12 PRs merged'
Portfolio alignment
The resume teases; the portfolio proves. Repeat the one-line value prop on both so interviewers connect them. For NDA-heavy work, describe project type and tech without naming the client.
Projects checklist
- ✓Each listed project matches keywords or skills from the target job
- ✓Stack or methods are explicit for technical roles
- ✓At least one bullet per project has a metric, user, or scope signal
- ✓Links work and match what you discuss in interviews
- ✓No duplicate entries under Education and Projects unless clearly different angles
Run MatchResume on your resume
Get an instant match score and actionable improvements. Upload your resume, paste the job description, and close the gap.
Get started freeFrequently Asked Questions
Where should projects go on my resume?
Below Experience is typical. Students and bootcamp grads may place Projects above Experience if projects are the strongest proof. Keep one clear section — don’t scatter the same project across three places.
Should I list school assignments?
Only if they mirror real work: scope, constraints, metrics, tech stack. Rename from 'CS 301 Final' to something outcome-driven, with course name in parentheses if needed.
How do I list open source contributions?
Treat like work: project name, org or repo, dates, stack, bullets on merges, issues closed, adoption, or performance gains. Link once in header or line item.
What about unfinished projects?
List if there’s shippable value (beta users, working demo). Label status honestly — 'in progress' is fine for early career; senior candidates should emphasize completed impact.
Do projects replace work experience?
They supplement — rarely replace paid experience entirely. For first roles, strong projects plus internships beat empty Experience. For mid-career, keep projects short and highly relevant.
Related Articles
How to List Certifications on a Resume: Placement, Expiration, and ATS-Friendly Wording
Certs can boost ATS match and trust — if listed cleanly. Learn where to put them, how to handle expired licenses, how to show role relevance, and the exact line format parsers read well.
How to Make a Resume Stand Out Without Gimmicks
Practical tips to make your resume stand out: tailor to the job, quantify impact, use strong action verbs, align keywords for ATS, and follow a 10-point checklist.
How to List Freelance Work on a Resume
Freelance experience counts — but only if it's presented clearly. Learn how to list contract work, self-employment, agency gigs, and side projects so they read as professional credentials, not filler.