Naming Your Notable Projects When You Don't Have a Portfolio

If you work in software, design, marketing, or research, you've probably been told to build a portfolio. That's fine advice if you've got time, permission from past employers to share work, and projects that photograph well. Plenty of people have none of those things — the work was internal, confidential, unglamorous, or simply never packaged up for public view. That doesn't mean the work didn't matter. It means you need to describe it well on the CV itself, because the CV is the portfolio for a lot of applicants.

Stop thinking of it as a list of tools

A common failure mode is listing a project as a string of technologies or software: "Built dashboard using Python, SQL, Tableau." That tells a recruiter what you touched, not what you did or why it mattered. A better project description answers three questions in order: what was the problem, what did you actually do, what changed as a result.

• What was the problem — one line of context, no jargon assumed.
• What you did — your specific contribution, not the team's.
• What changed — even a soft outcome (adopted by another team, replaced a manual process, used in a client pitch) counts.

You don't need a live link to prove something happened

Recruiters reading a CV are not expecting a clickable demo for every line. They're reading for evidence of judgement and follow-through. A well-written sentence describing a project you can't show publicly is worth more than a link to a half-finished side project that doesn't reflect your best work.

A project description should let someone picture you doing the work — not just tell them you were near it.

Handling confidential or internal-only work

You can describe the shape of a project without naming the client, the codebase, or anything under NDA. Swap specifics for structure: describe scale in relative terms, describe the before-and-after, and avoid anything you're not permitted to share.

An example rewrite

Weak: "Worked on internal tool using React and Node." Better: "Rebuilt the internal expense-approval tool that finance had been chasing manually by email; approvals now happen in-app, cutting the average turnaround from several days to under 24 hours." No client name, no confidential detail, but it's specific enough to be believable and interesting.

If you genuinely have nothing to point to

Some roles really don't produce discrete "projects" — you maintained something, you supported something, you kept a system running. That's still describable. Frame it as an ongoing responsibility with a clear scope and a moment where you improved or fixed something, rather than forcing it into a project shape it doesn't have.

When a portfolio is worth building anyway

If you're early-career or changing fields and have almost no paid project history to draw on, a small public portfolio — even two or three modest pieces — can carry real weight precisely because you have less else to show. The difference is deciding this deliberately, not defaulting to it because a guide told you to.

FixMyCV reads the actual job description, checks how your existing project descriptions score against what the role is asking for, and flags where a vague line needs a sharper before-and-after — without inventing outcomes you didn't have.