How to Put Personal Projects on Your CV (With Clear Examples)

A project can give an employer concrete evidence of what you can do, even if it was completed for a class, for yourself or as volunteer work. The key is to describe the work clearly and honestly—not to make an independent project sound like a job you never held.

When to include a personal project on your CV

Include a project when it helps demonstrate skills or knowledge relevant to the role. It can be a software tool, design portfolio, research assignment, blog, community initiative or other substantial piece of work. University career guidance also recognises class projects, independent projects, volunteering and other unpaid work as possible evidence of experience.

A project is most useful when you can explain your own contribution and connect it to what the employer is seeking. A long list of unrelated hobbies is less helpful than one or two relevant examples.

Where the project section belongs

Use a heading such as Projects, Relevant Projects or Selected Projects. If you have limited paid experience, place relevant projects near your education or experience so they are easy to find. If you already have substantial directly relevant employment, keep that evidence prominent and include only projects that add something new.

Keep the rest of the CV readable and tailor the selection to each application. A project does not need to be paid to be worth including, but its unpaid or independent context should be clear.

What to write for each project

For each entry, include the information a reader needs to understand the work:

• Project name and, if useful, a short description.
• Context: personal, academic, volunteer, freelance or team project.
• Dates or duration, especially if the work is ongoing.
• Your role: what you personally did, including your part in a team.
• Relevant methods or tools: name only those that matter to the job and that you can discuss confidently.
• Evidence of the result: a deliverable, finding, audience, improvement or other verifiable outcome.

Write a few concise bullets rather than a block of prose. Start with an action and explain what you did, how you did it and why it mattered. This is more informative than simply writing “good communication skills” or “experienced in Python.”

A simple bullet-point pattern

Action + what you made or changed + relevant method + result or purpose

For example:

Built a responsive portfolio site using HTML, CSS and JavaScript; organised six design projects into case studies so prospective clients could review the work.

That example is useful only if it accurately describes the project. Replace the details with your own facts; do not borrow its numbers or imply that the site generated clients unless you can verify that.

Make the description specific without inventing impact

If you have a reliable number, use it to give scale: the size of a team, number of users, pages researched or time saved. If you do not have a trustworthy measure, describe the completed output instead. “Created a prototype and documented three user-testing findings” is stronger than an unsupported claim that it “transformed the business.”

For team projects, distinguish the group’s result from your individual contribution. Say “worked with a four-person team” or “implemented the search interface,” rather than claiming sole ownership of work you shared.

If the project is live, a link to a portfolio, repository or published work can help. Check that the link works and does not reveal private information, confidential client material or credentials. Be ready to explain your decisions and answer questions about anything you list.

Tailor your projects to the vacancy

Read the job advert and note its main responsibilities and skills. Then choose projects that provide evidence for those requirements. A data-analysis role may call for a research project with a clear method; a front-end role may call for a deployed interface and an explanation of your contribution. Use the employer’s terminology where it genuinely matches your experience, not as a list of keywords detached from evidence.

You do not need to rewrite every project from scratch. Keep a fuller record of your work, then select and adjust the most relevant details for each application.

Common mistakes to avoid

• Presenting a personal or class project as paid employment.
• Listing tools without showing what you used them to do.
• Claiming results or metrics that you cannot substantiate.
• Hiding your own contribution inside a team’s achievement.
• Including every project, regardless of relevance.
• Sharing broken links or confidential material.

A well-chosen project entry gives the employer something specific to assess—and gives you a concrete example to discuss in an interview. Build or update your CV around the role you want, then check that every claim is accurate and easy to verify.

Sources

• National Careers Service: How to write a CV — guidance on tailoring a CV and using projects, volunteering or other experience when work history is short.
• UC Davis Career Center: Resume, CV and Cover Letter Guide — guidance on relevant projects and accomplishment statements.
• University of Pennsylvania Career Services: No Work Experience? Here’s What to Highlight Instead — examples of academic, volunteer and independent project experience.