How to Hire a UX Designer: Skills, Interview Questions & Where to Find Talent

Hiring a UX designer starts with figuring out whether you actually need a generalist, a UX researcher, an interaction designer, or someone who’s really more UI than UX, because posting for the wrong one is the fastest way to waste two months and $15,000 in recruiter time. Evaluate candidates through live portfolio deep-dives and scenario-based questions rather than take-home design challenges that senior designers won’t bother completing, and source from design-specific platforms like Dribbble, Behance, ADPList, and the Figma Community rather than generic job boards where your posting drowns in 200 irrelevant applications. Mid-level UX designers pull $91,000 to $125,000 in most markets, with senior practitioners at $135,000 to $180,000 depending on industry and geography.

Last year a client in Irvine called us three weeks into a UX designer search that was already sideways. They’d posted the role on LinkedIn, gotten 140 applications, phone-screened 22 people, and brought four in for interviews. All four had beautiful Dribbble profiles. Gradient-heavy mockups, slick animations, concept redesigns of apps they’d never actually worked on. The hiring manager loved the portfolios. Then she asked each candidate to walk through how they’d approach redesigning the company’s onboarding flow for a B2B logistics platform. Two of them froze. One pivoted to talking about “design thinking methodology” for ten minutes without ever asking a clarifying question about the users. The fourth asked three smart questions, sketched a rough research plan on the whiteboard, and got hired. She lasted four months before quitting because the role was 80% user research and stakeholder interviews and she wanted to be pushing pixels in Figma.

Wrong hire. Not because of the candidate. Because the job description said “UX Designer” when the company actually needed a UX researcher who could occasionally prototype. That distinction matters more than most hiring managers realize, and it’s the reason roughly half the UX searches we see through our digital and creative staffing practice at KORE1 take longer than they should, burn through three or four finalist candidates who looked perfect on paper, and end with the hiring manager calling us and saying “none of them were right” when the problem was always the job description, not the candidates.

What Does a UX Designer Actually Do?

A UX designer researches how people interact with a product, identifies friction points and unmet needs, then designs interfaces and workflows that solve those problems. The role sits between user research, visual design, and product strategy, and the exact balance depends on the company’s size and how mature their design practice is.

At a 30-person startup, the UX designer does everything: research, wireframes, prototyping, usability testing, visual polish, handoff to engineering, and probably some front-end CSS when the dev team is underwater and the product manager is begging someone to just fix the mobile nav before the investor demo on Thursday. At a company with 200+ employees and a dedicated design org, UX designers tend to specialize. One person owns the research. Another owns interaction design. A third handles the design system. The title is the same on LinkedIn. The actual jobs share maybe 40% overlap.

This is where hiring breaks down. A job posting that says “UX Designer” without specifying where on that spectrum the role sits will attract the wrong candidates. Every time. We’ve watched it happen with enough regularity that we now ask clients to describe a typical Tuesday before we even look at the job description, because the job description almost never matches the actual day-to-day work and the gap between the two is where bad hires get made. What does this person actually do between 9 a.m. and 5 p.m.? If the answer involves the words “stakeholder alignment” and “user interviews” more than “Figma” and “prototyping,” you don’t need a UX designer. You need a UX researcher. Different candidate pool entirely.

The Bureau of Labor Statistics groups UX under “web developers and digital designers” and projects 7% growth through 2034, with roughly 14,500 openings per year. That growth number understates the demand for UX specifically, because BLS lumps front-end developers, web designers, and UX practitioners into one bucket. The companies actually hiring for UX roles are competing for a smaller pool than the BLS numbers suggest.

UX Designer Skills Worth Testing For

Every job posting lists the same skills. User research. Wireframing. Prototyping. Figma. “Strong communication skills.” That list is technically correct and practically useless for evaluating candidates, because every UX designer with six months of experience will claim proficiency in all of them. The question isn’t whether someone lists these skills. The question is how deep the proficiency goes and whether they can apply it to your specific product context.

Here’s what actually separates a hire you’ll keep from a hire you’ll regret.

User research execution, not just awareness. Every candidate will tell you they’re “user-centered.” Ask them to describe the last usability study they ran. How many participants. How they recruited them. What they did with the findings. A strong answer includes specific numbers: “We ran moderated sessions with eight users over two weeks, identified three critical drop-off points in the checkout flow, and the redesign reduced cart abandonment from 34% to 19%.” A weak answer sounds like a textbook chapter. “I believe in empathizing with users and understanding their pain points.” That’s not research. That’s a LinkedIn headline.

