A design CV should show outcomes, how you got there, and how you shipped with engineering.
See the general guide: IT CV template (Romania).
TL;DR
- Your portfolio is your proof. Your CV should help people get to the right case studies fast.
- Lead with outcomes (conversion, retention, usability, support load).
- Show collaboration and constraints (handoff, iteration, QA).
Quick checklist (before you send)
- Title: “Product Designer” / “UI/UX Designer” + domain (B2B/B2C, mobile/web).
- 2–3 case studies that match the role (not 10 tiny projects).
- 3–6 strong bullets for your latest role: outcomes + collaboration + process.
- Clean links (portfolio/Figma) and clear “what I did” vs “what the team did”.
Recommended structure (Design)
- Header (portfolio link front‑and‑center)
- Summary (2–4 lines: product types + what you deliver + what you’re targeting)
- Experience (outcomes + how you got there)
- Selected case studies (2–3, with links)
- Skills (research, prototyping, design systems, collaboration)
- Education/Certs (short)
What a strong bullet looks like (Design)
Useful formula: Outcome + context (flow/segment) + process (research → iteration) + delivery (handoff/QA) + result.
Examples:
- “Improved checkout conversion by ~7% by reducing steps and validating via usability tests.”
- “Reduced support tickets on [topic] by clarifying UI copy and information architecture.”
- “Improved handoff quality with clear specs (states, empty/error, responsive), reducing rework.”
No numbers? Use signals:
- fewer tickets, fewer UI regressions, faster implementation, better onboarding, fewer usability complaints.
Bullet library (Design)
Pick 6–10 that are actually true for you, then tailor them to the role.
Outcomes (conversion / retention / usability)
- “Improved conversion by [X%] by redesigning [flow] based on research and iteration.”
- “Reduced support tickets by simplifying [feature] and clarifying UI copy.”
- “Reduced time‑to‑complete for [task] by improving IA and interaction design.”
- “Improved adoption of a feature by clarifying value and adding contextual onboarding.”
Research & discovery
- “Ran interviews/usability tests with [N] users, identified top issues, and prioritized fixes with clear impact.”
- “Validated a hypothesis via prototypes + testing, then adjusted scope before engineering started.”
- “Turned support/sales feedback into a repeatable insight loop and a focused backlog.”
Design systems & consistency
- “Built/extended a design system, improving consistency and reducing UI regressions.”
- “Documented component states/variants, reducing implementation ambiguity.”
- “Introduced design tokens and spacing/typography rules, improving consistency across surfaces.”
Collaboration & handoff
- “Worked closely with engineering to adapt designs to constraints without losing the core outcome.”
- “Improved handoff (states, empty/error, responsive), reducing rework and back‑and‑forth.”
- “Did implementation QA and closed gaps quickly, improving shipped quality.”
Content design (when relevant)
- “Rewrote microcopy for [flow], reducing confusion and input errors.”
- “Standardized error messaging patterns, reducing user dead‑ends.”
Common mistakes
- Only listing tools (Figma) without outcomes.
- Portfolio with no context (problem → approach → result).
- No collaboration story (handoff, iteration with engineering).
Useful keywords (use only what you actually did)
- usability testing, interviews, IA, user flows
- design systems, tokens, components, accessibility
- conversion, retention, onboarding
- handoff, QA, iterative delivery, stakeholder alignment
Design CV template (copy/paste)
FAQ
Should the portfolio be a separate PDF or a website?
Either works if it’s easy to skim. The key is 2–3 strong case studies with context and outcomes.
How do I show impact without analytics?
Use signals: fewer tickets, reduced rework, faster implementation, fewer regressions, clearer onboarding, stronger qualitative feedback.
