How to put projects on a resume: three worked examples
Turn coursework, personal projects, and team contributions into a clear resume projects section, with before-and-after bullets and an evidence worksheet.
All candidates, projects, and results below are fictional teaching examples. Replace them with work you actually did and can explain. No template guarantees an interview.
Choose the project that answers the job's question
A projects section helps when your paid experience does not yet show a skill the role needs. A course assignment, independent build, or volunteer deliverable can supply that evidence. Start with the requirement, then choose the work that lets you demonstrate it: a data-cleaning task for an analyst role, an error-handling feature for a development role, or a documented handoff for an operations role.
UC Davis recommends identifying the project, course or department, dates, and accomplishment statements. The examples here add an evidence check: what did you personally produce, what can you show, and what would be overstating the result? Two specific bullets can answer those questions more clearly than a long list of tools.
Example 1: a class analysis with a limited conclusion
Fictional context: Mina completed an individual statistics assignment using a public bike-share dataset. She cleaned duplicate records, compared weekday and weekend trip duration, and wrote a notebook explaining missing-data exclusions. She did not work for the bike-share operator or change its business results.
Entry heading: Bike-share trip analysis | Statistics coursework | March–April 2026. Before: Analyzed transportation data using Python. After: Cleaned duplicate trip records in pandas and documented missing-duration exclusions before comparing weekday and weekend trip lengths.
Second bullet: Presented the comparison in a reproducible notebook with charts and a limitations section covering excluded records and seasonal coverage. This gives an interviewer something concrete to discuss without claiming the analysis improved city transportation.
Example 2: a personal build without invented users
Fictional context: Omar built a recipe-cost planner for his own use. It imports ingredient prices from a manually maintained CSV and flags missing prices. It has no public customer base, revenue, or measured time savings.
Entry heading: Recipe-cost planner | Independent project | May–June 2026. Before: Created an innovative app that saves users time. After: Built a JavaScript recipe-cost planner that reads ingredient prices from CSV and identifies missing prices before calculating a recipe total.
Second bullet: Added sample files and setup instructions so another developer can reproduce the calculation locally. A working demo and readable README can support this claim. A private prototype is still useful evidence; describe it as a prototype instead of implying a commercial launch.
Example 3: separate team scope from your contribution
Fictional context: Elena joined a three-person volunteer project to organize a community group's equipment requests. Another volunteer built the form. Elena designed the tracking sheet and wrote the handoff instructions. The group used the process for one event, with no reliable before-and-after performance measure.
Entry heading: Equipment-request handoff | Volunteer team project | August 2026. Before: Led development of an equipment management platform. After: Designed a request-tracking sheet with owner and pickup-status fields for a three-person volunteer team, then wrote the handoff checklist used during one community event.
Here, team size and one-event scope describe what happened; they are not an impact metric. Do not turn a shared deliverable into sole ownership or rename a spreadsheet as a platform to sound more senior.
Build an evidence ledger before polishing the wording
Use one row per claim. Keep the ledger in your notes; the resume only needs the strongest relevant facts. If the evidence is unavailable or confidential, narrow the claim and explain the work without publishing restricted material.
| Claim | Evidence to keep | Boundary to state |
|---|---|---|
| Cleaned and compared trip records | Notebook, data source, cleaning notes | Coursework; no operational outcome measured |
| Built ingredient-price validation | Code, sample CSV, missing-price example | Personal prototype; no customer metrics |
| Created the volunteer handoff sheet | Permitted blank template and checklist | Owned the sheet, not the teammate's form |
Place and review the finished section
Use a plain heading such as Relevant Projects. For an early-career application, place it near education or relevant experience according to which evidence best supports the role. Keep substantial paid work in Experience; avoid repeating the same project in two sections. Remove weaker projects as stronger professional evidence becomes available.
Link only to a repository, portfolio, or demo that you are allowed to share and have checked while signed out. A broken link or exposed private data weakens the application. If there is no shareable link, a precise description still works. Prepare to explain the decisions, tradeoffs, and limitations in an interview.
Download the text examples to adapt in your own document, or use the editable worksheet to draft a section. ResumeTurtle's public resources are available now; the account workspace remains in prelaunch.
- Name the project type and dates accurately.
- Choose actions you personally performed and tools you actually used.
- Use measured results only when you can explain the baseline and calculation.
- Check the employer's file-format instructions and review the exported resume.