Portfolio Builder

---
name: portfolio-builder
description: Design and build a standout professional portfolio with case studies, project curation, and presentation.
category: career
---

## Overview

For designers, developers, writers, and most creative and technical roles, the
portfolio is the
interview before the interview. Hiring managers spend 2-5 minutes on it — which
means curation beats
volume, and the story around the work matters more than the work itself. This
skill covers selecting
projects, writing case studies, and structuring a portfolio site that converts
visitors into
conversations.

## When to use

- Building a first portfolio or rebuilding an outdated one

- Selecting which projects to include (and which to cut)

- Writing case studies that show process, not just outcomes

- Preparing a portfolio for job applications or freelance clients

- Reviewing an existing portfolio that's not converting

## Core concepts

- - - **Curation is the skill.** 4-6 excellent projects beat 15 mediocre ones.
  Every project should
  answer: does this represent the work I want more of? Cut anything that
doesn't.
- - - **Case study structure.** Context (what was the problem?), Role (what did
  you actually do?),
  Process (key decisions and why), Outcome (metrics or qualitative results),
Reflection (what you'd
  do differently). The process section is where seniority shows.
- - - **Show the thinking, not just the pixels.** Screenshots of final work are
  table stakes.
  Sketches, wireframes, rejected directions, tradeoff discussions — that's what
separates juniors
  from seniors in a reviewer's eyes.
- - - **The 10-second homepage test.** A stranger should grasp in 10 seconds:
  who you are, what you
  do, and see one impressive thing. Name, discipline, and 3-4 featured projects
above the fold.
- - - **Write for skimmers.** Short paragraphs, clear headers, captioned images.
  Reviewers skim; make
  every section's point obvious from its header and first line.
- - - **Frictionless contact.** Email, LinkedIn, and resume one click away on
  every page. Every extra
  step between "impressed" and "contacted" loses opportunities.

## Practical workflow

1. 1. 1. **Define the target.** What roles/clients is this portfolio for? List
   the 3-5 capabilities
   they care about. Every project choice maps to this list.
2. 2. 2. **Select 4-6 projects.** Prioritize: recent work, work matching the
   target, and work with
   measurable outcomes. Include one project that shows range if relevant — but
never at the cost of
   focus.
3. 3. 3. **Write the case studies.** For each: 300-600 words following the
   structure above. Lead with
   the outcome, then the story. Use real numbers; if under NDA, describe impact
qualitatively
   ("top-3 revenue driver") or get permission for anonymized metrics.
4. 4. 4. **Gather visuals.** Final outcomes first, then process artifacts.
   Consistent image sizing and
   quality — one blurry screenshot undermines the whole page. Redact or mock
sensitive data cleanly.
5. 5. 5. **Build the site.** Keep it fast and simple: a clean template beats a
   clever-but-broken custom
   build. Mobile-responsive is non-negotiable (40%+ of views). Test load time
and every link.
6. 6. 6. **Add the supporting pages.** About (human, specific, with a photo),
   contact, and a
   downloadable resume/PDF version. For developers: link GitHub with pinned,
documented repos.
7. 7. 7. **Get outside eyes.** Ask 2-3 people in your target roles to spend 3
   minutes and tell you what
   they remember. If they can't name your best project, the hierarchy is wrong.

## Common pitfalls

- - - **The museum portfolio.** Everything you've ever made, uncurated, from
  2016 onward. Reviewers
  judge you by your weakest piece — cut ruthlessly.
- - - **No context on team projects.** "We redesigned the app" — what did you
  do? Unclear ownership
  makes reviewers assume you did the least impressive part. Be explicit about
your role.
- - - **NDA paralysis.** "I can't show anything" is rarely fully true.
  Anonymize, recreate simplified
  versions, or build one strong personal project to fill the gap.
- - - **All visuals, no words.** Beautiful images with no explanation force the
  reviewer to guess the
  story. They'll guess wrong or move on.
- - - **Broken, slow, or desktop-only.** A portfolio that doesn't load on a
  phone fails the most basic
  test of craft. Test on real devices.
- - - **Never updating.** A portfolio frozen in 2022 signals stagnation. Add new
  work quarterly;
  retire anything older than your current skill level.