How to list projects on your CV without making them look like filler

Most people either dump links or bury the useful bit

Projects can be some of the best proof on a CV, especially in technical careers.

They show how you think, what you build, and whether you can turn vague problems into something real. That is useful when a job title alone does not tell the whole story.

The problem is that people often list projects badly. They write three project names, throw in a GitHub link, and hope the reader will do the detective work.

They will not.

Put projects on your CV when they earn the space

The first question is not whether you have projects.

The question is whether the project helps prove your fit for this role.

A project deserves space when it does at least one of these things:

• proves a skill the role cares about
• shows initiative or ownership missing from your job titles
• gives evidence of delivery in a domain close to the target role
• makes a career change or sideways move look more credible

If it does none of that, it is probably portfolio material rather than CV material.

Give projects their own section only when that helps

This is where people get messy.

If the project was part of your actual job, it usually belongs under that role. Splitting it out into a separate Projects section can make the CV feel fragmented for no gain.

If the project was independent, academic, freelance, open source, or the strongest proof you have for the direction you want to move in, then a dedicated Projects section can work well.

The goal is not to show that you enjoy side projects. The goal is to help a reader recognise relevant evidence quickly.

What to write for each project

A useful project entry usually answers five things fast:

• what the project was
• what problem it solved
• what your role was
• which tools or methods actually mattered
• what changed because of the work

That does not mean every project needs a metric. Some do. Some do not. But the entry should still sound like real work, not a decorative list.

Bad version:

• “Built a machine learning app using Python, Flask, Docker, and AWS.”

Better version:

• “Built and deployed a Python and Flask document-classification tool for internal operations, packaging it with Docker and reducing manual triage time for incoming files.”

The second one tells me why it existed and what the work achieved. That is what makes the tools believable.

Another bad version:

• “Personal budgeting app. React, Node.js, PostgreSQL.”

Better version:

• “Designed and shipped a personal budgeting app in React and Node.js with recurring-spend tracking, category alerts, and a PostgreSQL data model, then used it to test retention and feature prioritisation over three release iterations.”

Again, the point is not to sound grand. It is to sound specific.

Choose projects for the job, not for your ego

This bit matters more than people think.

The most interesting project you have ever done is not automatically the most useful one for the CV in front of you.

If the role is heavy on backend systems, the hiring team probably cares less about your clever design-system side project than your API reliability work, data pipeline project, or infrastructure automation work.

If the role leans product or AI, then the project that shows evaluation, experimentation, ambiguous requirements, or user judgement may be stronger than the one with the flashiest stack.

You are not making a museum of yourself. You are building a case.

Keep the entry short, then let the interview do the rest

One mistake I see a lot is over-explaining projects because the person is proud of them.

Fair enough. But a CV is not where the full story goes.

For most projects, one or two lines is enough. If a project needs a whole paragraph to make sense, it probably needs tighter writing, not more space.

Save the deeper explanation for the interview, portfolio, or supporting links.

Why this matters even more for experienced technical people

For junior candidates, projects often compensate for limited work history.

For more experienced people, the job is different. Projects help show range, depth, and direction. They can prove hands-on credibility when your recent roles sound managerial. They can prove product judgement when your title sounds purely technical. They can prove technical depth when your official job descriptions were too vague.

That is why I think of projects as proof blocks, not hobbies.

That is also why a master profile helps. In OutRung, this is exactly the sort of material I would want stored once and then reused properly. Keep the full version of the project in your profile, then pull the relevant one into a tailored CV when the role actually calls for it.

The honest rule

If a project makes the hiring manager more confident you can do this job, keep it.

If it is there mainly because you spent ages on it, like it personally, or feel guilty deleting it, that is not enough.

Projects belong on a CV when they sharpen the case. If they do not, leave them out this time.