Information architecture is an underrated filter. Can they organize a complex product into a navigation structure that makes sense to someone who’s never seen it before? We had a candidate last quarter who aced every visual design test but completely fell apart during a card-sorting exercise for a healthcare dashboard with 47 distinct data views. She organized the entire thing by internal team structure rather than by clinical workflow. Logical from a developer’s perspective. Unusable for a nurse trying to check vitals during rounds. That gap between “I can design screens” and “I can organize systems that make sense to someone who’s stressed, distracted, and has twelve other things happening at the same time” is where a lot of mid-level candidates get stuck and where the interview process needs to push harder than most hiring managers think to push.

Figma proficiency beyond the basics. Figma’s own 2026 design statistics show it dominating the market for interface design and prototyping. Knowing Figma isn’t differentiating anymore. What differentiates is whether a candidate can build and maintain a component library with proper auto-layout and variant nesting, set up design tokens that map to the engineering team’s CSS variables so handoff doesn’t require a two-hour meeting every sprint, and create interactive prototypes with realistic state transitions and conditional logic rather than the click-through wireframes that tell you nothing about how the product actually feels to use. Ask to see their Figma file structure. Messy files with 200 unnamed layers tells you more than a polished case study ever will.

Accessibility knowledge. Not optional anymore. WebAIM’s annual audit found that 94.8% of the top million homepages still fail basic WCAG 2 standards. Lawsuits over inaccessible digital products have spiked, and the companies that haven’t been sued yet are scrambling to make sure they aren’t next. A UX designer who can’t explain color contrast ratios, keyboard navigation, or screen reader considerations is a designer who’s going to create work that has to be redone. Ask about WCAG during the interview. The candidates who hesitate are telling you something.

Interaction design and micro-interactions. Can they think about what happens between screens, not just what’s on them? Loading states, error handling, empty states, progressive disclosure. One of our placed candidates redesigned a SaaS onboarding flow and the client told us the single biggest improvement wasn’t the new layout. It was the inline validation on form fields that told users what was wrong before they hit submit. Small. Specific. The kind of thing that only happens when someone is thinking about the experience as a sequence rather than a set of screens.

Data fluency. Not data science. But a UX designer who can pull a Mixpanel funnel report, read a heatmap, and use analytics to prioritize which part of the product to redesign next is worth substantially more than one who waits for a product manager to hand them a brief. The Nielsen Norman Group’s State of UX 2026 report noted that senior UX roles are recovering faster than junior positions precisely because companies want designers who bring analytical judgment, not just artifacts.

UX Designer Salary: What Four Sources Say (And Why None of Them Agree)

Four databases, four different numbers. The disagreement is informative once you understand what each source is actually measuring.

$25,000 gap between PayScale’s average and Glassdoor’s. That’s not noise. PayScale draws heavily from self-reported data across all company sizes and geographies, including design agencies in the Midwest paying $65K for a “UX/UI designer” who’s really doing production graphic design with some wireframing mixed in. Glassdoor’s sample leans toward the companies where people bother to leave reviews, which skews toward larger employers in coastal metros.

For hiring budgets, the ZipRecruiter range is probably the most actionable because it reflects active postings rather than historical reports. If you’re posting a mid-level UX designer role and your budget is under $90K, you’re going to struggle in any major metro. $105K to $120K is the sweet spot where you’ll get qualified candidates without overpaying for the market. Senior UX designers with 7+ years and a design leadership track record pull $135K to $180K depending on industry. Fintech, healthtech, and enterprise SaaS pay at the top of that range. Agencies and non-profits sit well below it.

Use our salary benchmark tool to check current ranges for your specific market and seniority level.

Interview Questions That Reveal What Portfolios Can’t

Portfolios lie. Not intentionally, usually. But a polished Behance case study is a curated narrative. The messy parts got edited out. The stakeholder who vetoed the best solution doesn’t appear. The research that got cut because of timeline pressure is never mentioned. The interview is where you find out what actually happened versus what made the final presentation deck.

These questions are ones we’ve refined over roughly 200 UX placements. They’re grouped by what they reveal, not by difficulty.

