The portfolio: the document that multiplies your chances in interviews

This document is often called a portfolio. And no, it isn't reserved for designers or creative agencies. Whether you're in sales, HR, marketing, development or project management, you have achievements that deserve to be shown, not just told.

The problem everyone knows: in an interview, you have 20 useful minutes to talk about yourself. Impossible to detail that complex project you led, that solution you found, that tool you built. You often leave frustrated, feeling you showed only 10% of your value.

The solution: where the CV must stay lean and concise, the portfolio is your chance to present in detail who you are, how you work, and the real impact you have. Beyond claiming you're "proactive," "adaptable" or "dynamic," you show how you tackle problems, with what methods and what results.

The concrete impact: you're no longer limited by interview time, the reader understands more easily how you work, you come across as structured, and documenting your projects naturally prepares you for many questions (notably the situational questions).

How to build it

First step: create a centralized documentation space. I recommend Notion. It's free, easy to use, easy to format and to share publicly.

1. A professional introduction (2-3 paragraphs)

Who you are, your area of expertise, what drives you. A chance to say more than a CV allows, more authentically.

2. Your public work

Anything already accessible online: articles, a podcast appearance, videos, open-source projects, visuals, and so on.

3. Your past projects

Here you make your contributions explicit, the ones that aren't public content. Start by asking yourself:

• Which projects made you particularly proud?
• Which tools or processes did you create that are still used?
• Which problems forced you to explore new solutions?
• Which presentations or analyses helped make or change a decision?
• Which measurable results did you generate?
• What do colleagues regularly ask you for?

Once you've identified the most relevant projects (in line with the role), format them:

• The context (what problem? what goal? what constraints?)
• Your actions (what did you create or set up?)
• The results (measurable or qualitative impact)
• The lessons (what did you learn?)
• A proof (screenshot, anonymized excerpt, diagram)

A concrete example

Automating customer follow-ups: how I recovered €45K in overdue invoices.

Context: at a 30-person SME where I ran admin and accounting, we had about €200K in unpaid invoices, some more than 6 months old. Everyone knew, no one had time to chase them. One day I did the math: a personalized follow-up takes 15 minutes, so 50 hours for 200 customers. Impossible by hand. I looked to automate without it feeling like "robot spam."

Actions:

• Segmenting overdue invoices into 3 buckets (under 30 days, 30-60 days, over 60 days)
• Three email templates (from polite reminder to firmer tone)
• A Zapier system connecting the accounting software to Gmail
• A test on 10 customers before rolling out
• Training a colleague to take over

Results after 3 months: €45K recovered, 2 hours of work per week, and some customers even thanked me for the "courteous reminder."

The limits (yes, show them): 3 large customers complained about the automated feel, so back to manual for them. A misconfiguration sent 50 reminders at once on a Friday at 6pm. And my colleague never really took the tool over, which left me indispensable for the setup.

Lessons: I should have spent more time training my colleague, and avoided automation on key accounts. Showing these limits, far from hurting you, proves your honesty and self-awareness (exactly what a recruiter looks for, as I explain in Inside a recruiter's head).

A few rules

• No more than 3 to 5 projects. Beyond that, you come across as unable to be concise.
• The projects you cite should add value for the role (ideally, they show skills mentioned in the job description).
• Forget the visuals. The portfolio doesn't need to be pretty, it needs to be easy to read and rich in information about you.

How to share it

As simple as a direct link in your CV, plus a mention in your cover letter: "I've documented several of my projects in this document, feel free to take a look."

Enjoying this article?

Get the next ones straight to your inbox.

you@email.comSubscribe

Start today

The best candidates understand that an interview doesn't always go their way, and that they almost never get to present every achievement. Building your portfolio isn't a cosmetic exercise. It's an investment that pays immediate dividends: clarifying your value, naturally preparing you for interviews, setting you apart.

Start simply. Open a Notion document. Write the title of a project you're proud of. Document it using the context-action-result structure. In an hour, you'll have done more for your employability than 95% of candidates.

FAQ

Is a portfolio only for creative jobs?

No. Sales, HR, marketing, development, project management: everyone has achievements worth showing rather than just telling. The portfolio documents how you work and the impact you have.

How many projects should a portfolio include?

Three to five at most, directly relevant to the role. Beyond that, you risk looking unable to prioritize. Each project follows the structure context, actions, results, lessons, proof.

Should I show a project's limits and failures?

Yes. Owning a project's limits proves your honesty and self-awareness, two signals recruiters value highly. A project presented as flawless raises suspicion instead.