UX Designer Interview Questions and Scorecard

The first UX designer I ever interviewed showed me a portfolio so beautiful that I stopped asking questions after ten minutes. I hired on the strength of the artwork. Three months later I understood the mistake: the screens were lovely and the product was no easier to use, because nobody in that interview had asked why any of those decisions were made.

That is the trap in hiring a designer when you are not one. Portfolios are built to impress, and a good presenter can carry an hour on visual polish alone. The questions in this kit are built to get underneath that, so an owner or hiring manager can hear the difference between someone who makes screens and someone who solves problems.

At FirstHR, we build for the people who run these interviews themselves. Below are six question sets covering core questions, the portfolio walkthrough, research methods, collaboration, seniority and situational judgment, and a scoring rubric. If you have not written the posting yet, start with the UX designer job description templates and come back here.

What a UX Designer Actually Does

A UX designer is responsible for whether people can accomplish what they came to do in your product. That means understanding the user problem, mapping the flow from first click to finished task, structuring the information, prototyping the interaction, and testing it with real people before it gets built. The output is a working experience, not a picture of one.

On a small team the job is broader than the title suggests. Your designer will likely also draw the interface, write the microcopy, talk to customers, and argue with an engineer about what is feasible this sprint. Federal agencies describe the same discipline in their own user experience guidance: a user-centered approach built on research, testing, and iteration rather than on opinion.

That breadth matters for the interview. You are not hiring a specialist who will be handed clean requirements. You are hiring someone who will decide what to work on, find out what users need, design it, and hand it to engineering in a form that can be built.

It also helps to know what the job produces, because those artifacts are what you will ask about. Expect user flows, wireframes, clickable prototypes, a small component library, findings from usability sessions, and specifications an engineer can build from. If a candidate cannot show or describe most of those, you are probably looking at a visual designer rather than a UX designer.

Telling UX, UI, and Product Design Apart

UX is the experience and the reasoning behind it, UI is the visual and interactive surface, and product design usually covers both plus business context. Mixing these up is the most expensive mistake in the whole process, because you end up interviewing for one skill and hiring for another. Decide which gap you have before you write a single question.

A quick diagnostic: if your product looks acceptable but customers get stuck or churn during a workflow, the gap is UX. If flows work but the interface looks amateurish next to competitors, the gap is UI. Most small businesses need one hybrid person, which is why the combined UI/UX role is so common at this size.

Say the split out loud in the interview and ask the candidate which one they are genuinely stronger in. Honest designers answer immediately. If you eventually need depth in one direction, a product designer or a dedicated UX researcher becomes the next hire.

Which Question Set Should You Use?

Pick the sets that match the role and the round. Most small businesses use the core set in the first interview, the portfolio set in the second, and collaboration plus situational questions in the third, scoring after each round. Use the same combination for every candidate for the same job.

Three rounds are enough for almost any small business: a short screen for level, scope, and pay expectations, then the portfolio walkthrough, then a working session with whoever the designer will sit beside. Add general behavioral questions only where they earn their place, since the design-specific sets already cover most of the same ground.

6 Free UX Designer Question Sets to Download

Download all six as a single Word document or copy individual sets. Each one follows the same structure: when to use it, the questions with notes on what a good answer sounds like, a what-to-listen-for block, and a quick score at the end. Fill in the candidate details and use them as they are. Applicant tracking is coming soon to FirstHR.

Set 1: Core UX Designer Questions

The main set for a first or only design hire: process, prioritization, disagreement with engineering, accessibility, tools, and how they measure whether a design worked. Every question carries a good-answer note. Start here.

Set 2: Portfolio and Case Study Walkthrough

Questions that push past a rehearsed case study: what the real problem was, which parts the candidate personally did, what constraints shaped it, what failed, what got cut, and what the metric did afterward.

Set 3: UX Research Methods Questions

For a designer who will own research too: usability testing, non-leading questions, sample size judgment, when a survey is the wrong tool, and what they would do in one week with no budget at all.

Set 4: Collaboration and Stakeholder Questions

The usual failure point on a small team: handoff to engineering, taking blunt feedback, disagreeing with a founder who owns the vision, and keeping sales and support informed about what is changing.

Set 5: Seniority and Situational Judgment

Separate question banks for junior, mid, and senior candidates, plus three situational scenarios every finalist answers, so you can compare judgment under pressure and set the right level and pay range.

Set 6: Scoring Rubric and Red Flags

A designer-specific scorecard across six areas, a red-flag checklist, and a decision block, so you compare candidates on recorded evidence instead of on whichever conversation felt best. Use it with any set above.

The Portfolio Walkthrough Is the Real Interview

Give the portfolio walkthrough more time than any other round, and structure it: one project, 20 to 30 minutes of presentation, then 25 minutes of your questions. Tell the candidate in advance that visual polish matters less than the decisions behind it. That single instruction changes what they prepare and what you learn.