Research and Discovery

“Walk me through the last time you had to change direction mid-project because of something you learned from user research.” You’re looking for intellectual honesty. Did they actually pivot, or did they just validate what they already planned to build? The best answers include a specific finding that surprised them and what they did about it. Bad answers sound like “We confirmed our hypothesis through user testing.” That’s not research. That’s confirmation bias with a budget.

“You have two weeks and $2,000 to understand how nurses use the medication dispensing system in this hospital. What do you do?” Constraints reveal methodology. Candidates who immediately say “I’d run a survey” are showing you their default, which is the cheapest and fastest method that also produces the least useful data for understanding a physical workflow in a high-stress clinical environment where the people using the system have about forty-five seconds of attention to give you between patients. Candidates who ask clarifying questions first (“Are we allowed to shadow them on the floor? Can we access their existing workflow documentation? Is there an EMR system we need to integrate with?”) are showing you how they actually think about research design. The dollar amount is intentional. It’s low enough that they can’t default to “I’d hire a research firm.”

Design Process and Problem-Solving

“Show me a project where the final design was significantly different from your initial concept. What changed and why?” The candidates who can’t answer this haven’t been challenged enough. Real design work involves killing your darlings. If every project ended up looking like the first wireframe, they were either designing in a vacuum or nobody was giving them feedback. Neither is great.

“How do you decide when a design is done enough to hand off to engineering?” This is a question about judgment, not process. “When the stakeholders approve” is a mediocre answer. “When usability testing shows task completion above our threshold and the design system components are documented in Figma with proper specs” is a better one. The best answer acknowledges that “done” is a tradeoff between quality and shipping speed and that the answer changes depending on what you’re shipping.

Collaboration and Communication

“Tell me about a time a developer pushed back on your design. What happened?” Every UX designer has this story. The answer tells you whether they view engineering as a constraint to fight or a partner to collaborate with. “I explained why the design was important and they implemented it” is a red flag. “We found a middle ground that preserved the core interaction pattern but simplified the front-end implementation by about 40%” is what you want to hear, because it means they understand that design doesn’t exist in a vacuum and that implementation cost is a design variable.

“How would you present a research finding that contradicts what your VP of Product has already committed to the board?” Political skill matters. UX designers who can’t navigate organizational dynamics don’t last, no matter how talented they are. You’re not looking for someone who avoids conflict. You’re looking for someone who can frame a difficult truth in a way that gives leadership an off-ramp without making them feel ambushed.

The Portfolio Deep-Dive (Do This Instead of a Take-Home)

Take-home design challenges are losing favor with good candidates. Senior designers won’t do them. They have three other offers and no patience for spec work. What works better is a 45-minute live portfolio deep-dive where you pick one case study and drill into the parts they didn’t put on the slide.

Questions that expose real depth versus presentation polish:

• “What did you cut from this project and why?”
• “Show me the version of this design that got rejected.”
• “What would you do differently if you had twice the timeline?”
• “Which metric moved after this shipped?”
• “Who on the team disagreed with this approach?”

If they can answer all five with specific, detailed responses, they did the work. If they get vague after the second question, someone else on the team carried the weight and this person was involved enough to put it in a deck but not enough to explain what got cut, what failed, or what the engineer said when they saw the first round of specs.

Where to Find UX Designers Worth Hiring

The source matters more for UX than for most roles. A software engineer’s GitHub profile tells you something useful. A UX designer’s LinkedIn profile tells you almost nothing. The work lives in portfolios, communities, and platforms that general recruiters don’t know exist.

Design-Specific Platforms

Dribbble. Over a million designers. The talent directory lets you filter by specialization, location, and availability. Strong for visual and interaction designers. Weak for UX researchers, who tend not to post visual work because their output is research reports and journey maps, not interface shots. If your role is research-heavy, Dribbble will waste your time.

Behance skews toward visual design portfolios but has better case study depth than Dribbble. Candidates who post full case studies with problem statements, research findings, and outcome metrics are the ones worth contacting. Candidates who post only final screens are showing you art direction, not UX work.

ADPList and Designer Hangout. Community platforms where experienced designers mentor and network. The people active in these communities tend to be senior practitioners who aren’t job-searching on Indeed. Posting in these communities or reaching out to active members directly can surface candidates you’d never find through job boards, because the people mentoring other designers for free on a weeknight are usually the senior practitioners who stopped job-searching on Indeed three promotions ago and will only move for something they hear about through their network. It takes more effort. The candidate quality is higher.

