Product Designer CV & Portfolio Guide
How to balance a keyword-friendly CV with a portfolio that closes the interview.
Priya Nair
Head of Career Content · · 7 min read
Product design hiring is a two-gate process. ATS and recruiters search for Figma, user research, prototyping, and design systems before anyone opens your case studies. Then the portfolio decides whether you get the interview. A strong product designer CV must work for parsers and busy hiring managers: plain text, correct keywords, and bullets that describe impact — not thumbnails. This guide covers structure, keywords, portfolio pairing, and bullets that prove you ship products, not just screens.
CV plus portfolio: two gates
Many designers over-invest in portfolio polish and under-invest in the CV. That fails when:
- ATS never surfaces your application because "Figma" and "usability testing" are missing from parseable text
- Recruiters skim a visual CV they cannot search or forward easily
- Bullets describe deliverables ("designed mockups") without business or user outcomes
Your portfolio proves craft. Your CV proves scope, collaboration, and results at a glance. Both should tell the same story — see our 7-second test for why the top of the CV matters before anyone clicks through.
Recommended CV structure
- Contact details — include portfolio URL and LinkedIn
- Professional summary — seniority, domain, tools, one impact line
- Skills — Design tools, Research, Methods, Collaboration
- Experience — reverse chronological; 4–5 bullets per recent role
- Selected projects — optional if thin employment history; link to portfolio case studies
- Education and relevant courses or bootcamps
Do not embed portfolio screenshots in the PDF CV. Link out. Embedded images break many parsers — more in our ATS formatting guide.
Keywords recruiters search for
- Tools: Figma, Sketch, Adobe XD, FigJam, Miro, Principle, Framer
- Research: user interviews, usability testing, personas, journey mapping, A/B testing
- Delivery: wireframes, prototypes, high-fidelity UI, design systems, component libraries
- Collaboration: product managers, engineers, stakeholders, agile, sprint planning
- Domains: B2B SaaS, mobile, e-commerce, fintech, health — match the job ad
Mirror the job ad with our keyword matching guide. If they want "design system ownership", that phrase belongs in summary or a lead bullet when accurate.
Three before-and-after bullet examples
End-to-end product feature
Before: Designed new onboarding flow in Figma.
After: Led discovery and UI for mobile onboarding redesign (12 user interviews, 3 prototype rounds); shipped with iOS/Android engineering in 8 weeks — day-7 activation rose 22% and support tickets for "getting started" fell 31%.
Design system
Before: Helped maintain the company design system.
After: Co-owned Figma design system (40+ components); cut average feature design time from 5 days to 3 by standardising patterns and pairing with front-end on token documentation.
Research-driven iteration
Before: Conducted user research and improved the checkout experience.
After: Ran moderated usability tests (n=9) on checkout prototype; simplified payment step from 4 screens to 2 — conversion on completed purchases improved 14% in A/B test over 4 weeks.
Sample professional summary
Product designer with 5 years in B2B SaaS, specialising in complex workflows and design systems. Figma, user research, and prototyping; partnered with PM and engineering on 15+ shipped features. Recent work on analytics dashboard redesign increased weekly active use by 19%. Portfolio at example.design — seeking senior product designer role in productivity or data tools.
Accessibility and inclusive design
Accessibility is increasingly a screening signal, not a nice-to-have. If you have shipped WCAG-aligned work, name the standard and your role: audits run, contrast fixes, keyboard flows, screen-reader testing. A bullet like "redesigned settings panel to WCAG 2.1 AA; reduced accessibility-related support tickets by 26%" beats a skills line that only says "accessibility". Hiring managers in public sector, health, and finance especially search for this language.
Agency vs in-house: different CV emphasis
Agency designers should show client count, project turnaround, stakeholder management across brands, and reuse of design systems across accounts. Name sectors served when they match the target employer.
In-house designers should show depth on one product: roadmap partnership, design debt paid down, metrics over multiple releases, and cross-functional rituals (sprint planning, design critiques).
Do not use the same summary for both — agency breadth and in-house depth read as different hiring bets.
Junior, mid, and senior: what proof changes
Junior: Bootcamp or graduate projects, tools, research participation, and craft under mentorship. Portfolio quality matters more than years.
Mid-level: End-to-end feature ownership, measurable impact, and collaboration with PM and engineering without hand-holding.
Senior: Design system strategy, mentoring, ambiguous problem framing, and influence on product direction — still with outcomes, not titles alone.
A senior CV that only lists screens shipped reads junior. A junior CV that claims "led design strategy" without evidence reads inflated. Calibrate language to scope.
Portfolio pairing
Best portfolios show problem → role → process → outcome for 3–5 case studies. Each case study should align with a bullet on the CV so recruiters can cross-reference quickly. Include:
- Your specific contribution on team projects ("I owned research and UI; PM defined roadmap")
- Constraints: timeline, platform, accessibility requirements
- Metrics or qualitative impact where possible
- Readable case study text — not only hero images
Junior designers with limited commercial work should lead with bootcamp or personal projects in both CV and portfolio, written with the same rigour as paid roles.
UX vs UI vs product design
UX-heavy roles: Lead with research, testing, information architecture, and problem framing.
UI-heavy roles: Lead with visual craft, design systems, and interaction polish — still with outcomes.
Product design (generalist): Balance discovery, delivery, and collaboration; show you can own a feature from problem to ship.
One generic "designer" CV for all three underperforms. Tailor summary and project order per application.
Engineering and PM handoff on your CV
Product design hiring increasingly tests whether you can ship, not only ideate. Bullets that mention design specs, component handoff, Storybook contribution, or pairing with engineers on edge cases signal delivery maturity. "Partnered with 2 squads on quarterly roadmap; design QA on 8 releases with <5% post-launch UI defects" tells a hiring manager you understand the last mile. Designers who only describe workshops without release outcomes read as research-heavy for product design generalist roles.
Common product designer CV mistakes
- Image-only CV with no parseable tool or method keywords
- Bullets that list deliverables without user or business impact
- Portfolio link buried or broken — test it before every application batch
- Claiming sole credit on large team launches
- Omitting collaboration with engineering and product — hiring managers want team players
- Typos in tool names (Figmma, Figmaa) — undermines attention-to-detail brand
Bootcamp graduates and career changers
Lead with a Projects section: capstone, redesign challenges, volunteer work for nonprofits. Name tools, users researched, and measurable or observable outcomes. Summary example: "Career changer from teaching; UX Design bootcamp (2025) with 3 case studies in accessibility and mobile. Strong facilitator background for user interviews and workshops."
Career changers should connect prior domain to design advantage: healthcare admin → clinical workflow empathy; support engineer → technical product intuition. One honest bridge sentence in the summary prevents recruiters from guessing why you pivoted.
Next steps
Write a text-first CV that names tools and impact; let the portfolio show craft. For general CV structure, start with our complete guide to writing a CV. For dual ATS and human optimisation, read how to optimise for the robot and the recruiter. Then run your CV through Cvaluate's free analysis against a product designer job description — keyword gaps and bullet rewrites before you apply.
Frequently asked questions
- Should I put my portfolio link on a product designer CV?
- Yes — prominently in contact details or summary. Recruiters expect a portfolio URL. The CV still needs text keywords for ATS; do not rely on the portfolio link alone to carry screening.
- Do product designers need a two-page CV?
- Often yes at mid-level and above, when you have multiple substantial product launches. Junior designers may fit on one page plus a strong portfolio. Cut older freelance work that does not support the target role.
- How do I show UX research on a CV?
- Name methods you actually used: user interviews, usability testing, surveys, diary studies. Tie to outcomes: "12 moderated tests informed checkout redesign; cart abandonment fell 18%." Avoid listing research methods you only observed.
- Can I use a visual CV template as a designer?
- Not for ATS-heavy applications. Use a clean text-based CV for online applications and save visual layout for direct outreach or portfolio context. Parsers cannot read image-heavy CVs reliably.
See how your CV scores — free
Design CV getting filtered before anyone sees your portfolio? Cvaluate checks tool keywords and impact bullets — free.
Analyse my CVFree to try · Sign in in one click · No credit card