Projects on a Resume

For anyone without directly relevant job history, projects are the strongest evidence available. They also fail most often for one reason: they are listed rather than written up.

Write a project like a job

Give it the same anatomy as an employment entry.

Weak:

• Completed a group project on retail inventory management

Strong:

Stock Process Rebuild (module project, external client) · Portland State University · Sep to Dec 2025 Twelve-person retail business, four-person student team, I led

• Replaced a four-hour manual weekly stock count with a count-by-section method and a variance-flagging spreadsheet
• Reduced their count to about one hour, and the owner has kept using it since the module ended
• Spent as much time persuading two resistant staff members as building the system

Title, context, dates, then bullets with outcomes. The same shape as a job, because it is doing the same job on your resume.

The third bullet is the one that makes it credible. Nobody invents the detail about resistant staff, and it is the thing an interviewer will ask about.

Which projects to include

Ranked by how much they are worth.

One: work for a real external user. A local business, a nonprofit, a client, a public repository people actually use. Someone with no obligation to you found it useful, which is the strongest signal available.

Two: substantial coursework with a real deliverable. A capstone, a final-year project, a competition entry.

Three: personal projects with an outcome. Something you built and shipped, with users or a measurable result.

Four: tutorial and practice projects. Worth very little. Everyone applying has done the same well-known exercises, and they demonstrate that you followed instructions.

If you have anything in the first two categories, lead with it and consider dropping the fourth entirely.

Depth over breadth

One developed project beats four listed.

Four one-line project mentions give a reader nothing to ask about and nothing to assess. One project with context, outcome and an honest complication gives them a conversation, which is what you want from a resume.

Two or three projects maximum on a resume, one of them developed properly. Harvard’s career service materials describe a document that differentiates you, and depth differentiates where a list does not.

Where the section goes

Above experience when projects are your strongest evidence: students, recent graduates, career changers, and people entering technical fields without industry experience.

Below experience once you have relevant professional work. At that point projects supplement rather than carry the document.

Merged into experience is often best for students. Rather than a separate projects section, put projects in the experience section alongside part-time jobs, labelled accurately. It reads as a fuller experience section, which is the honest impression. See the student resume guide.

Include the complication

The single most persuasive element and the one almost everyone omits.

Every real project has a part that went wrong, took longer than planned, or required a compromise. Naming it does three things: it proves the project was real, it demonstrates judgement, and it gives an interviewer something substantive to explore.

• The first version failed because I had assumed clean data; rebuilding the import to handle the actual export took another two weeks

That sentence is worth more than a paragraph of description. It is also the answer to the interview question you will be asked anyway.

Choosing what to build

If you are building a project specifically to strengthen an application, three properties make it count.

A real user. Even one. A friend’s business, a club, a local charity.

Something visible. A reader can look at the result, use it, or see evidence it was used.

Aligned with the target role. Read the O*NET profile for the occupation you want and pick a project that exercises the skills it actually lists, rather than the ones that are fun to build.

Small and finished beats ambitious and abandoned, every time. A modest tool in use is stronger evidence than a large half-built system.

Links

Include one if there is something worth looking at: a repository with a real README, a live site, a case study, a document.

Do not link to an empty repository or a project that no longer runs. A reader who follows a link and finds nothing has learned something worse than if you had not offered it. See the resume header guide.

For creative fields the portfolio does this job and the resume should point at it rather than duplicate it. See the graphic designer resume guide.

A short check

1. Does each project have a title, context and dates?
2. Does each have an outcome, not just a description?
3. Is at least one developed with three bullets including a complication?
4. Are tutorial projects removed?
5. Does every link work and contain something?

Related

For the section it sits near, see the resume work experience guide and resume achievements. For early-career documents, see the student resume guide and the internship resume guide. For coursework, see relevant coursework.

Or write them up with the resume bullet point writer, free at Kazifi.