How to List Projects on Your Resume

List projects on your resume when they prove a skill the job asks for that your job titles alone do not show. Give each one a name, your role, the tools you used, and one or two bullets on what you built and what changed because of it. Put work projects inside the relevant job entry, and give personal, freelance, or academic projects their own "Projects" section. That section goes above your experience only when the projects are more relevant than your work history.

When a projects section earns its space

A resume page is limited, so a projects section has to do something your experience section cannot. It usually earns its place in one of four situations:

• You are changing careers. Your job history is in a different field, but you have built things in the new one. A project is often the only direct evidence you can offer, which is why our career-change resume guide leans on them.
• Your best work does not match your title. An operations coordinator who built the team's reporting dashboard, or a teacher who ran a school's move to a new learning platform, did work their title hides.
• The posting asks for a skill you use outside work. If the role wants SQL and you have only used it on a side project, the project is where that skill becomes believable.
• You are early in your career. For students and recent graduates, projects often carry most of the resume; our guide on writing a resume with no experience covers that case in depth.

If none of these apply, and your experience section already shows everything the job asks for, you probably do not need a separate section. Adding one out of habit only pushes stronger material further down the page.

Work projects versus independent projects

The most common formatting mistake is treating every project the same way. The two types belong in different places.

Projects you did for an employer

These normally belong under the job where you did them, written as bullets. That keeps the context clear: the reader sees the project as part of your role, at a real company, with real stakes. A work project deserves its own entry in a Projects section only if it was large enough to be the main thing you did in a period, or if you want to group several projects across jobs under a theme. Consultants, agency staff, and project managers often use this format, listing client engagements with the employer name kept visible.

Personal, freelance, volunteer, and academic projects

These go in a separate section, because they have no job entry to sit under. Label the section plainly: "Projects," "Selected Projects," or "Independent Projects." If the work was paid freelance work, it may belong in your experience section instead; our guide on listing freelance and contract work explains that choice. Volunteer projects can go either here or in a volunteer section, depending on which one tells the stronger story for the job.

What each project entry should include

Every entry needs enough for a reader to understand it in a few seconds:

• A name that describes it. "Inventory Forecasting Tool" tells the reader more than a codename or repository name.
• Your role and the context. Solo, lead of a team of three, or one contributor among many. Honesty here matters, because interviewers ask.
• Dates. A year or a month range is enough. Recent work reads as a current skill; older work may need to show that the skill is still in use.
• Tools or methods. Name the ones the posting cares about, which also helps an applicant tracking system match you to the job.
• One or two outcome bullets. What you built and what happened because of it.
• A link, if there is something to see. A live site, a repository, a case study, or a portfolio page. Use a short, readable URL, and check that it works and is public before you send the resume.

An illustrative entry for a marketing coordinator moving into data analysis might look like this:

• Customer Churn Analysis (independent project, 2026) | Python, pandas, SQL, Tableau
• Cleaned and joined a public telecom dataset of several thousand customer records and built a model to flag customers at risk of cancelling.
• Published a dashboard and a two-page write-up explaining which account features were most associated with churn and what a retention team could test first.

Notice what the example does not do. It does not claim a business result the project could not have produced, such as revenue saved, because there was no business. For independent work, the outcome is what you built, what you found, and who used it, if anyone did.

Writing project bullets that read like results

Project bullets follow the same rules as any other resume bullet: start with a strong verb, name the specific thing you did, and end with the effect. Our guide to bullet points that show impact goes deeper, but a few rules matter especially for projects.

• Lead with the problem or the outcome, not the tech stack. "Built a React app" is weaker than "Built a booking tool that let a local studio take appointments online without phone calls."
• Use real numbers only. Users, downloads, time saved, records processed, response time improved: include them if you measured them, and speak qualitatively if you did not. An invented number is a liability in an interview.
• Show judgment, not just labour. One line about a decision you made, such as a trade-off, a scope cut, or a test that changed your approach, tells the reader how you work.
• Keep it to two bullets for most projects. A project that needs five bullets is probably better told as a portfolio case study, with the resume linking to it.

Where the section goes and how many to include

For most experienced candidates, the Projects section sits below experience and above education. Move it above experience when the projects are more relevant to the target job than your work history is, which is typical in a career change or for a recent graduate. A combination resume format handles this well, because it lets you lead with relevant work without hiding your job history.

As for quantity, two to four projects is a sensible range for a single page. Experienced candidates often need only one or two; career changers and graduates may use three or four. Choose the ones that match the posting most closely, not the ones you are proudest of, and swap them per application. When you tailor your resume to a job description, the projects section is one of the easiest parts to rotate, because each entry stands alone.

Mistakes that make projects look weak

• Tutorial clones. A to-do app or weather app copied from a course shows that you finished a course, not that you can solve a problem. If you built one while learning, extend it into something with a real user or a real question before listing it.
• Overstated roles. Writing "built" when you contributed one module of a group project will come apart the moment an interviewer asks you to walk through the architecture.
• Dead or private links. A reviewer who clicks a broken link assumes the project is abandoned. Check every link before each application.
• Confidential employer work. Do not publish or describe proprietary code, client names, or internal data from an employer project without permission. Describe the problem and your approach in general terms instead.
• Listing everything. Ten small projects read as unfocused. Three strong, relevant ones read as a direction.

Make the project easy to talk about

A project on your resume is an invitation for interview questions, and that is its biggest value. Prepare a two-minute version for each one: the problem, what you did, a decision you would make differently now, and what you learned. If a project is substantial, a short write-up or portfolio page lets you give the resume line depth without adding length.

Tailorapply builds a tailored resume for every posting, which makes choosing the right projects for each job much less work. The rule behind it stays the same: include the projects that prove what this employer is asking for, describe them honestly, and cut the rest.