The point of the follow-up questions is to find out whether the story survives pressure. Anyone can narrate a finished case study. Far fewer can explain the constraint that forced a compromise, the direction they abandoned, or the number that did not move. Three questions do most of the work.

One warning about confidentiality: many designers cannot show client work publicly, so expect some candidates to present under a verbal agreement or with details blurred. That is normal and not a red flag. What matters is whether they can still explain the problem, the constraints, and their own contribution without the pretty pictures to lean on.

Do not ask for unpaid spec work on your live product. Strong designers have options and will decline, and the ones who accept are often the ones with the least leverage. If you want to see them work, run a short paid exercise or a live 45-minute session on a realistic problem, and give every finalist the same one.

How to Judge Design Skill If You Are Not a Designer

You do not need to grade the visuals; you need to hear whether the reasoning holds up. Every strong designer can answer the question behind the question: why this and not that. Weak candidates answer with preference, trend, or what a competitor does. That difference is audible to any business owner, no design training required.

Four signals carry most of the evaluation. Look for judgment you can hear, craft you can see across full flows rather than hero screens, accessibility treated as a habit, and communication that stays steady when you push back.

Accessibility deserves a direct question, because it is both a quality signal and a real exposure. The Department of Justice has published guidance on web accessibility under the ADA, and a designer who treats contrast, labels, and keyboard access as a late-stage checklist will cost you rework later. Ask how they build for assistive technology and listen for habit rather than vocabulary.

Research Methods Worth Testing

At your size the research question is not whether the candidate knows the academic method, it is whether they can learn something true about your customers in a week for almost nothing. Ask them to plan it out loud. The answer tells you more than any credential on a resume.

Ask one follow-up on every method answer: what would you have done differently with more time, and what would you have skipped with less. Designers who have actually run research at a small company answer that instantly, because they have made the trade-off. Designers who have only read about it tend to describe an ideal study that no small business could afford to run.

A strong candidate reaches for the cheapest method that answers the question and knows the limits of each. Watch for the answer to the conflict scenario: support says one thing and analytics say another. Designers who investigate rather than pick the source that agrees with them are the ones worth hiring.

Red Flags in a UX Interview

Most bad design hires show warning signs in the interview that were visible and got explained away. The four below are the ones I see most often at small companies, and each has a matching question in the sets above so you can test for it rather than hope it does not apply.

Two more are worth naming. A candidate who cannot describe a single failure in their entire career is either inexperienced or not being straight with you, and one whose work samples do not match the sophistication of their conversation may be presenting team work as their own. Both are reasons to check references carefully before an offer.

Scoring and the Hiring Decision

Score every candidate on the same rubric immediately after the interview, while the answers are fresh, and write down the evidence behind each number. Comparing scores anchored to real quotes is a completely different exercise from comparing impressions a week later, and it is the core of a structured interview.

Keep the questions job-related and consistent across candidates. That is both better hiring and a sensible safeguard; the EEOC lists the practices to avoid in interviews. Use a shared interview evaluation form so every interviewer scores independently before comparing, and record the reasoning in your interview feedback step.

UX Designer Pay

Anchor the range to federal wage data first, then adjust for level, location, and how much of the product experience the person will own. Publish the range in the posting, since several states now require it and a stated range attracts better candidates.

Two cautions on that number. It covers a broad occupation that mixes web designers with product-focused UX designers, so treat it as a floor for a senior hire rather than a ceiling. And the range across states and metros is wide, so check the local figures for your area before you commit to a band.

Junior designers sit near the bottom of that spread and senior product-minded designers well above the median, especially in large metros. Many small businesses start with a part-time contractor or a fractional designer for a quarter before committing to a full-time hire, which is a reasonable way to confirm the need and calibrate the level you actually require.

Hiring a UX Designer as a Small Business

A large company hires designers through a design director, a recruiter, and a five-stage loop. You are doing it yourself, between everything else, probably without a designer on staff to consult. That reality shapes what the interview should test and where the avoidable mistakes happen.

The simplest rule: if this person will be your only designer and has to decide what to work on, interview with the senior set and pay for that level. If a founder or product lead will set direction and review the work, a strong mid-level designer is the better value at the same risk.

From Interview to Onboarding

The interview is step one. Onboarding a designer has a few specifics: a signed offer with the level and range you scored them against, confidentiality and IP assignment agreements so the company owns the work product, tool and repository access ready on day one, and a small real project rather than a redesign. Standard new-hire paperwork runs alongside it.

Once the decision is made, an onboarding template gives the new designer a structured first two weeks, and the confidentiality agreement gets signed before any access is granted. FirstHR connects the offer, e-signature, document management, and the first-week task workflow in one place, so a small business can onboard a designer without stitching together five tools. Applicant tracking is coming soon to FirstHR.

Frequently Asked Questions