Resume Project Examples: 20+ Ways to List Projects (Students & Developers)
Table of contents
Projects are the only section of a resume where you control the brief. No manager decides the scope, no job title limits the claim — you show exactly what you can do, at whatever scale you can prove.
Here is how to list them: three formats to choose from, 24 worked examples across technical and non-technical fields, the four details that make a project credible, and how to write about work that never had a job title attached to it.
What makes it credible
The four details every project entry needs
| Detail | Question it answers | Example |
|---|---|---|
| What it does | Is this relevant to my opening? | 'A habit tracker with offline sync' |
| Who uses it / the scale | Is it real, or a tutorial? | '1,400 active users; 2M events a day' |
| The stack or method | Which of my keywords does it contain? | 'TypeScript, Next.js, Postgres' |
| The result or link | Can I verify this in one click? | 'live demo + repository, 96% test coverage' |
Formatting
Three ways to format a projects section
1. Compact — one line per project
Use when projects support a strong work history rather than carrying the resume. Three lines total, no bullets.
Lumen — real-time analytics dashboard · TypeScript, Next.js, Postgres · live: lumen.example.com
2. Standard — two or three bullets per project
The default for students, career changers and anyone whose projects are a primary qualification. Keep each project to five lines maximum.
Standard project entry
Inventory API — Personal project 2025 – Present Go · PostgreSQL · Redis · Docker · github.com/you/inventory-api · Built a REST API handling 40k requests/day with sub-50ms median latency · Wrote 180 integration tests, taking coverage to 86%; deployed via GitHub Actions · Used by two local businesses; reduced their stock-take time by roughly 4 hours a week
3. Case study — a short narrative block
For consultants, designers and senior candidates where the method matters more than the deliverable. One project, four lines, framed as problem → approach → result.
Case study entry
Checkout redesign — Northwind Retail (contract) 2026
Problem: 61% of mobile carts abandoned at the payment step.
Approach: ran 14 user sessions, rebuilt the payment flow as a single screen, tested
with 6,000 users in an A/B test.
Result: cart abandonment down to 44%; roughly £180k of additional monthly revenue.Library
24 project examples by field
Software and data
Scheduling app used by 220 students across two departments — FastAPI, Postgres, Docker, deployed on Fly.io with GitHub Actions CI.
Real users is the strongest signal available to a new graduate.
Open-source CLI that lints Terraform configurations; 1.2k stars, 42 external contributors and a fix that cut startup time 30%.
Open source proves you can work inside someone else's codebase.
ETL pipeline pulling 1.8M rows a day from three APIs into BigQuery, orchestrated with Airflow and documented with dbt tests.
Volume plus tooling — the exact shape data teams hire for.
Interactive sales dashboard covering three years and 1.2M records, rebuilt in Power BI to replace 14 manual spreadsheets.
Time saved is the most transferable analyst outcome there is.
Mobile expense tracker with offline sync (React Native, SQLite) — 3,500 downloads and a 4.6 average store rating.
Store metrics convert a hobby project into evidence.
Machine-learning classifier predicting equipment failure from sensor data; 0.91 F1 on a held-out set of 40k readings.
State the evaluation metric, not just the model name.
Accessibility audit and remediation of a university website — fixed 180 WCAG violations and raised the Lighthouse score from 61 to 98.
Before/after scores are compact and verifiable.
Self-hosted home-lab running 9 services behind a reverse proxy, with automated backups and uptime monitoring at 99.9%.
Infrastructure work counts as experience, documented with real numbers.
Business, marketing and finance
Financial model for a simulated £5M portfolio with a scenario dashboard; used by two classmates for their own coursework.
Adoption — even small — shows the work was good enough to reuse.
SEO audit and content plan for a local charity; organic sessions up from 900 to 4,100 monthly in five months.
Volunteer projects generate real, citable metrics.
Market-entry analysis for a fictional coffee brand: TAM, five-competitor review and a pricing model in Excel and Google Slides.
Case competitions and coursework count when you name the deliverables.
Cost-reduction study across 40 SaaS subscriptions for a student society, identifying £1,900 of annual savings.
Even small money is still money — the method is what matters.
CRM rebuild for a 3-person freelance agency: pipelines, automations and a reporting dashboard in HubSpot's free tier.
Unpaid systems work is legitimate experience for operations roles.
Freelance social media management for two small businesses; grew one account from 1.1k to 14k followers in five months.
Freelance is professional work — list it under experience, not projects.
Design, research and creative
End-to-end UX case study for a food-delivery app: 12 interviews, wireframes, a prototype and usability tests with 8 participants.
Say how many people you tested with — that is the credibility number in UX.
Brand identity system for a community sports club: logo, type scale, signage and a 24-page usage guide.
Name the deliverables; 'branding' alone is too vague.
Short documentary filmed and edited solo — 18k views and used by a local charity in its fundraising campaign.
Distribution and reuse are the outcomes that make creative work count.
Longitudinal research study on remote-work habits with 120 participants; findings presented at a university symposium.
An academic presentation is a real, verifiable outcome.
Six-part illustration series sold as prints, exceeding a £1,200 funding goal on a crowdfunding platform.
Revenue is the clearest creative proof there is.
Education, healthcare and operations
Designed and ran a six-week numeracy intervention for 14 pupils; average progress of 1.6 sub-levels against a 0.8 target.
Teaching projects become impressive when you report the cohort and the target.
Authored a 12-lesson media-literacy unit adopted by three colleagues in the same department.
Adoption by peers shows the quality reviewers respect.
Quality-improvement project reducing sample rejections in a hospital lab from 6.4% to 1.9% over four months.
Clinical QI work is project-shaped; give it numbers.
Community first-aid workshop delivered to 45 attendees across two sessions, with post-session confidence scores rising 38%.
Survey results turn volunteering into evaluable work.
Rebuilt a volunteer rota covering 60 shifts a month, cutting no-shows from 22% to 6%.
Operations improvements in volunteer organisations are real projects.
Placement
Projects, freelance work or experience?
| The work | Where it belongs | Why |
|---|---|---|
| Paid freelance or contract work | Work Experience | It is employment. Invoicing clients is a job, however small |
| Unpaid but ongoing and client-facing | Work Experience with 'Volunteer' or 'Pro bono' noted | Duration and responsibility are what make it experience |
| Personal, academic or open-source builds | Projects | Self-directed work reads as initiative here, not padding |
| Coursework with a concrete deliverable | Projects | Only if it produced something a stranger could evaluate |
| Hackathons and competitions | Projects (or a one-line Awards section) | Competitive results carry weight; participation does not |
| Internal tooling built at a previous job | Inside that role's bullets | It is an achievement within employment, not a side project |
- Put projects above experience for students, career changers and bootcamp graduates — the strongest evidence has to be reachable without scrolling.
- Put projects below experience once you have two or more relevant roles, and cut it to two entries.
- Never mix projects into the middle of employment history; it breaks the timeline a recruiter is reconstructing.
- Give every project a date range or a year. Undated work looks either ancient or invented.
Fix these
Six project mistakes that cost interviews
Weak
Built a personal project to learn web development and improve my coding skills.
Stronger
Built and deployed a recipe-sharing app (React, Node, Postgres) — 1,400 users, 2M page views, loads in under 1.2s on mobile.
Why: the rewrite gives scale, stack and a result — three facts instead of an intention.
Weak
Used machine learning to analyse a dataset for a university module.
Stronger
Trained a churn model on 410k customer records; improved recall from 0.61 to 0.78 by rebalancing classes and adding tenure features.
Why: naming what was hard shows engineering judgement.
Do
- Two or three substantial, relevant projects
- A live link, a repository or a case-study PDF
- Numbers: users, records, latency, revenue, time saved
- Your exact role if you worked in a team
Don't
- Seven tutorial projects listed one line each
- Course titles presented as projects
- No links, no dates, no scale
- 'Contributed to' without saying what you personally built
For technical roles specifically, the software engineer resume guide covers how projects interact with internships, open source and portfolio links, and the bullet point library has the phrasing patterns for the bullets inside each project.
Do it now
Write your project entries in five steps
- 1
Pick two or three, for relevance not volume
Choose the projects that share the most keywords with the job advert, even if a different project was harder.
- 2
Write the title line
Project name, your role, the stack or method, the link and the dates. One line, scannable.
- 3
Add the numbers you can defend
Users, records, latency, downloads, revenue, hours saved, test coverage, before/after metrics. Use 'roughly' where you are estimating.
- 4
Name the hard part
One line on the constraint you solved — a migration, a scaling limit, a conflicting requirement. That is what separates a project from a course.
- 5
Test every link from a phone
A dead GitHub link or a broken demo is worse than no link at all, because it reads as carelessness rather than missing evidence.
Frequently asked questions
How do I list a project on my resume?
Where should the projects section go on a resume?
How many projects should I put on my resume?
What if my projects are personal and not used by anyone?
Should I include university coursework as projects?
About this guide
Hiring and applicant-tracking practices vary by employer and platform, so no format, keyword check or tool can guarantee an interview. Treat example details and metrics as models, not verified outcomes; use only facts you can support from your own experience.
Something out of date or wrong? Tell us — we review suggested corrections and update the guide when appropriate. Last reviewed .
Resume Earth publishes the free tools and guides on this site — read more about who we are and how the tools stay free.
Put this guide to work in 5 minutes
Use these ideas while building your resume, then review the exported file and the suggestions from the checklist before you apply.
Keep reading
Software Engineer Resume Guide 2026
This guide covers ways to present engineering work, projects and technical skills, with examples by seniority and practical layout tips for links and readable text.
200+ Resume Skills Examples for 2026
Browse skill ideas by field, learn how to prioritize relevant strengths, and distinguish demonstrated skills from unsupported self-descriptions.
30+ Resume Bullet Point Examples
Turn duty-led bullets into clearer evidence with a practical formula, examples by function and before-and-after rewrites. Adapt the patterns using your own facts.