UI Designer CV Example and Writing Guide [2026]

Before you write any section, decide what question the hiring manager needs the CV to answer. For a junior UI designer, the question may be whether you can apply design fundamentals, learn a design system, and explain your decisions clearly. For a mid-level designer, it is usually whether you can take ownership of interface work across a product area. For a senior UI designer, the question moves towards design systems, visual direction, accessibility standards, mentoring, and cross-functional influence.

Your CV should not try to document every screen you have designed. That is what your portfolio is for. The CV should provide context: what kind of product you worked on, what problem the interface needed to solve, how you collaborated, which constraints mattered, and what improved after your work.

A weak CV says you designed screens in Figma. A stronger CV says you redesigned a subscription onboarding flow in Figma, used reusable components, checked contrast and interaction states, and prepared handover notes that reduced avoidable rework for developers. The second version gives the reader proof of judgement, not just tool use.

Use your CV and portfolio together. The CV should make the recruiter want to open the portfolio, while the portfolio should prove the quality behind the CV claims. Add a portfolio link near the top, check that it works on mobile and desktop, and make sure the first case studies match the kind of role you are applying for.

Your profile is the short paragraph at the top of the CV. Keep it specific. It should tell the reader what kind of UI designer you are, what environments you understand, and what you can prove.

Avoid broad lines such as creative, passionate, or detail-oriented designer. They do not help a product lead, design manager, or recruiter judge whether you can contribute. Use concrete details instead: product type, design system experience, accessibility awareness, tools, and outcomes.

For example:

UI designer with three years of experience shaping SaaS dashboards, ecommerce journeys, and responsive web interfaces. Confident in Figma, component libraries, interactive prototypes, WCAG-aware design decisions, and developer handover. Recent work includes redesigning account settings and checkout screens to improve task clarity and reduce design-dev rework.

That profile works because it names the role, the design context, the tools, and the kind of evidence the reader can expect. You can adapt the same structure for different levels. A junior profile might focus on course projects, internships, freelance work, and design fundamentals. A senior profile might lead with design system ownership, visual quality standards, team coaching, stakeholder alignment, and measurable product improvements.

Keep the profile to four or five lines. If you need more space, move the detail into experience bullets or selected projects.

For a UI design role, the portfolio is not optional. Even when the job advert asks for a CV first, the recruiter will usually look for case studies that show interface thinking, not just polished visuals.

Place the link near your name and contact details. Use a clean URL if you have one, or a clear portfolio label if the link is long. Make sure it opens without a password unless the role genuinely needs private work samples. If work is under NDA, create anonymised case studies that explain the problem, process, constraints, and design decisions without exposing confidential information.

Your CV should briefly signpost the same evidence. If your portfolio has a case study on a billing dashboard, your CV bullet might say:

• Redesigned billing dashboard states, empty screens, error messages, and plan comparison UI for a B2B SaaS product, creating reusable Figma components and handover notes for front-end developers.

That line gives the recruiter a reason to look at the case study. It also shows that you understand states and edge cases, which are often more useful than a single polished hero screen.

Do not put large portfolio images inside the CV unless the employer asks for a visual CV. A standard CV should stay readable, ATS-friendly, and easy to scan. Let the portfolio carry the visuals and let the CV carry evidence.

The work experience section should show how you design, not only what you designed. Hiring teams want to see evidence of hierarchy, interaction patterns, accessibility, iteration, design systems, and delivery.

Use each bullet to answer three questions: what did you design, what design decision or process did you use, and what changed as a result? If you cannot share metrics, explain the practical result: clearer handover, fewer repeated components, improved consistency, faster sign-off, stronger accessibility, reduced support confusion, or better alignment with user research.

Useful UI designer bullet angles include:

• improving navigation, forms, onboarding, checkout, dashboards, account areas, or product settings;
• building or maintaining Figma components, variants, styles, tokens, and documentation;
• creating responsive layouts for mobile, tablet, and desktop;
• applying WCAG-aware colour, contrast, focus, keyboard, and target-size considerations;
• producing prototypes for user testing, stakeholder review, or developer handover;
• working with researchers, UX designers, product managers, engineers, content designers, and brand teams;
• designing empty states, loading states, error states, confirmation messages, and transactional journeys;
• translating brand guidelines into scalable interface components.

Here are CV-ready examples you can adapt:

• Created a reusable Figma component set for subscription, billing, and account screens, reducing duplicated design files and giving developers clearer interaction states.
• Redesigned a mobile checkout journey with clearer hierarchy, error messaging, and progress cues, improving sign-off speed across product, engineering, and marketing.
• Audited dashboard UI against design system rules, colour contrast checks, and spacing conventions, then documented fixes for 40+ components and templates.
• Built clickable prototypes for onboarding research sessions, turning observed user confusion into revised navigation labels, form grouping, and empty-state guidance.
• Partnered with front-end developers to prepare responsive handover notes, component specifications, and design QA feedback before release.

