Hiring Guide

How to Hire a UX Designer

To hire a UX designer, start from a portfolio review that prioritizes thinking over polish, then run a design challenge or whiteboard exercise plus a portfolio walkthrough. Look for clear problem framing, research-driven decisions, and the ability to explain trade-offs. Verify they collaborate with engineers and PMs, and reference-check that the shipped work matches their case studies.

Where do you source good UX designers?

Strong UX designers congregate where their work is visible: Dribbble, Behance, and personal portfolio sites, plus design communities and Slack groups. The most reliable signal is the portfolio itself, so let candidates apply with a link rather than forcing a long form. Referrals from your existing designers and design-conscious PMs are gold because design talent clusters socially and people know each other's real abilities.

How do you read a UX portfolio for thinking, not just pretty screens?

A polished portfolio can hide weak process, so read case studies for the problem framing, the research that informed decisions, the alternatives considered, and the measured outcome, not just the final mockups. Ask who did what; a lot of 'team' portfolios overstate the individual's contribution. The strongest case studies show messy middle states, rejected directions, and a clear narrative of why the final design solves a real user problem.

What's the right way to run a UX design challenge?

Use a portfolio walkthrough plus a focused design exercise rather than a giant unpaid take-home. A live or short whiteboard challenge ('redesign this onboarding flow given these constraints') reveals how they ask clarifying questions, frame the problem, and reason about edge cases under light pressure. Pay for anything substantial. Watch whether they design for real constraints and accessibility, not just the happy path on a perfect-sized screen.

Which skills are essential versus learnable for a UX designer?

Essential: user empathy, interaction and information architecture fundamentals, the ability to justify decisions, and collaboration with PMs and engineers. Learnable on the job: a specific tool (Figma versus older tools), your exact domain, and your component library. Distinguish UX (research, flows, IA, usability) from pure UI or visual design; many 'UX/UI' candidates are strong at visuals but thin on research and systems thinking, so probe for both.

How do you close a UX designer and set the timeline?

Plan four to seven weeks; portfolio review front-loads the funnel, so most filtering happens early. Designers care deeply about craft culture, whether design has a real seat at the table, and whether their work will actually ship rather than be overruled. Show them recent work the team shipped and let them meet the PM and an engineer. Closing is about convincing them their best work will see the light of day here.

The hiring process for a UX Designer

  1. 1
    Define UX vs UI scope Clarify whether you need a researcher-leaning UX designer, a product designer who spans research-to-UI, or primarily a visual designer, and write the JD to match.
  2. 2
    Portfolio-first screen Require a portfolio link and screen for case studies that show problem framing, research, and outcomes rather than only finished pixels.
  3. 3
    Portfolio walkthrough interview Have them present one project deeply, drilling into their specific contribution, the alternatives they rejected, and how they measured success.
  4. 4
    Run a focused design challenge Give a short, scoped exercise (ideally live) that tests problem-framing, clarifying questions, edge cases, and accessibility rather than a sprawling unpaid take-home.
  5. 5
    Cross-functional collaboration check Have a PM and an engineer interview to assess whether the designer communicates rationale and partners well under real constraints.
  6. 6
    Reference and close on craft culture Reference-check that shipped work matches the portfolio, then close by showing design's influence and recently shipped work.

What to look for

  • Case studies explain the problem and research before showing any UI
  • Can clearly separate their individual contribution from the team's work
  • Asks clarifying questions and surfaces constraints before jumping to solutions
  • Considers accessibility, edge cases, and error states, not just the happy path
  • Explains design decisions in terms of user needs and business goals, not taste
  • Talks fluently about working with engineers and PMs to ship real designs
  • Shows rejected directions and iteration, demonstrating genuine process

Red flags to avoid

  • !Portfolio is all polished final screens with no process, research, or rationale
  • !Vague about what they personally did versus what the team delivered
  • !Jumps straight to high-fidelity solutions without framing the problem
  • !Dismisses accessibility or treats it as someone else's job
  • !Can't point to anything they designed that actually shipped to users
  • !Designs in a vacuum and bristles at engineering or PM constraints as 'compromises'
FAQ

Frequently asked questions

What's the difference between a UX designer and a UI designer? +
A UX designer focuses on the overall experience: research, user flows, information architecture, and usability. A UI designer focuses on the visual layer: layout, typography, color, and components. Many candidates blend both as 'product designers,' so define which depth you actually need and test for it rather than trusting the title.
Do I need a separate UX researcher, or can a designer do both? +
At smaller scale, a strong product designer can run lightweight research themselves. Once you're making high-stakes decisions or have many designers, a dedicated researcher pays off. If you expect your designer to do research, screen explicitly for research methods and evidence of real user testing in their case studies.
Should I give a paid take-home or a live design challenge? +
A short live or whiteboard challenge often reveals more about how a designer thinks and asks questions, and it avoids unpaid-labor concerns. If you need a take-home, keep it small and pay for it. The goal is to see reasoning under realistic constraints, not to extract free design work.
How important is Figma proficiency? +
Tool fluency is genuinely easy to pick up for a strong designer, so don't filter hard on a specific tool. Figma is the current standard and most candidates already use it, but prioritize design thinking, research, and collaboration. A great designer learns your tooling in days; weak fundamentals never improve as fast.
Built for recruiters & hiring teams

See how much faster your team could hire

Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.

Prefer to talk? Book a demo · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Sign up free Book a demo