A portfolio is not a universal upgrade
Many candidates hear that they need a portfolio to stand out. That is true in some fields, unnecessary in others, and sometimes harmful when the portfolio is weak.
The right question is not "does a portfolio look more professional?" It is whether the portfolio helps a recruiter judge your level, your way of working, or the quality of what you actually produce.
If the answer is yes, the portfolio becomes a strong complement to the CV. If not, a clearer and more direct CV usually works better, as explained in design CV or neutral CV: what do recruiters prefer?.
When a portfolio is genuinely useful
Portfolios matter most when the output of your work can be shown, assessed and compared.
They are often relevant for:
- graphic, UX and UI designers;
- front-end, full-stack and no-code developers;
- writers, copywriters and content marketers;
- creative project managers with visible deliverables;
- photographers, video editors and motion designers;
- some product, architecture, communication and branding profiles.
In these roles, recruiters want to see work, not just job titles. That is why a portfolio can be more convincing than a long skills list. Instead of saying "Figma" or "strong app structuring skills," you show the output.
For technical candidates, it can complement a developer CV. For creative profiles, it expands on what we cover in our guide to useful CV complements.
When you are better off not adding one
A portfolio is not automatically the right move.
It is often unnecessary if:
- the role is judged mainly on leadership, coordination or seniority;
- you do not yet have enough work to show with proper context;
- your portfolio contains only visuals with no explanation of the problem or your role;
- the link is outdated, empty or broken.
A weak portfolio can send the opposite message from the one you want. It suggests poor selection, confusion between volume and quality, or a link added simply because "people say you should have one."
What recruiters expect from a good portfolio
Recruiters are not only looking for attractive outputs. They want to understand:
- the context;
- your exact role;
- how you worked;
- the result the project produced.
In other words, a good portfolio shows more than the final screen or final asset. It shows your thinking.
For a designer
The portfolio should present the starting problem, the constraints, key design choices, a few steps of the process, and the final result. A gallery of polished mockups with no context is easy to forget.
For a developer
The strongest proof is not always a screenshot. It is often a mix of:
- a product link;
- a clean GitHub repository;
- a short explanation of the stack and your role;
- one concrete sign of impact or complexity.
For a writer or marketer
Selected work should demonstrate a point of view, a quality level and, when possible, metrics such as traffic, conversions, open rates, engagement, SEO growth, or leads.
Where to place the portfolio on the CV
The best location depends on the role the portfolio plays in the application.
1. In the header
If the portfolio is central, put it at the top next to LinkedIn, GitHub or your website. This is often the best choice for designers, developers, freelancers and creative profiles.
Example:
- Name
- Portfolio
- GitHub
2. Inside a Projects section
If you have limited experience, a Projects section can bridge the CV and the portfolio. This works especially well for students, junior candidates and career changers.
3. Inside one or two key experience entries
You can also add the link only where it adds weight, for example on a product redesign, brand identity, shipped app or content project.
The mistake is pasting the same link everywhere. Effective internal linking inside your own application works like it does on a site: a few strategic entry points beat repetition.
How to connect the CV and the portfolio properly
The CV and the portfolio should confirm each other.
Your CV title, summary, featured projects and portfolio case studies should all tell the same story. If your CV says "B2B SaaS Product Designer" but the portfolio opens with event posters, you create friction.
Check the following:
- job titles are consistent;
- the projects highlighted on the CV also appear in the portfolio;
- dates and contexts match;
- the tools and skills claimed in the CV are visible in the work shown.
That consistency matters as much as the design itself. If you use Canva for your CV, remember that appearance never compensates for a vague portfolio.
Which platform should you use?
The best platform depends on your role and the level of autonomy expected.
Personal website
Usually the strongest option when you want full control over positioning, hierarchy and presentation. Very good for senior designers, freelancers, developers and creative consultants.
Behance or Dribbble
Useful for designers, illustrators and motion designers. They are practical for quick visibility, but they do not always replace a proper site when you need to explain your process.
GitHub
Essential or highly useful for many developer profiles. But a GitHub profile alone is not enough. Repositories need to be readable, selected and documented.
Notion, PDF or Google Drive
Acceptable in some cases, especially for content, strategy or student portfolios. The presentation still has to be stable, clear and easy to scan.
What to include in the portfolio
Three to five strong case studies usually beat fifteen superficial ones.
For each project, aim to show:
- context;
- objective;
- your role;
- tools or methods;
- result;
- what you learned, when relevant.
That logic is very close to the way you should write work experience on a CV: recruiters do not want a task list, they want to understand your contribution.
The most common mistakes
A portfolio that is too broad
When everything is shown, nothing is prioritised. Keep only the work aligned with the role you want.
A portfolio with no context
A gallery of links or images without explanation gets tiring fast.
A buried or badly labelled link
Avoid long raw URLs or vague labels such as "personal site maybe." Use clear labels like Portfolio, GitHub or Case Studies.
A portfolio disconnected from the CV
If the CV sells one target and the portfolio tells another story, trust drops immediately.
Should junior candidates have a portfolio?
Often yes, as long as it truly compensates for limited experience by showing evidence. For students, interns and junior candidates, a strong portfolio can surface academic, freelance or personal projects that a CV alone would summarise too quickly.
Do not force it, though. A minimal, empty or amateur portfolio does not help. If you do not yet have enough material, strengthen your CV, your Projects section and your LinkedIn profile first, then add the portfolio once it is ready.
The best portfolio supports the same promise as the CV
Your portfolio is not a separate object. It is proof. It should extend the CV, not contradict it or distract from it.
If it helps a recruiter see what you can do more quickly, keep it visible. If it adds noise, simplify.
Build a CV that points to the right proof
CV Creator helps you build a clear CV and then add the right links in the right places: portfolio, GitHub, LinkedIn or selected projects. You can adjust the hierarchy for each target role without starting from scratch. No sign-up, one-time price, unlimited CVs for 24 hours.
Further reading:
Ready to create your professional CV?
Use CV Creator to build a standout CV in minutes.
Create my CV →Continue reading
Canva CV: Pros, Limits and Better Alternatives in 2026
Should you use Canva for a CV? See the pros, ATS risks, practical limits and better alternatives depending on your profile.
Read more →References on a CV: When to Include Them and Who to Pick
Should you put references on a CV? Who should you choose, how should you prepare them, and when should they stay for the end of the process?
Read more →Beyond the CV: What Else to Add to an Application
A good CV opens the door, but cover letters, portfolios, LinkedIn and application emails can make your application much stronger.
Read more →