Figma Community. Underutilized for recruiting. Designers who publish reusable components, design system templates, and plugins on the Figma Community page are demonstrating exactly the kind of systems thinking and technical proficiency that matters in a production UX role. Go browse. Filter by “design systems.” Contact the people building tools other designers use.

Job Boards That Actually Work for Design Roles

LinkedIn is table stakes but the signal-to-noise ratio is brutal. You’ll get 150 applications and maybe 8 are worth screening. The platform works better for outbound sourcing than inbound postings. Search for UX designers who are posting about their work, commenting on design discussions, or publishing case studies. Active contributors are usually better hires than passive job-seekers.

Built In works well for tech companies in major metros. The candidate pool tends to be mid-to-senior level and tech-savvy. Authentic Jobs and We Work Remotely pull a design-literate audience that Indeed and ZipRecruiter don’t reach.

Staffing Agencies That Specialize in Creative and Design

Generalist staffing agencies treat UX designers the same way they treat Java developers. They match keywords on a resume to keywords on a job description. The result is candidates who “know Figma” the same way someone who took a weekend course “knows Python.” It’s technically true and practically meaningless.

A creative staffing agency with actual UX placement experience will screen for portfolio depth, research methodology, tool fluency, and the subtle difference between a designer who led the work versus a designer who was the third person on a five-person team presenting the group’s output as their own, which happens more often than you’d expect and is almost impossible to catch from a resume. The fee is worth it when the alternative is spending six weeks screening 150 applications yourself, interviewing 12 people, and making one offer that gets declined because you took too long.

Contract, Direct Hire, or Contract-to-Hire?

UX fit is harder to evaluate in interviews than engineering fit. An engineer’s code either works or it doesn’t. A UX designer’s effectiveness depends on how they navigate your specific stakeholders, your specific users, your specific constraints. You can’t test that in a 45-minute interview.

That’s why contract-to-hire works particularly well for UX roles. A 90-day contract gives you time to see how a designer handles real feedback from real stakeholders on real projects. Do they get defensive when a PM pushes back? Do they over-index on visual polish at the expense of shipping? Do they actually talk to users, or do they design from assumptions and call it “intuition”? Three months answers all of those questions. An interview answers none of them.

Direct hire makes sense when you’ve found a senior designer with a proven track record at companies similar to yours and you’re confident in the role definition. You’ll pay a higher upfront fee, but you’ll also signal commitment that attracts better candidates. Senior UX designers with multiple offers tend to choose stability over contract ambiguity, especially after two years of tech layoffs that made even people with excellent resumes and no employment gaps suddenly nervous about anything that doesn’t come with benefits and a clear path to permanence, which is a shift we didn’t see coming and one that has changed how we pitch contract-to-hire arrangements to senior candidates entirely.

Pure contract works for project-based work. Redesigning an app. Fixing a specific onboarding flow. Building a design system from scratch. Scope it, timebox it, bring in a specialist. No reason to create a full-time headcount for a six-month project.

Red Flags That Save You From a Bad UX Hire

A few of these you’d catch on your own. Most of them you won’t until the person is already on payroll.

Portfolio with zero case studies. Just final screens, no process. This person might be a talented visual designer. They’re not demonstrating UX skill. UX is process, not output. If the portfolio doesn’t show research, iteration, and tradeoffs, you’re guessing.

Concept redesigns only. A portfolio full of “I redesigned Spotify” or “My vision for the Uber app” without any shipped production work means the candidate has never dealt with real constraints. Engineering feasibility, accessibility requirements, a product manager who changes the brief halfway through because the CEO saw a competitor’s feature at a conference and came back with opinions, and a legacy system that hasn’t been updated since 2019 and doesn’t support the interaction pattern the designer wants to use. Concept work is practice. You’re hiring for the game.

Can’t explain a design decision without mentioning aesthetics. “I chose this layout because it looks clean” is a graphic design answer. “I chose this layout because our eye-tracking data showed users scanning in an F-pattern and the primary CTA needed to sit at the first fixation point” is a UX answer. If every justification comes back to visual preference rather than user evidence, the designer is decorating, not designing.