Do not exaggerate metrics. If you have numbers, use them. If you do not, focus on the design contribution and the team result. Honest, concrete detail is stronger than unsupported claims.

Many UI designer roles now expect design system awareness. That does not always mean you owned a full enterprise system. It may mean you worked with components, variables, tokens, styles, layout rules, documentation, or contribution processes.

In your CV, explain the scale of your involvement. Maintained design system can mean anything from renaming layers to leading a multi-product component library. A better line says what you actually did:

• Updated button, modal, table, and form components in Figma with variants, usage notes, and responsive behaviour for mobile and desktop layouts.

This tells the reader what you handled. It also helps the hiring team judge whether your experience matches their design maturity. A start-up may need a designer who can build foundations. A larger product team may need someone who can follow contribution rules, document decisions, and protect consistency across teams.

If you are junior, mention how you used an existing system correctly. For example, you might say you applied grid rules, spacing tokens, typography styles, and approved form patterns across a new account area. That is still useful evidence. It shows discipline and respect for standards.

If you are senior, go further. Show governance, documentation, contribution review, visual direction, component strategy, mentoring, or collaboration with engineering. Senior evidence should show that you improved the system, not only used it.

Accessibility should not be hidden in a skills list. UK employers, public sector teams, charities, banks, SaaS companies, and ecommerce brands increasingly expect designers to understand accessible interface decisions. Your CV should show this through examples.

Mention accessibility where it affected the work. You might refer to colour contrast, focus states, keyboard behaviour, target size, form labels, error messages, readable typography, motion, alternative states, or WCAG 2.2 AA awareness. If you worked with disabled users, accessibility audits, assistive technology checks, or specialist accessibility consultants, say so clearly.

A useful bullet might read:

• Revised form labels, error states, focus styles, and colour contrast across an account setup journey, aligning UI decisions with WCAG 2.2 AA principles and improving design QA before build.

That is stronger than saying accessible design in the skills section. It shows where accessibility appeared in your process.

Do not claim expert knowledge unless you have it. If your experience is limited, phrase it accurately: accessibility-aware design, WCAG 2.2 AA familiarity, contrast checking, inclusive UI patterns, or collaboration with accessibility specialists. Careful wording is more credible than inflated expertise.

UI design rarely happens in isolation. Even highly visual roles sit inside a product process. Your UI Designer CV should show that you can work with the people who shape requirements, user needs, content, technical feasibility, and release quality.

Mention UX designers or researchers when their work informed your designs. For example, you might say you used research findings to simplify navigation labels, change form grouping, or revise prototype flows. Mention content designers when microcopy, error messaging, onboarding text, or labels affected interface clarity. Mention developers when your handover improved build accuracy, component reuse, or design QA.

This matters because employers are not only buying visual craft. They are hiring someone who can help a product team move from problem to usable interface. A designer who collaborates well reduces friction and protects quality during delivery.

For a junior designer, evidence might include design critiques, paired work, feedback rounds, and willingness to iterate. For a senior designer, evidence should include stakeholder alignment, cross-team standards, mentoring, and product influence.

A UI Designer CV for a fintech dashboard should not read exactly like one for a fashion ecommerce role. The core skills may overlap, but the proof should change.

For SaaS roles, emphasise dashboards, tables, permissions, settings, onboarding, empty states, and complex flows. For ecommerce roles, show product listing pages, checkout, promotions, mobile journeys, conversion, and brand consistency. For mobile app roles, mention platform patterns, responsive behaviour, navigation, touch targets, and prototype testing. For public sector or charity roles, accessibility, content clarity, inclusive design, and service patterns may matter more.

Read the advert closely. Look for product type, tools, team structure, design system maturity, accessibility expectations, and portfolio requirements. Then reorder your bullets so the most relevant evidence appears first.

Tailoring does not mean rewriting your whole CV each time. It means making stronger editorial choices. Move the right case studies up. Replace generic bullets with role-specific ones. Use the employer's wording where it accurately matches your experience, but do not stuff keywords into every line.

A UI designer's CV should look considered, but it should not become a design experiment. Recruiters still need to scan dates, roles, tools, achievements, education, and links quickly. Applicant tracking systems may also need to read the text.

Use clear headings, consistent spacing, readable type, and a simple column structure. Avoid low-contrast text, tiny type, decorative icons, screenshots, complex sidebars, and background shapes that make the document harder to parse. The CV should prove you understand hierarchy and restraint.

One page is often enough for a junior UI designer. Two pages are fine for mid-level and senior designers if the evidence is strong. Do not squeeze important context into unreadable type just to meet a one-page target. A clean two-page CV is better than a crowded one-page file.

Export the CV as a PDF unless the employer asks for another format. Use a professional file name such as Sophie-Morgan-UI-Designer-CV.pdf. Test all links before you send it.