UX Designer Resume vs Portfolio: What Goes Where

Product companies reviewing UX candidates typically look at two separate artifacts before scheduling a screen: a resume and a portfolio. Each one does a different job. Mixing up what belongs in each is one of the most common mistakes designers make — and it costs them interviews before a hiring manager ever clicks the portfolio link.

This guide breaks down exactly what each document needs to accomplish, what to put in each one, and how to make them work together.

What the Resume Actually Has to Do

Your resume has one job before it reaches a human: survive the applicant tracking system. Most mid-to-large product companies route applications through an ATS before a recruiter sees them. These systems parse plain text and match it against keyword criteria derived from the job description. A visually rich, two-column designer resume with embedded icons and custom fonts often fails this step entirely — not because the design is bad, but because the parser can’t read it.

Understanding how ATS parses columns and tables is worth your time before you finalize your layout. The short version: single-column, standard-font resumes parse reliably. Multi-column layouts frequently scramble the order of your content when ingested.

Once the resume clears ATS, a recruiter typically spends 6–7 seconds scanning it before deciding to read further. At that point, the resume needs to answer three questions fast: What level is this person? What kinds of products have they worked on? Do they show measurable impact?

Your portfolio answers none of those questions quickly enough. That’s why the resume exists.

What the Portfolio Has to Do

The portfolio is where you demonstrate craft, process, and judgment. Hiring managers at product companies — especially those with a design-mature culture — want to see how you think, not just what you shipped. They’re looking for evidence that you can frame a problem, navigate ambiguity, collaborate with PMs and engineers, and iterate based on data or user feedback.

Case studies do this work. A resume bullet cannot. The portfolio is the right place for annotated wireframes, research synthesis, before/after comparisons, and the reasoning behind design decisions. Trying to cram process narrative into a resume wastes space and reads poorly.

Which Projects to Name on the Resume

Name projects on the resume only when they add context that keywords alone can’t provide. A line like “Led end-to-end redesign of checkout flow for a B2C e-commerce platform” tells a recruiter the domain, the scope, and the type of work. That’s useful. A paragraph describing your design process is not.

For each project you mention, follow this structure:

• Role and scope (what you owned)
• The problem or initiative in one clause
• A quantified outcome if you have one

Example: “Redesigned onboarding flow for a SaaS dashboard product, reducing time-to-first-action by 34% over two release cycles.”

If you don’t have a hard metric, use a proxy: usability test scores, NPS delta, task completion rate, reduction in support tickets related to a specific flow. Approximate figures are acceptable if they’re honest. Invented numbers are not.

For guidance on framing impact without inflating claims, the same principles that apply to product manager resumes and ATS keywords translate well to design roles — both functions need to show business outcomes, not just activity.

Metrics and Outcomes for Design Work

Design metrics are harder to isolate than engineering or sales metrics, but they exist. Common ones worth including on a resume:

• Task completion rate (before vs. after)
• Time-on-task or time-to-complete a key user flow
• Error rate reduction
• Conversion rate changes tied to a redesigned surface
• Reduction in user-reported friction (support volume, CSAT, NPS)
• Accessibility compliance improvements (WCAG AA/AAA)
• Design system adoption across teams or components

If you led research, include the scale: “Conducted 18 moderated usability sessions across three user segments.” Numbers like that signal rigor without overstating impact.

Avoid vague phrases like “improved user experience” or “enhanced usability.” Every UX designer claims this. Specificity is what differentiates you.

Tools and Methods: Resume vs. Portfolio

Tools belong on the resume. Methods belong in the portfolio.

List the tools you use fluently in a dedicated section: Figma, Sketch, Protopie, Maze, UserTesting, Miro, Zeplin, Storybook, Jira. Recruiters and ATS systems both scan for these. A job description that requires Figma proficiency will filter out resumes that don’t mention it.

Methods — jobs-to-be-done frameworks, double diamond, card sorting, tree testing, diary studies — are better demonstrated through case study narrative in your portfolio. Listing “double diamond” as a skill on a resume without showing it in action carries little weight with experienced hiring managers.

For a practical look at how to structure the skills section so it reads well for both humans and parsers, see the ATS-friendly resume template guide.

How to Link Your Portfolio Without Losing ATS Credit

This is a real problem. If you put your portfolio URL in a header graphic, a sidebar, or a custom-styled text box, many ATS systems won’t parse it. The link needs to appear as plain text in the body of the resume.

Best practice: include the URL in your contact line at the top of the document as plain text — not hyperlinked text that obscures the URL. Write it out fully: yourname.com/portfolio or dribbble.com/yourhandle. Some ATS systems don’t follow hyperlinks at all, so the visible URL matters.

Also include a brief portfolio note in your summary or experience section if relevant: “Portfolio with case studies available at [URL].” This reinforces the signal for human readers who skim.

Don’t rely on LinkedIn to substitute for a portfolio link. A LinkedIn profile is useful for other reasons, but a hiring manager evaluating design work wants a direct path to case studies, not a social profile.

One Page vs. Two Pages for Designers

The one-page rule is frequently misapplied to designers. It originated in contexts where resumes were physically printed and passed between interviewers. For digital submissions, the more relevant question is: does every line earn its space?

If you have under five years of experience, one page is almost always the right call. If you have 8–12+ years across multiple products and companies, two pages is reasonable — but only if the second page contains substantive experience, not padded descriptions.

The how long should a resume be guide covers this in more detail across roles. For designers specifically: don’t use extra space to describe your process. That belongs in the portfolio. Use extra space only if you have additional relevant roles, projects, or education that genuinely add signal.

One common mistake: designers sometimes use a two-page resume to compensate for a weak portfolio. A hiring manager who wants to see your work will not be persuaded by more resume text. Fix the portfolio first.

Putting It Together

Think of the resume and portfolio as two stages of the same argument. The resume gets you past the filter and earns the click. The portfolio closes the case for an interview.

That means the resume needs to be machine-readable, keyword-aligned, and outcome-focused. The portfolio needs to be case-study-driven, process-transparent, and visually coherent with your actual design sensibility.

If you’re tailoring your resume to specific job descriptions — which you should be doing for every application — tools like TailorMyJob can help you align your resume language with the exact terms a job description uses, without manually rewriting from scratch each time.

For a broader look at how to adapt your resume to different roles and requirements, the how to tailor your resume for each job guide walks through the full process.

The split is simple in principle: let the resume prove you’re qualified, and let the portfolio prove you’re good.