Designer portfolio guide: selecting work, showing process and handling NDAs

For a designer, the portfolio is the interview before the interview. It's judged both on what it contains and on how it's put together, because the presentation itself is a design decision. This guide covers how to choose pieces, how much process to show, how to present visuals so they read well, and what to do when your best work is under a nondisclosure agreement.

Decide what kind of designer the portfolio is for

"Designer" covers very different jobs. A product designer is hired for problem solving and collaboration with engineers. A visual or brand designer is hired for craft and taste. A graphic designer working in print or packaging is hired for execution across formats. A single portfolio trying to be all three usually comes across as unfocused.

Before you pick any work, write one sentence that finishes "I want this portfolio to get me..." For example:

• "...a mid-level product design role at a company that builds tools for small businesses."
• "...freelance brand identity projects for independent restaurants."
• "...an in-house graphic design job at a publisher."

That sentence decides what goes in, what order it goes in, and how much explanation each piece needs.

Selecting the work

Four to six strong projects is enough for most designers. Fewer, deeper pieces almost always beat a large gallery.

When choosing, ask of each project:

• Does it match the work I want next? Lead with it if yes. Cut it or move it down if no, even if you're proud of it.
• Can I explain my specific contribution? If you were one of eight designers, you need to be able to say which part was yours.
• Is there a story? A constraint, a turn, a decision that went one way instead of another.
• Does it still represent my current skill? Work from years ago can quietly drag the whole portfolio down.

Your weakest piece sets the bar people remember. If you hesitate about including something, that hesitation is usually the answer.

Real work, redesigns and personal projects

Client and employer work carries the most weight, because it came with real constraints. Unsolicited redesigns of well-known apps are common in junior portfolios; if you include one, frame it honestly as a self-directed exercise and focus on your reasoning rather than claiming the original was "broken." Personal projects are fine, especially for visual designers, as long as they're finished and show the kind of work you want to be hired for. If you're just starting out, building a portfolio with no experience has more ideas.

Process vs. polish

Hiring managers for product and UX roles want to see how you think. Clients hiring for brand or illustration often care more about the final result. Most portfolios need both, in different proportions.

For UX and product designers

Process matters, but not all of it. A project page that walks through every sticky note from a workshop is tiring to read. Show the moments where your thinking changed direction:

1. The problem, in one or two sentences, with who it affected.
2. What you learned that shaped the design: a research finding, a data point, a constraint from engineering.
3. Two or three key decisions, each with the options you considered and why you chose one.
4. The final design, shown large and clearly.
5. The outcome, or honest notes on what happened if the project didn't ship.

Put a short summary and the final design near the top. Many reviewers skim the first screen to decide whether to read on. The detailed process can follow for the people who want it. Our guide on how to write a case study goes deeper into this structure.

For visual and graphic designers

Let the work carry more weight, but don't leave it completely silent. A brief caption for each project should cover the client or context, the brief, and one sentence on your approach. "Identity for a neighborhood bakery that wanted to feel handmade without looking amateur. I built the wordmark from hand-cut paper letters and paired it with a strict grid on the packaging so the overall system still felt organized."

Presenting visuals so they read well

The way you present the work is part of the work. A few practical rules:

• Show work at a readable size. If an interface screen needs to be zoomed to read, crop to the part that matters and show the full screen separately.
• Use mockups with restraint. A phone frame can help with context. A photo-real coffee-shop scene around every screen mostly adds noise.
• Keep a consistent background and spacing across projects so the work, not the layout, changes from page to page.
• Caption your images. One line explaining what the viewer is looking at ("Early wireframe: we tested putting search first, then moved it into the header") turns a picture into evidence.
• Show before and after where you improved something existing. Side by side is clearer than two separate sections.
• Check file sizes. Large uncompressed images make a portfolio slow, and a slow portfolio feels careless.

Check how your project pages look on a phone. Many people will first open your link from a message or email on their phone, and detailed screens that work on a large monitor can turn into unreadable thumbnails.

Handling NDA and confidential work

Many designers do their best work on internal tools, unreleased products or client projects with strict confidentiality. You have more options than leaving it out.

• Ask. Some employers and clients will allow portfolio use after launch, or with sensitive details removed. Get permission in writing.
• Anonymize. Remove the company name, logo, real data and any distinctive brand elements. Replace real content with realistic placeholder text and numbers. Describe the client generally: "a regional healthcare provider."
• Recreate. Rebuild key screens in a neutral style that shows the structure and interaction pattern without reproducing the original.
• Describe without showing. Write up the problem, your process and the decisions, using sketches or simplified diagrams instead of final screens.
• Password-protect. Some designers share confidential case studies only behind a password they send to interviewers. Check that this is actually allowed by your agreement; a password doesn't change what the contract says.

Add a short note at the top of these projects so reviewers know why details are missing: "Client and product details have been changed to respect a confidentiality agreement."

If you're unsure whether you can show something, assume you can't until you've checked. Reviewers notice designers who are careful with confidential work, and that counts in your favor.

Writing the words around the work

Designers often underinvest in text, but the headline, bio and project summaries are what make a reviewer understand the images. Keep them short and specific.

• Headline: "Product designer for complex B2B tools" says more than "Designer. Dreamer. Coffee lover." See writing a portfolio headline.
• Project titles: describe the outcome or problem, not just the client. "Making invoice setup possible in one sitting" beats "Acme Billing."
• Your role: state it plainly on every project. "My role: lead designer, working with one researcher and three engineers."

A quick checklist before you share

• Four to six projects, strongest and most relevant first.
• Every project states the context, your role and at least one decision.
• Images are readable, captioned and load quickly.
• Confidential work is cleared, anonymized or recreated.
• Pages work on a phone.
• There's a clear way to contact you.

Putting it together

A strong designer portfolio is edited, not exhaustive. Decide what job it's for, choose a handful of projects that point there, and show enough process that people understand your judgment without making them wade through every artifact. Present the visuals cleanly, caption them, and treat confidential work with care. Then read through it once as a stranger would, on a phone, and cut anything that slows them down. For more on what trips people up, see common portfolio mistakes.