No questions for you during the interview. A UX designer who doesn’t ask questions about the users, the product, the business goals, or the team structure is showing you exactly how they’ll approach the job. They’ll wait to be told what to design rather than proactively identifying what needs to be designed, which means every product decision that should have a design voice will get made without one, and you’ll find out six weeks later when the feature ships and the support tickets start arriving. That passivity is expensive.

Tool obsession. “I only work in Figma” or “I need Sketch, I don’t use Figma” is a flag in 2026. Tools are tools. The underlying skill is spatial reasoning, interaction logic, and user empathy. A designer who can’t adapt to your tool stack is a designer who’s going to create friction with your existing team from day one.

Things People Ask About Hiring UX Designers

So what’s the actual difference between UX and UI design?

Bigger than most job postings suggest. UX is the research, strategy, and structure. UI is the visual execution. A UX designer decides that the checkout flow needs three steps instead of five and maps the information hierarchy. A UI designer decides the button is 48px with 16px border radius and #F48830 for the CTA color. Some people do both. Most are stronger at one. The combined “UX/UI Designer” title works fine for small teams where one person handles everything, but at senior levels the skill sets diverge so sharply that posting a single role expecting both usually means you get someone who’s decent at one and mediocre at the other, and the mediocre half is the one that costs you six months of rework when the product ships and users can’t figure out the navigation you thought was obvious.

Realistically, how long does it take to hire a good one?

30 to 60 days for a mid-level role if your job description is accurate and your compensation is competitive. Longer if either of those is off. We had a client keep a senior UX designer role open for four months because the salary was $95K in a market where the role required $130K. They finally adjusted the budget. Filled the role in three weeks. The timeline problem is almost always a positioning problem. Either the title is wrong, the salary is low, or the job description describes three different roles stapled together.

Do you actually need a dedicated UX designer, or can a developer handle it?

Depends on what “it” is. If your product has fewer than 10 screens and your users are internal employees who’ll use whatever you give them, a developer with decent design taste can probably handle it. Maybe. If your product faces external customers, has complex workflows, or competes in a market where user experience is a differentiator, no. A developer who “does UX on the side” will build functional interfaces that nobody enjoys using. Functional, sure. It’s just the kind of mediocre that slowly bleeds customers to competitors who invested in the experience.

Remote, hybrid, or on-site for UX designers?

48 to 72 hours. That’s how long it takes for a fully remote UX designer to lose context in a fast-moving product sprint if the team’s communication infrastructure isn’t solid. Slack messages don’t replace whiteboard sessions when you’re working through a complex interaction flow. That said, the best UX designers we’ve placed in the past year have been hybrid. Two to three days on-site for collaborative work, research sessions, and stakeholder meetings. Remote the rest of the week for deep design work. Fully on-site five days a week is a hard sell for senior UX talent right now. You’ll narrow your candidate pool significantly.

How do you tell a real UX designer from a bootcamp graduate who padded their portfolio?

Short answer: the portfolio deep-dive questions from the interview section above will surface it fast. The longer answer involves looking for specificity. Bootcamp portfolios follow templates. Three case studies, each with the same structure: empathize, define, ideate, prototype, test. Real-world portfolios are messy. One project might be 80% research with a paragraph about the final design. Another might start with “The PM gave us two weeks and we skipped formal research entirely.” That messiness is the signal. Real work doesn’t follow a five-step framework. If every case study looks like a textbook exercise, it probably was one.

Is the fee from a creative staffing agency actually worth it?

$14,000 to $22,000 for a typical direct hire placement at a $110K salary. That sounds like a lot until you calculate the alternative. A bad hire costs roughly 30% of annual salary in recruiting, onboarding, lost productivity, the three months of design work that has to be redone by the replacement, and the morale hit to the product team that spent a quarter collaborating with someone who’s now gone. That’s $33K. A vacant role costs the salary equivalent in lost output for however long it stays open, which for UX is usually the entire product roadmap slipping because nobody’s doing the design work and the PM is trying to wireframe in PowerPoint. The agency fee is insurance against both of those outcomes. Not every company needs it. But if your internal recruiting team doesn’t have a design portfolio reviewer and can’t tell Figma from Photoshop, the fee pays for itself on the first placement.

Ready to start a UX designer search? Talk to our creative staffing team and we’ll scope the role before sourcing a single candidate.