Hiring guide
How to Hire a UI Designer
How to hire a UI designer: where to source, the visual and design-system skills to test, a component-and-screen work sample, red flags and onboarding.

The short answer
Hiring a UI Designer comes down to verifying visual hierarchy, typography and colour, figma components, variants and auto layout and building and maintaining design systems before you commit interview time. The process below runs 5 stages, screens on evidence rather than résumé claims, and scores every candidate against the same criteria.
- Watch for: Portfolio full of single hero shots with no error, empty, loading or disabled states
- Watch for: Figma files with detached components, inconsistent spacing and unnamed layers
- Score on: Visual quality: hierarchy, spacing, type and colour
- Score on: Correct and consistent use of your components and styles
Paste your UI Designer job description; Cohesyve finds, contacts and tests candidates on the real work and ranks them. Ten candidates free, no card.
Applying for a role like this? Practise the assessment free →To hire a UI designer, test visual craft and systematic thinking together: can the candidate design screens that look sharp, read clearly and hold together as a consistent set of components that engineers can build? A portfolio of beautiful one-off shots does not answer that. This guide covers where to find UI designers, the skills that matter, a practical work sample, red flags and onboarding.
Why this role matters
A UI designer turns flows and wireframes into the screens, components and states people actually see and use. Their choices on layout, type, colour, spacing and interaction states decide whether a product feels clear and trustworthy. Good UI work, built on a solid design system, also speeds up engineering and keeps the product consistent as it grows.
Where to find candidates
- Dribbble and Behance, filtering for app and web interface work
- LinkedIn and Dribbble Jobs for in-house and agency roles
- Figma Community, where many designers publish UI kits and design systems
- IxDA local groups and design meet-ups
- Design and digital recruitment agencies
- Front-end engineers in your network, who often know designers with good handoff habits
Skills to look for
Red flags
- Portfolio full of single hero shots with no error, empty, loading or disabled states
- Figma files with detached components, inconsistent spacing and unnamed layers
- Ignores accessibility, such as low-contrast text or tiny tap targets
- Cannot explain how a design adapts to mobile and desktop
- No experience working from or contributing to an existing design system
The interview process
- 1
Portfolio screen
Look for complete screens and flows in real products, not only showcase shots. Ask for a Figma file or link if possible to see how they structure work.
- 2
File walkthrough
Have the candidate share their screen and walk through a real Figma file: components, variants, naming, styles and how they handled responsive layouts. This reveals working habits quickly.
- 3
UI work sample
Give a wireframe of one screen from your product plus your component library or style guide. Ask for a finished design including empty, error and loading states, at mobile and desktop widths. A job simulation of the real work is one option if you want every candidate to tackle the same screen.
- 4
Engineering and product interview
Ask a front-end engineer to discuss handoff, design tokens and edge cases, and a product manager or product designer to discuss how they take direction on flows.
- 5
References
Ask previous teams about attention to detail, consistency and how smoothly their designs were built.
Cohesyve
Start the UI Designer interviews from a ranked shortlist
Cohesyve takes your UI Designer job description, finds and contacts candidates and tests each one on an AI job simulation of the job, so the stages above start with people who have already done the work. Ten candidates free, no card.
How to evaluate
- Visual quality: hierarchy, spacing, type and colour
- Correct and consistent use of your components and styles
- Coverage of states and responsive behaviour
- Accessibility of contrast, sizes and focus states
- Organisation and naming in their Figma file
- Clarity of handoff notes for engineers
Onboarding
- 1Walk through the design system, tokens and contribution rules in the first week
- 2Give access to Figma libraries, the front-end component library and staging environments
- 3Start them on a contained UI task that touches existing components
- 4Pair them with a front-end engineer to review a build against their design
- 5Schedule regular design critiques for consistent feedback
Common questions
What is the difference between a UI designer and a UX designer?
A UI designer focuses on the visual interface: layout, type, colour, components and states. A UX designer focuses on research, user flows and structure. Many roles blend both.
Do UI designers need to know front-end code?
It is not required, but knowing how HTML, CSS and component libraries work helps them design layouts and tokens that engineers can build accurately.
Which tools should a UI designer know?
Figma is widely used in product teams. Familiarity with prototyping features, design tokens and handoff tools matters more than knowing many apps.
Should I hire a UI designer or a product designer?
Hire a UI designer if flows and research are already covered and you need stronger visual craft and system work. Hire a product designer if you need one person to own problems end to end.
Cohesyve · Skill assessments for hiring
Hiring a UI Designer? Start with a ranked shortlist
Cohesyve takes your UI Designer job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then ranks them for you.
1,500+
assessments completed
50%
faster time-to-hire
5 min
from JD to assessment
No credit card · 10 free candidates · Plans sized to your hiring volume
From the blog