Designers usually have two artifacts working for them in a job search: a resume PDF and a portfolio. The mistake most designers make is treating them as the same artifact in different formats. They aren't. They do different jobs at different stages of the funnel, and conflating them tanks both.

This post is what each one does, where each one fails, and how they work together.

The two artifacts solve different problems

The resume PDF is read first, in 7-10 seconds, by a recruiter who is sorting through 100 applications. Its job is to pass the recruiter screen. The recruiter is not evaluating your craft — they're confirming you've worked at the right kinds of companies on the right kinds of projects.

The portfolio is read second, in 2-15 minutes, by a hiring manager or design lead. Its job is to convince a designer that you can think — about problems, users, tradeoffs — not just produce visuals. The portfolio is the interview-earning artifact.

When designers treat the resume as a portfolio (visually elaborate PDFs with embedded project shots), the resume fails its actual job of being scannable. When designers treat the portfolio as a resume (a long list of projects with screenshots and no narrative), the portfolio fails its job of demonstrating thinking.

What each does — and what each doesn't

The compare-list is the working filter. A few additional notes:

The resume PDF should not be a visual showpiece. It can be cleanly designed and have one or two visual choices that signal taste — a confident type pairing, a deliberate accent color — but its main job is readability under a 10-second scan. Visually elaborate resume PDFs are the most common self-inflicted wound for designers. They look great in Behance shots and parse badly in actual hiring pipelines.

The portfolio is not a project gallery. A grid of 12 project thumbnails with no narrative is a portfolio in the literal sense and a failure in the functional sense. The hiring manager doesn't want to see everything you've done — they want to see how you think about 3-4 specific problems.

The case studies are the load-bearing element of the portfolio. Most designers spend 80% of portfolio time on visuals (image selection, layout, polish) and 20% on writing. The ratio should be closer to 50/50. The writing is what hiring managers cite when they decide to advance you.

The four-artifact stack

The full stack a senior designer typically has working for them:

1. Resume PDF — submitted to applications, read by recruiters.
2. Portfolio site — linked from the resume, read by hiring managers.
3. One-page visual sample — optional, useful for channels that don't link easily.
4. Case-study walkthrough — the live presentation in interview.

These are four different artifacts. They share content but serve different audiences. Designers who treat them as four versions of the same document tend to over-design the resume and under-prepare the walkthrough.

The walkthrough is especially under-prepared. Most designers spend a month polishing their portfolio and then walk through it cold in the interview. The walkthrough is the artifact that decides offers; it deserves rehearsal.

How the workflow actually runs

The funnel above is what happens in practice. Each stage filters out a different fraction of candidates. The resume filters most aggressively (about 60% of resumes don't earn a portfolio click). The portfolio filters next (about half of clicks don't lead to an interview). The walkthrough is where final offers are made or lost.

The implication: the resume is the gate. If the resume doesn't earn the portfolio click, all the portfolio work is wasted. Designers often invest heavily in the portfolio without realizing that the resume is the bottleneck.

For the resume side, see resume-action-verbs-that-arent-cliche and achievements-vs-responsibilities. The same patterns apply: lead with outcomes, quantify impact, cut responsibilities.

What goes in a strong design resume

The structure of a design resume that earns the portfolio click:

Header. Name, role title, contact, LinkedIn, portfolio link prominent. The portfolio link should be in the top 5 lines of the resume. Recruiters who are interested will click; if they have to hunt for the link, fewer click.

Summary (optional). Two lines. "Senior product designer with 8 years building B2B SaaS interfaces. Last 4 years focused on enterprise workflow tools — admin UX, integrations, complex data inputs." Skip if it would be generic.

Experience. Reverse chronological. Role, company, dates, 3-5 bullets per role. Bullets are achievement-led, scoped, and end on outcomes.

Skills. A short block. Don't list every tool; list the ones you'd be interviewed on. Figma, Framer, Webflow, Lottie, Principle — list the 5-8 that actually matter for the roles you want.

Education. One line.

Notable projects (optional). A single line or two — "Lead designer on [notable product]." This is the bridge that earns the portfolio click.

What goes in a strong portfolio

The structure of a portfolio that earns interviews:

Landing page. 4-8 project tiles, each with a hero image and a one-sentence problem statement. No long bios — your About lives on its own page.

Case studies. 3-6 of them, each 3-7 minutes to read. The structure of a strong case study:

1. Problem (1 paragraph). What was the design challenge? What constraints existed?
2. Process (1-3 paragraphs). Research, key insights, exploration. Show 1-2 alternative directions you considered and why you didn't pick them.
3. Solution (visual + 1-2 paragraphs). The final design with annotated decisions.
4. Outcome (1 paragraph). What happened after launch — usage, adoption, business impact, what you'd do differently.

Most portfolios fail on the outcome section. Skipping outcomes signals that you either didn't measure them or didn't get involved in measuring. Both are bad signals.

For broader portfolio-vs-resume context across roles, see pm-resume-what-makes-it-different — the analogous role-specific thinking applies.

When to skip the portfolio

Some design roles don't expect a portfolio:

• Design leadership roles (Director, VP) often weight portfolio less, because the work is increasingly about strategy, hiring, and team-building rather than craft. A short portfolio is still useful but the resume and the conversation carry more weight.
• Highly specialized roles (research, ops, strategy designers) sometimes use case-study writing instead of visual portfolios. Check what the JD asks for.
• Internal designers at large companies often work on confidential products. A "selected work" section with limited screenshots and more narrative is appropriate.

In all three cases, the resume becomes more load-bearing. Tighten it accordingly.

What this isn't

A few clarifications:

• It's not optional for IC designers. Don't try to interview for a senior product-design role without a portfolio. The interviewer expects to walk through case studies.
• It's not a Behance dump. Behance, Dribbble, and personal sites serve different functions. The portfolio for hiring should be on a personal site or a curated PDF, not a public-feed platform.
• It's not finished. Portfolios should be updated annually or after every major project. A portfolio last touched four years ago signals that nothing recent is worth showing.

The short version: resume PDF earns the portfolio click; portfolio earns the interview; walkthrough earns the offer. Three artifacts, three audiences, three different jobs. Designers who treat them as the same artifact tend to over-design the front and under-prepare the back.