How to Hire a UX Designer:A Hiring Manager's Complete Guide
Hiring a UX designer is not like hiring an engineer or a marketer. The skills are harder to verify from a resume, the evaluation process requires different tools, and the mistakes are expensive. This guide gives you a practical framework for getting it right.
UX design hiring breaks down in predictable ways. Companies post a generic job description, screen candidates based on aesthetic taste, skip the portfolio walkthrough, and then wonder why the hire did not work out six months later. According to the AIGA Design Census, design roles have among the highest turnover rates in tech, often because companies hire for craft skills but ignore process skills, or vice versa.
The core problem is that most hiring managers evaluate design output (what a designer made) instead of design thinking (how and why they made it). A beautiful portfolio is not evidence of a strong designer. It is evidence of a designer with good visual taste. Whether they can define a problem, conduct user research, navigate cross-functional conflict, and ship work that moves metrics is a different question entirely.
The Google re:Work research on structured interviewing applies here too: structured evaluation processes outperform intuition-based ones, even when evaluating creative roles. The mistake most teams make is treating design as too subjective to evaluate systematically. It is not. You can build a consistent, fair, and predictive hiring process for design roles. This guide shows you how.
Before you post a job, read the section on defining the role. Most companies hire the wrong type of designer because they wrote the wrong job description. If you already have a clear picture of what you need, jump to the portfolio review framework or the interview question section. For context on how design hiring fits into a broader hiring process, that guide covers the full funnel.
Step One
Define the actual role before you write the job description
The titles UX designer, product designer, UI designer, and UX researcher get used interchangeably in job postings, but they describe meaningfully different roles. Hiring a UI designer when you need someone to conduct user research wastes everyone's time. Before you write anything, answer these four questions:
Do you need someone to talk to users, or someone to translate existing insights into designs?
Do you need someone who can handle visual design and branding, or someone focused on flows and information architecture?
Do you need a generalist who can own end-to-end design work, or a specialist who goes deep in one area?
Will they work alone or collaborate with other designers?
Most early-stage companies need a product designer: someone who can do research, wireframing, and high-fidelity UI. Larger teams often hire specialists. The spectrum below shows what each role typically emphasizes.
User research, usability testing, data synthesis
Needs: strong interview skills, statistical comfort
Wireframes, user flows, information architecture
Needs: systems thinking, research literacy
End-to-end: research through high-fidelity UI
Needs: full-stack design skills, product instinct
Visual design, design systems, component libraries
Needs: strong aesthetics, Figma mastery
Once you know the type, get specific about the work. The most useful thing you can put in a job description is a "day in the life" description: what will this person actually do in week one, month three, and month twelve? Vague descriptions like "you will own the design process" attract the wrong candidates and set up unrealistic expectations.
On tools: Figma has become the standard for most product design work. If you require other tools, state them. Do not list Adobe XD, Sketch, and Figma as equal requirements. Pick the one your team uses and filter for it. For tips on writing job descriptions that attract the right candidates, see our job description guide.
Step Two
Where to find strong UX designers
Strong designers are rarely unemployed and actively job hunting. Most are employed, doing good work, and open to the right opportunity. That means passive sourcing matters more here than in most roles.
Portfolio sites: Dribbble and Behance
Both have talent search and direct messaging. Dribbble skews more visual/UI. Behance has broader representation including UX-heavy case studies. Search by skill tags ("user research", "product design") and filter by location. The quality signal here is the portfolio, not the profile stats.
LinkedIn with design-specific filters
Use the job title filter strictly. Search for 'Product Designer' or 'UX Designer' with current company signals that match the complexity you need. Designers who have worked at product companies (not just agencies) are often better prepared for embedded team work.
Design communities
Designer Hangout (Slack), AIGA chapters, and local design meetups are underused sourcing channels. Posting in community job boards often reaches mid-career designers not actively browsing LinkedIn. These channels also let you see how designers engage in professional conversations before you reach out.
Internal referrals from your engineering team
Engineers who have worked with great designers know exactly who they want to work with again. Ask your product and engineering team specifically. This referral network is different from general employee referrals and often surfaces excellent candidates who are not applying anywhere.
One sourcing note: job boards work for entry-level and some mid-level hiring. For senior designers, direct outreach on Dribbble or LinkedIn beats posting and waiting. The best senior designers rarely need to apply. You have to find them and make a compelling case for why your team and problem are worth their time. For a broader look at passive candidate sourcing, see our guide on sourcing passive candidates.
Step Three
Structure your hiring process in five stages
Most companies run too many or too few stages for design roles. Four to five stages is the right range. Fewer than four and you miss critical evaluation signals. More than five and you lose candidates to faster-moving teams. Here is the process that works.
Does their past work match your product type and complexity?
Motivation, logistics, salary alignment, and process fit.
Deep portfolio walkthrough and role-fit discussion.
Paid take-home or live problem-solving session.
Cross-functional team evaluates craft, process, communication.
The portfolio screen happens before any human conversation. You are filtering for: does their past work match the product complexity, user type, and design maturity your role requires? A designer who worked on B2C mobile apps is not automatically a fit for a complex B2B SaaS product. Domain translation happens, but it takes time. Be honest about whether you have room for that ramp.
The hiring manager interview at stage three is where most design interviews go wrong. Do not use this as a general conversation. Use it as a structured portfolio walkthrough. Ask the candidate to walk you through one or two case studies in detail. Interrupt and probe: "Why did you choose that approach over alternatives?" and "What would you have done differently with more time?" The answers reveal process thinking, not just output quality.
Keep your total process under three weeks. Top designers have options. A process that drags to six weeks sends a signal about how your company operates. Use a good applicant tracking system to keep stages moving and candidates informed. Radio silence between stages costs you candidates who are also talking to your competitors.
Step Four
How to evaluate a design portfolio
The most common portfolio review mistake is evaluating aesthetics when you should be evaluating thinking. A portfolio full of beautiful screens tells you the designer knows how to make things look good. It does not tell you whether they can define problems, collaborate with engineers, handle ambiguity, or ship work that drives outcomes. Use this four-part framework.
Does the case study explain the problem before the solution?
Clear problem statement with user context and constraints
Jumps straight to wireframes without explaining why
Can you see how they think, not just what they made?
Research, iteration, decision rationale shown explicitly
Only polished final screens, no messy middle
Do they measure the impact of their design decisions?
Metrics cited: conversion rate, task completion, NPS change
Vague claims like 'improved user experience'
Is their specific contribution clear in team projects?
'I led the IA work while my colleague handled visual design'
'We designed the product' with no individual attribution
A few practical notes on portfolio review. First, look at the oldest work, not just the newest. The progression from their first case study to their most recent one tells you about growth trajectory. A designer whose work has meaningfully improved shows learning agility. One who shows the same quality across five years might be competent but plateaued.
Second, watch for portfolio pieces that were not shipped. Concept projects and student work belong in a junior designer's portfolio. Mid-level and senior designers should primarily show real work that went through production, user testing, and iteration. Unshipped concepts do not tell you whether they can navigate real-world constraints.
Third, do not penalize designers for protected work. Many enterprise and fintech designers cannot show their actual screens publicly. If they describe their NDA situation clearly and offer to walk through work privately or with context, that is reasonable. Ask them to talk through one case study without showing the visuals. You will learn more from the conversation than from the screens anyway. For guidance on maintaining consistency across candidates, see our interview scorecard guide.
Step Five
Running a design exercise that actually predicts performance
Design exercises are the UX equivalent of a technical screen. Done well, they reveal how a designer approaches ambiguity, communicates decisions, and handles feedback. Done badly, they extract free work and waste everyone's time.
My view on take-home vs. live: if your budget allows, offer a paid take-home with a $100 to $200 stipend for 3 to 4 hours of work. This compensates candidates for their time and signals that you value design work. If budget does not allow, a 60-minute live session works too, but give the candidate the brief 24 hours in advance so they can come prepared rather than panicking under pressure.
Do not use your actual product problems
Asking candidates to design a feature you are actively building is unpaid labor. It also creates legal complexity around IP. Design a fictional brief that tests similar skills. Many companies reuse the same brief for years without issue.
What makes a good brief? Keep it constrained and ambiguous in the right ways. Give them a user type, a problem space, and a business goal. Do not prescribe the solution. A good brief might be: "Design the onboarding flow for a B2B project management tool targeting 5-person agencies. The main drop-off in our data is between account creation and first project setup." That brief has constraints (user type, product type, specific problem) without telling them what to design.
During the review, watch for the signals below. They predict performance far better than the quality of the final designs.
- Asks clarifying questions before diving in
- States assumptions explicitly
- Considers multiple approaches before picking one
- Frames the problem before sketching solutions
- Thinks about edge cases and error states
- Articulates trade-offs, not just decisions
- Jumps to solutions without defining the problem
- Designs only the happy path
- Cannot explain why they made specific choices
- Asks no questions about users or context
- Treats the exercise as a pixel-pushing task
- Gets defensive when the interviewer probes assumptions
Step Six
Interview questions that reveal how designers actually think
Most UX designer interview questions test trivia about design methods rather than actual design thinking. "Explain the double diamond model" tells you nothing about whether someone can solve a real problem. These questions do.
Process & Research
Walk me through how you decided what to design first on your last project.
What to listen for: Are they prioritizing based on user data and business goals, or just gut feel? Good designers articulate a clear decision framework.
Tell me about a time when user research changed a decision that had already been made.
What to listen for: This tests whether they actually use research to drive decisions or treat it as a checkbox. The best answers show how research changed direction mid-project.
How do you handle situations where you have no time for research?
What to listen for: Good designers have mental models for making informed decisions under time pressure. Red flag: 'I just design based on best practices' without any user input.
Collaboration & Communication
Describe a time you disagreed with a product manager about a design direction. What happened?
What to listen for: You are looking for someone who advocates for users with evidence, not someone who either capitulates immediately or digs in defensively.
How do you communicate design decisions to engineers who are skeptical about timelines?
What to listen for: This tests cross-functional communication. Strong designers understand engineering constraints and frame design rationale in terms engineers care about.
What do you do when you get conflicting feedback from different stakeholders?
What to listen for: Watch for whether they go back to user data and business goals as a tiebreaker, or whether they default to whoever is most senior.
Craft & Standards
Show me a design decision in your portfolio that you think was wrong in hindsight.
What to listen for: Self-awareness about past work is one of the best predictors of future growth. Designers who defend every decision uncritically tend to plateau.
How do you decide when a design is good enough to ship?
What to listen for: You want someone who understands that perfect is the enemy of shipped. The best designers talk about measurable quality thresholds and iteration post-launch.
For the panel interview, assign each interviewer a specific evaluation dimension: one person owns research and process, another owns collaboration and communication, a third owns craft and quality standards. This prevents everyone from asking similar questions and ensures you cover the full picture. Use a consistent structured interview approach to make comparisons across candidates reliable.
Step Seven
Compensation, offers, and closing design candidates
Design compensation has grown significantly over the past decade. The Levels.fyi data for product designers at major tech companies shows total compensation ranging from $150,000 for entry-level at FAANG to well over $350,000 for staff designers. Startups and non-tech companies run considerably lower in cash compensation but often compete on equity, mission, and growth opportunity.
Mid-level designers at growth-stage startups in major US markets typically expect $110,000 to $145,000 in base salary. Senior designers expect $145,000 to $185,000. If you are outside a major tech hub or working with a services company, adjust down by 20 to 30 percent. Check the AIGA Design Census for non-tech benchmarks and the Glassdoor design salary data for real-time market ranges.
Three things that close design candidates beyond compensation:
Design influence
Designers want to work where design decisions actually shape the product. Explain concretely how design has changed product direction in the past year. Specific examples beat vague promises.
Tooling and process maturity
Strong designers want a functioning design system, clear handoff processes, and time for research. Show them your current setup honestly. Hiding process gaps leads to early attrition.
Growth trajectory
Where can they be in 18 months? Can they become a design lead? Will they work on harder problems with more scope? Growth opportunity matters more than a $10,000 salary bump to most mid-career designers.
One tactical note on offers: send the offer letter quickly. Design candidates with strong portfolios are often interviewing with three to five companies simultaneously. A two-day gap between verbal offer and written offer letter loses candidates to faster-moving teams. For best practices on structuring an offer that closes, see our offer letter guide. For candidate experience considerations that affect offer acceptance rates, that guide covers the full picture.
What Goes Wrong
Six UX hiring mistakes that cost teams their best candidates
Hiring for style match instead of skill match
If the designer you hire makes work that looks like work your team already makes, you are replacing capacity, not adding capability. The best design hires bring perspectives you do not already have.
Evaluating final screens instead of the design process
Polished Figma files are cheap to produce. The question is whether the designer can diagnose the right problem, involve users, and make decisions under pressure. That only shows up when you probe the process.
Running a 6-round process for a mid-level role
Every extra interview stage costs you candidates. Three to four stages, completed within three weeks, is the right benchmark for most design roles. More than that signals operational dysfunction to experienced candidates.
Not involving the design team in the evaluation
If you have existing designers, they should be involved in the panel stage. They will catch craft signals and cultural fit factors that non-designers miss. And the candidate will want to meet the team they will actually work with.
Using unpaid design exercises on real product problems
This is both ethically problematic and legally risky. Build a fictional brief, compensate candidates for their time, and respect that strong designers have other options. Unpaid work requests filter out confident candidates who know their worth.
Ignoring domain fit
A designer who spent five years in consumer social apps is not automatically a fit for an enterprise B2B SaaS product. The user research methods, design patterns, and stakeholder dynamics are different. Ask directly how they think about domain transition and whether they have adjacent experience that would transfer.
Frequently Asked Questions
What is the difference between a UX designer and a product designer?
The terms overlap significantly, but product designer usually implies broader ownership: research, wireframing, visual design, and sometimes light front-end work. UX designer often (not always) means a stronger focus on research and information architecture with less emphasis on final visual execution. In practice, check the job descriptions of the specific companies where a candidate has worked. The title tells you less than the portfolio.
Should we use a take-home assignment or a live design exercise?
Both have merit. Take-home assignments let candidates work at their own pace and show polished thinking, but they favor people with more free time and create unpaid labor concerns. Live exercises reveal how someone thinks in real time and reduce bias from over-polish. My recommendation: offer a paid take-home (3 to 5 hours, $100 to $200 compensation) or a structured live session with clear time limits. Never ask candidates to solve your actual product problems for free.
How many portfolio pieces should a strong UX designer have?
Three to five well-documented case studies beat ten shallow ones every time. You want depth over breadth. Each case study should show the problem, the process, key decisions, trade-offs, and outcomes. A designer with three excellent case studies that show real impact is stronger than one with ten that only show final screens.
What Figma skills should we expect from a mid-level UX designer?
At the mid-level, expect strong component-based design, auto-layout proficiency, basic prototyping for user testing, and the ability to work within an existing design system. You should not expect them to build complex design systems from scratch. Senior designers should be comfortable creating and documenting design tokens, building reusable component libraries, and managing handoff with engineering.
How do we evaluate UX research skills if we only need a generalist designer?
Ask them to walk you through how they approached user research on a past project. You are not checking for academic rigor. You want to see: did they talk to actual users? Did they synthesize findings into insights, not just data? Did their research change any design decisions? A generalist who ran five user interviews and adjusted navigation based on findings is more valuable than one who never left Figma.
What salary should we budget for a UX designer?
Ranges vary significantly by location, company size, and designer seniority. In 2025, mid-level UX designers at US tech companies typically earned between $95,000 and $145,000 in base salary. Senior designers ranged from $140,000 to $185,000. Agencies and non-tech industries run 20 to 30 percent lower. Check Glassdoor, Levels.fyi for public companies, and the AIGA Design Salary Survey for current benchmarks in your market.
Resources & Further Reading
Related Guides
- Structured Interviews: How to Build a Process That Actually Predicts Performance
Use structured evaluation across all design interview stages
- Interview Scorecard: Build One That Predicts Performance
Create consistent scorecards for portfolio and exercise review
- How to Source Passive Candidates
Reach designers who are not actively applying
- How to Write Job Descriptions That Attract the Right Candidates
Write a design JD that filters effectively
External Sources
- AIGA Design Salary Survey
Industry benchmark compensation data for design roles
- Levels.fyi Design Compensation
Crowdsourced total compensation data for designers at tech companies
- Google re:Work: Structured Interviewing
Research on why structured evaluation beats intuition
- Nielsen Norman Group: UX Career Paths
Understanding specializations and career trajectories in design
Hire UX designers faster with AI screening
Prepzo screens design candidates automatically, routes portfolios to the right reviewers, and keeps your pipeline moving without manual follow-up. Free to start.
Try Prepzo free