Talvio
Beta
Talvio
Beta

How to List Projects on Your Resume (So They Count as Experience)

Where to put a projects section, how to write each entry so it shows your contribution and results, and how to keep it readable for ATS and recruiters.

Published Updated

Projects are one of the most underused sections on a resume. People either skip them because they feel "not real" or dump a list of repo names with no context. Both waste the space. A well-written project entry can carry the same weight as a job, especially when you are early in your career, changing fields, or filling a gap.

This guide covers when projects belong on your resume, where to put them, how to write each entry, and how to keep them readable for applicant tracking systems (ATS) and humans.

When projects deserve a place on your resume

Add projects when they prove something your work history does not. Common cases:

  • You have little or no paid experience. Students, recent grads, and bootcamp finishers often have more relevant evidence in projects than in part-time jobs.
  • You are switching careers. If you are moving from teaching into data analysis, a project where you cleaned and analyzed a real dataset says more than your classroom bullets ever will.
  • Your job title undersells what you did. Sometimes the most relevant thing you built happened inside a role with a generic title. A project entry lets you pull it out and give it room.
  • You have a gap. A project you worked on during time off shows that your skills stayed in use.
  • The role values a portfolio. Design, engineering, writing, marketing, and research roles often expect to see things you have made.

If you already have several years of directly relevant experience, projects usually become optional. Keep one or two only if they show a skill your jobs do not.

Where to put the projects section

Placement depends on what you want the reader to see first.

  • Above experience if projects are your strongest evidence for this specific role. This is common for career switchers and early-career candidates.
  • Below experience if your work history is already relevant and projects are supporting detail.
  • Inside a job entry if the project happened at work. Do not pull work projects into a separate section unless you need the extra visibility, and if you do, make it clear where it happened.

Use a plain heading such as "Projects" or "Selected Projects." Avoid creative headings like "Things I've Built" or "Side Quests." An ATS maps sections by recognizable headings, and a recruiter skimming quickly looks for familiar labels too.

What every project entry needs

A useful project entry answers four questions fast: what it is, what you did, what tools you used, and what happened as a result.

A simple structure:

Project name | Tools or tech | Date or date range | Link (optional)

  • One line on what the project is and who it was for
  • One or two bullets on what you specifically did
  • One bullet on the result, scope, or what it proved

Here is a weak version:

Budget App

  • Built a budgeting app using React

And a stronger version of the same project:

Household Budget Tracker | React, Node.js, PostgreSQL | 2025

  • Web app for tracking shared household expenses, built for a group of four roommates who were splitting bills in a spreadsheet
  • Designed the data model for recurring and one-off expenses, and built the monthly summary view
  • Used weekly by the group for six months; replaced the spreadsheet entirely

The second version gives context, shows decisions you made, and ends with evidence that it worked. It does not invent numbers. "Used weekly by four people for six months" is small, but it is true and specific, and specific beats impressive-sounding.

Write what you did, not what the project is

The most common mistake is describing the project instead of your contribution. "An e-commerce platform with cart and checkout" tells the reader about the software, not about you.

Shift each bullet so you are the subject:

  • Instead of "Platform includes user authentication," write "Implemented email and password login with session handling."
  • Instead of "Dashboard showing sales trends," write "Built a dashboard that grouped sales by week and product category so the owner could spot slow sellers."

For team projects, be honest about your part. "Led the data cleaning and wrote the analysis section of a four-person capstone project" is better than implying you did the whole thing. Interviewers will ask, and a clear answer about your actual role is far more convincing than a vague claim.

Results when you don't have big numbers

Most personal and academic projects do not have revenue or user metrics. That is fine. You still have options for showing outcomes:

  • Usage: "Used by my department's 12-person team for shift planning."
  • Completion and scope: "Processed and cleaned 40,000 rows of public transit data."
  • Recognition: "Selected as one of three projects presented to the program's industry partners."
  • What it replaced or fixed: "Replaced a manual copy-paste process that took about an hour each week."
  • What you learned to do: "First production deployment; set up CI and automated tests from scratch."

Only use figures you can explain in an interview. If you estimate, phrase it as an estimate ("about an hour a week"). Never make up user counts or percentages to make a project look bigger.

Links to a live demo, GitHub repository, case study, or portfolio page help, especially for technical and creative roles. A few guidelines:

  • Write links as short, readable URLs (github.com/yourname/project) rather than long tracking links.
  • Make sure the link works and the thing behind it is presentable. A repo with no README is a missed opportunity.
  • Do not hide important information behind the link. Many readers never click, and ATS parsers usually ignore what is on the other side. The entry should stand on its own.

If you submit a PDF, keep links as plain text that is also clickable, so they still make sense if the document is printed or converted.

Keep projects ATS-readable

Projects sections get mangled by parsers more often than you might expect, usually because of formatting choices. To keep them clean:

  • Use a standard heading ("Projects").
  • Put the project name, tools, and dates on one line or in a simple consistent pattern. Avoid tables and multi-column layouts for this section.
  • Write tools and skills as plain words in the entry ("Python, pandas, Tableau") so they are searchable. Icons or logos are invisible to most parsers.
  • Use the same date format you use elsewhere on the resume.

Including the tools in each project entry also helps you match job descriptions naturally. If a posting asks for SQL and you used SQL in a project, the keyword appears in context, which reads far better than a long skills list on its own.

How many projects to include

Two to four is usually right. Pick the ones most relevant to the job you are applying for, not your favorites or your most recent.

If you have more, keep a longer master list somewhere and choose from it for each application. A data analyst role and a product operations role may call for completely different projects from the same pool. Tailoring the projects section is one of the fastest ways to make a resume feel written for the job, since it rarely requires rewriting your work history.

Keeping your projects saved in one place, such as a Talvio profile, makes it quicker to pick the right ones for each application instead of rebuilding the section from memory.

Projects to leave off

Some projects hurt more than they help:

  • Tutorial follow-alongs presented as original work. If you followed a course, say so, or pick something you extended on your own.
  • Unfinished projects with nothing to show, unless the role cares about the attempt and you can explain what you learned.
  • Projects that conflict with your current employer's policies or reveal confidential work.
  • Anything you would not be comfortable walking through in detail in an interview.

A quick checklist

Before you send the resume, check each project entry:

  • Does it say what the project is and who it was for?
  • Is your specific role clear, especially on team work?
  • Are the tools listed in plain text?
  • Is there at least one bullet on a result, scope, or outcome?
  • Is it relevant to this particular job?

A project that passes all five does real work on your resume. It shows the reader you can take something from idea to finished, which is what most hiring managers are trying to figure out in the first place.

Start your first resume

Free forever, no card needed. Talvio is in beta, and more features are on the way.