Guide

Portfolio preparation guide.

A portfolio is not a folder of everything you've ever made. It's a small, curated collection of work that answers one question: can you do what this role needs? This guide explains what to include, what to leave out, and how to present each piece.

By Advoke CV Editorial Team Published: January 2025 Reading time: ~5 minutes

1. Who needs a portfolio

Portfolios are typically expected in: design, UX, development, content writing, photography, marketing (sometimes), architecture, and academic research. They can also be an advantage in roles where samples of work help — for example, an analyst who can show a data story they wrote.

If a portfolio isn't expected in your field, you can still benefit from having one — but don't let a portfolio site distract from the resume. For most roles, the resume is read first.

2. What to include

Include three to six pieces of work. More than that dilutes the portfolio, and readers rarely go past the first few pieces anyway.

For each piece, ask: does this show what I want them to see?

  • Relevance. Is this the type of work the role will involve?
  • Depth. Can I describe what was hard about it?
  • Ownership. Can I say clearly what I did, not just what the team did?
  • Recency. Is this from the last few years, unless the older work is significantly stronger?

3. How to present a case study

A good case study is a short narrative with four elements:

  1. Context — what was the project, who was it for, what was the problem?
  2. Your role — what did you specifically do, and what did you not do?
  3. Process — what was hard, what did you have to figure out, what decisions did you make?
  4. Outcome — what happened, and what can you measure or demonstrate?

Aim for 150–300 words per case study. Design portfolios may be more visual and content portfolios more text-heavy, but the structure is the same.

4. What to leave out

  • Every piece you've ever made. Volume is not quality.
  • Work you can't describe. If you can't explain what was hard, leave it out.
  • Client work without permission. If you signed an NDA, use generic descriptions and no client details.
  • Work you completed years ago. Unless it's specifically relevant and still reflects your current work, prefer newer pieces.
  • Old or weak pieces to "show range". Range is less important than depth of quality.

5. Format

A simple, fast, readable portfolio works better than an elaborate one. Most people who look at portfolios want to see the work and understand the context quickly. That said, if you're a designer, the portfolio itself is judged as a piece of work.

Considerations:

  • Accessibility. Accessible design is part of quality now. Ensure colour contrast, keyboard navigation, and image alt text.
  • Load speed. Large images slow the portfolio down. Optimise.
  • Navigation. If you have many pieces, use a simple index page.
  • Contact. Make it easy to reach you — a visible email, not just a form.
  • Portfolio type. A personal site, a Behance/Dribbble profile, or a PDF can all work depending on the field. Match the convention your target roles expect.

6. Final checklist

  • Does the portfolio have three to six pieces (not fifteen)?
  • Is every piece genuinely relevant to the target role?
  • Does every piece have context, role, process, and outcome?
  • Have you removed work you can't describe in detail?
  • Is the portfolio fast, accessible, and easy to navigate?
  • Is your contact information visible?