Resume writing guide
Projects on a Resume: Select Evidence and Explain Your Contribution
Put projects on a resume when they provide relevant evidence that the rest of your experience does not show clearly. A useful project entry explains the problem, your contribution and how you checked the work. It also identifies whether the project was personal, academic, volunteer or employed work, and whether it was completed or remains a prototype.
Select a project for the target task
Compare the vacancy with two or three possible projects. Choose the one that demonstrates the work the employer needs, not automatically the most elaborate or recent project. A small, explainable project can provide stronger evidence than a large team result whose ownership is unclear.
An original selection exercise
Target: an operations role requiring process documentation. Candidate options: a personal travel blog, a volunteer event handover guide, and a class presentation unrelated to operations.
Selection: the handover guide, if the candidate can explain the process they documented and how a volunteer checked it.
Reason: it demonstrates the required work directly. The travel blog may be more visually polished but is less relevant to this particular task.
Personal project: show what exists and how you checked it
Personal work belongs in a Projects section when it is relevant. Avoid calling an experiment a business or claiming users you do not have. The following original sample is fictional.
Fictional personal-project entry
Neighborhood Walk Map | Personal project | May–July 2026
“Created a map of self-researched walking routes with distance notes and access observations.”
“Checked the route descriptions against repeat walks and recorded sections needing a current-condition check.”
“Published a small prototype for personal use; no public-user or accessibility-certification claim.”
The project demonstrates organization and checking. If applying for a mapping role, add the actual tools and methods you used; if applying for writing work, emphasize the clarity of the descriptions.
Team project: identify the part you owned
A team title does not show an individual contribution. Name the group context and your work within it. Do not claim that you led the project merely because you completed a substantial component.
Fictional academic team entry
Community Event Feedback Study | Research methods course | January–April 2026
“Worked in a four-person course team to design and evaluate a practice feedback survey.”
“Drafted the open-ended questions and reviewed pilot responses for ambiguous wording.”
“Wrote the limitations section explaining the small convenience sample; classmates completed the visual summaries and final presentation.”
This was a course exercise. It should not be presented as commissioned research or a representative community survey.
Workplace project: decide whether it belongs under the job
When the project was part of your employment, it often fits naturally under that role. A separate Projects section can be useful for a portfolio-heavy application, but avoid repeating the same bullets twice.
Fictional employed-project bullet set
Under the relevant job: “Mapped the supplier-request handoff with operations and finance, identifying the approval point and missing-document path.”
“Prepared a revised checklist for the manager’s review and tested it against sample requests.”
If the checklist was only proposed, say proposed. Do not write “implemented across the business” unless that happened and you can explain your role.
Use a five-part evidence note before drafting
Write a private note with the project purpose, context, your contribution, validation and current status. Then select the parts that matter to the vacancy. Include dates and a descriptive title so the reader can place the work.
Validation might mean tests, review feedback, a comparison with source records or a documented limitation. It does not have to be a dramatic business metric. If you cannot explain how a claimed improvement was measured, use a more precise description of the work instead.
Check links and permissions
Use a working portfolio or repository link when it adds useful evidence. Check that a reviewer can access the intended material and that it supports your description. Remove secrets, personal records and material you are not permitted to share.
Prepare to explain one decision and one limitation. A project entry should start a useful conversation about your work, not conceal uncertainty behind a long tool list. Keep older projects only when they still provide relevant evidence.
Questions, answered
Can an unfinished project go on a resume?
Yes if it is relevant and has meaningful work to show. Label it in progress or prototype and describe what is complete. Do not claim outcomes that depend on unfinished work.
Should every project have a numerical result?
No. A clear contribution, tested behavior or documented review can be useful evidence. Use numbers only when they are accurate and help explain scope or results.
Sources and examples
ResumizeAI team. Examples are fictional teaching material, not customer results. Replace sample details with your own facts.
Your experience. A complete resume.
Build in Resumize with ATS-friendly templates, guided editing and a live preview. Start free, then upgrade when you need more.
Free account required. Free-plan PDF exports include a watermark.