Resume evidence · Published September 25, 2026
Add projects when they supply relevant evidence your work history does not already prove. Remove them when they merely repeat stronger professional examples.
Put projects on your resume when they demonstrate target-role work that your employment history does not yet show, or when the project itself is a meaningful credential: a deployed product, published analysis, open-source contribution, capstone, competition, or substantial independent engagement. Do not add a Projects section simply because a template has one. If recent paid work already proves the same capability at greater scale, use that space for the stronger evidence.
Label the context honestly—personal, academic, volunteer, freelance, or internal—and describe your contribution, constraints, and result. A project is evidence only when a reader can understand what you actually did.
Run the PROOF-GAP test
Score Proximity, Responsibility, Output, Original contribution, Freshness, and Gap filled.
| Test | Strong signal | Weak signal | |---|---|---| | Proximity | Mirrors core target work | Uses a tool named in the posting but solves unrelated work | | Responsibility | Your contribution is separable | Team outcome with no role clarity | | Output | Deployed, analyzed, tested, published | Tutorial copied step by step | | Original contribution | You made decisions and tradeoffs | Cosmetic variation only | | Freshness | Reflects current ability | Old exercise below present level | | Gap filled | Adds proof absent elsewhere | Repeats a recent job bullet |
Two or three strong projects usually beat a long catalogue. The test is not whether a project was paid; it is whether it supplies credible relevant evidence.
Write projects with employment-grade clarity
Give the project a descriptive name, context, date, and link when the destination is maintained and safe to share. Then write bullets with problem, contribution, method, and result. Quantify only what you measured.
Weak: “Created a machine-learning model using Python.”
Stronger: “Built and evaluated a demand-forecasting baseline on 36 months of public bicycle data; compared seasonal naïve and gradient-boosted models, documented leakage controls, and published the reproducible notebook.”
The stronger version does not invent a business impact. It reveals judgment and an inspectable output. If the project is collaborative, name your part: data cleaning, interface, test design, research synthesis, or deployment. Link to a focused landing page or repository README rather than an unexplained folder.
Worked example: one project, two candidates
Elena is graduating in computer science. Her accessible transit-map project demonstrates API integration, geospatial data handling, user testing, and deployment—capabilities absent from her part-time retail work. She places Projects above unrelated employment and includes two precise bullets plus a live link.
Omar has five years building production mapping systems. He completed the same kind of side project recently, but his work history already proves larger-scale integration and accessibility ownership. On his resume, the side project duplicates stronger evidence. He omits it unless the project shows a new target capability, such as an unfamiliar mobile stack he is moving toward.
The project's intrinsic quality did not change. Its marginal proof value changed with the candidate's record.
Protect confidentiality and avoid tutorial inflation
Never publish client data, internal screenshots, source code, credentials, or results you do not have permission to share. A sanitized project description can still explain the problem, constraints, your decisions, and a non-confidential outcome. If even that would violate an agreement, choose another example.
Tutorials can support learning, but completion alone rarely differentiates. State what you extended, tested, redesigned, or discovered beyond the instructions. A course capstone should be labeled as such; do not present it as client employment.
- Remove secret keys and personal data from repositories.
- Write a README explaining problem, decisions, and limitations.
- Test every portfolio link while logged out.
- Distinguish team outcome from individual contribution.
- Archive broken demos or provide a stable case study.
- Be ready to explain tradeoffs, not only tools.
Choose placement and retire projects deliberately
Graduates and career changers can place high-value projects before unrelated work. Experienced applicants often put a compact Projects or Selected Work section after professional experience, unless the project is the clearest evidence for the new target. Projects completed inside employment normally belong under that role so context remains clear.
Review the section every few months. As paid or higher-stakes evidence grows, retire beginner exercises. Preserve a fuller portfolio elsewhere, but keep the resume selective. If a project link breaks or the underlying tool becomes obsolete, update the case study to emphasize durable decisions—or remove it.
The section succeeds when each item answers a hiring question that would otherwise remain open. Once it no longer closes a proof gap, it has completed its job.
Sources and scope
- U.S. Department of Labor: Resume Essentials Participant Guide (2026) — Current workbook covering targeted resumes, evidence, transferable skills, and special career situations.
- CareerOneStop Resume Guide: Work experience — Guidance on relevant duties, accomplishments, job language, and evidence in work history.
- O*NET OnLine — U.S. Department of Labor-sponsored occupation profiles covering tasks, skills, technologies, education, and work context.
Project expectations differ by occupation. This guide treats projects as supporting evidence, not a guarantee of equivalence to professional experience, and requires truthful context and contribution labels. Editorial review: September 6, 2026.
Take the next useful step
List your target role's three hardest-to-prove capabilities, map each to work evidence, and keep only projects that close a remaining gap.
- Resume Section Checker
- Resume Bullet Point Generator
- Resume Section Order for Graduates, Career Changers, and Experienced Professionals
- Job Description to Resume Mapping
- Resume Readability Score
- Start Free
Questions readers usually ask
How many projects should be on a resume?
Use the smallest set that proves missing target capabilities—often two or three. Quality and distinct evidence matter more than count.
Do personal projects count as experience?
They count as project evidence, not automatically as employment. Label them honestly and explain scope, contribution, and output.
Should I include GitHub links?
Yes when the repository is readable, safe, maintained, and helpful. A focused README or case study may be stronger than a raw profile.
Can I include confidential work projects?
Only at a level you are authorized to share. Sanitize details or use another example rather than risking client or employer information.