Product Designer Interview Questions and Scorecard
Free product designer interview questions for small businesses without HR: 6 question sets, a design exercise brief, and a 1-to-5 scorecard.
The first time I interviewed a product designer I did the thing almost every founder does. I opened the portfolio, scrolled through some beautiful case studies, felt underqualified to have an opinion, and hired on vibes. The work that arrived afterward was pretty and did not move a single number that mattered. The interview had tested presentation, which the candidate had rehearsed, instead of judgment, which I actually needed.
At FirstHR, we build for small businesses hiring without an HR department, where the founder runs the whole process alone. This page is the employer side of the table: six question sets, each question paired with a stated reason it is worth asking and a note on what a good answer sounds like, plus a scorecard so the decision rests on what people said rather than on who presented best.
If you have not written the posting yet, start with the product designer job description templates, then come back here for the interview.
- Sign the offer letter
- Sign the employee handbook
- Workplace Safety course
What a Product Designer Actually Does
A product designer decides what to build and then designs it: framing the user problem, choosing which version is worth the engineering time, producing the interface, and following what happens to the numbers after launch. The title sits across research, interaction design, and visual craft, with a heavy dose of business context that a pure interface role does not carry.
At a small company that scope expands rather than shrinks. There is no product manager writing the brief and no design director reviewing the output, so the designer talks to customers directly, argues scope with engineering, and sets up whatever design practice exists. Before you interview anyone, write down one sentence: will this person receive a brief, or write one? The answer sets the level and changes half the questions you should ask.
Titles in this space are unreliable. A UX designer posting and a product designer posting often describe the same job, and industrial product design is a different profession entirely. Read the scope, not the label, and be specific in your own posting so you attract the right applicants.
The Four Things Worth Assessing
Assess product sense, craft and systems, shipping record, and collaboration. Everything else, including the aesthetic quality of the portfolio, is downstream of those four. A designer who scores well across them will produce work that fits your business; a designer who scores well only on craft will produce work that photographs beautifully and changes nothing.
Weight them by the role. If a founder or product lead will set direction and review the work, craft and collaboration matter most. If this person will be your only designer and has to decide what to work on, product sense and outcome ownership carry the hire, and you should interview and pay at the senior level even if the title says otherwise.
Which Question Set Should You Use?
Pick the sets that match the round you are running and the level you are hiring. Most small businesses need three of the six: product sense in the first conversation, the shipped-work deep dive in the second, and the scorecard throughout. Add the others when the role or the candidate calls for it.
6 Free Product Designer Question Sets to Download
Download all six as separate Word files in one ZIP, or copy individual sets. Each follows the same structure: why the set exists, the questions with a reason for asking and a good-answer note, what to listen for, and space for notes. Fill in the brackets, keep the wording identical across candidates, and score right after each conversation.
Set 1: Product Sense and Problem Framing
The core set for a first or only designer: how they frame problems, prioritize, make trade-offs, and know whether a design worked. Start here in the first conversation.
Set 2: Craft, Design Systems, and Execution
Whether they can actually build the interface: states beyond the happy path, edge cases, accessibility, fidelity, handoff specs, and keeping a product consistent with a component library.
Set 3: Shipped Work Deep Dive
One project, 30 to 40 minutes, candidate driving. What they personally did, what shipped versus what was designed, what got cut, and what the metric did afterward. The highest-yield hour in the process.
Set 4: Engineering and Founder Collaboration
Where most product designer hires actually fail at this size: feasibility conversations, being overruled, presenting to non-designers, and a realistic first-30-days plan.
Set 5: Paid Design Exercise Brief and Grading Sheet
A four-hour, paid, invented brief with the grading criteria attached, for the case where the deep dive left one question unanswered. Same brief, cap, and sheet for every candidate.
Set 6: Scoring Rubric and Red Flags
Six scoring areas, a red-flag checklist, and level calibration from junior to only-designer, so candidates are compared on evidence. Use with every set above.
How to Judge Answers If You Are Not a Designer
Judge the reasoning, not the pixels. You cannot grade a layout, but you can grade whether someone explains what problem they solved, what evidence they had, what they cut, and what happened after launch. Those are business answers, and a vague one is unmistakable once you are listening for specifics.
Three tells separate strong candidates from polished ones. They ask about your customers and your revenue before proposing anything. They can say what they personally made after you ask once. And they know how the live product differs from the file they designed. If you still want a craft opinion, pay a senior designer for one hour to join the final round; it costs less than a mis-hire by two orders of magnitude.
Running the Shipped-Work Deep Dive
Give one project 30 to 40 minutes and let the candidate drive, then interrupt with the questions from Set 3. A case study presentation is rehearsed; the interview is what you find underneath it when you ask about the parts that were not slide-worthy.
| Ask | What a strong answer includes |
|---|---|
| Which artifacts did you personally make? | Precise scope for themselves, generous credit for everyone else |
| What shipped versus what you designed? | Knows the gap in detail and the reason for each compromise |
| What did you cut, and what argument did you lose? | A concrete cut with reasoning, and one loss described without resentment |
| What happened to the metric after launch? | The actual number, including when it disappointed |
| What would you fix first with two more weeks? | Specific and technical, not a general wish for more polish |
Ask to see the messy files: sketches, discarded directions, the version that was rejected. A portfolio of only finished screens is a presentation, not evidence of design work. Candidates who show the middle of the process are usually the ones who have actually shipped through the middle of the process.
Should You Give a Design Exercise?
Only when the interview left a specific question unanswered, and only if you pay for it. A deep dive into work the candidate already shipped tells you more in most cases, because you can probe real constraints and real outcomes rather than a sanitized invented scenario.
| Approach | Shipped-work deep dive | Paid exercise |
|---|---|---|
| Shows real constraints and trade-offs | ||
| Shows what the work achieved after launch | ||
| Works for a candidate with little shippable work | ||
| Isolates problem framing on a level playing field | ||
| Costs the candidate unpaid hours if run badly |
If you run one, follow five rules: cap it at four hours, pay a fair fee on delivery regardless of outcome, invent the problem rather than using live work you would otherwise pay an agency for, send the grading criteria with the brief, and give every candidate the same brief and cap. Unpaid multi-day exercises filter out exactly the experienced designers you want most.
Red Flags in a Product Design Interview
The clearest red flag is a candidate who proposes redesigning your product before asking anything about your customers or your business model. Confidence about your product from someone who has spent four minutes with it is taste being sold as judgment, and it predicts a designer who will argue from preference rather than evidence.
None of these is automatically disqualifying on its own, and nerves produce false positives. Two or more together usually means the person will be expensive to manage on a small team. Weigh defensiveness about feedback heavily, because a company your size gives blunt feedback constantly and there is no manager to buffer it.
Scoring and the Hiring Decision
Score six areas from 1 to 5 immediately after each interview, while the answers are fresh, and anchor every score to something the candidate actually said. Memory reorganizes itself within hours around whoever was most likable, which is precisely the bias a written score defeats.
| Scoring area | What a 5 looks like |
|---|---|
| Product sense | Frames the problem, prioritizes, ties design to an outcome |
| Craft and systems | States, edge cases, accessibility, component thinking |
| Shipping record | Work reached users and they know what happened next |
| Collaboration | Works with engineers and founders, disagrees then commits |
| Customer contact | Seeks evidence without a research team |
| Communication | Explains design decisions clearly to a non-designer |
If more than one person interviews, each scores independently before the group discusses. The same questions and the same rubric for everyone is the core of a structured interview, and the written scores make the feedback step a comparison of evidence rather than a contest of impressions.
The scorecard in Set 6 is designer-specific. If you would rather keep one sheet across every role you hire, a general-purpose interview evaluation form covers the same ground with wider scoring areas.
Fair, Legal, and Structured Interviewing
Asking the same job-related questions of every candidate is simultaneously the fair approach, the legal one, and the one that predicts performance best. Structure is not paperwork at your size; it is what stops a single confident portfolio walkthrough from deciding a hire that will shape your product for years.
Keep every question tied to the work and avoid the small-talk traps: age, family plans, national origin, religion, disability. Several states and cities also restrict asking what a candidate earned previously, so check your local rules before raising salary history. A consistent question set is the cheapest safeguard you have, and it doubles as a way to reduce bias. This is general information, not legal advice.
Accessibility is worth one specific question rather than a general nod, because for a customer-facing product it carries genuine exposure. The Department of Justice publishes guidance on web accessibility under the ADA, and a designer who treats contrast, focus states, and screen reader support as part of the first pass saves you a retrofit later. Applicant tracking is coming soon to FirstHR.
Product Designer Pay
Anchor the range to federal wage data first, then adjust for level and metro. There is no separate federal occupation for product designers, so the closest published category is web and digital interface designers, which mixes web-focused and product-focused roles together.
Two cautions. Because the category blends web design with product design, treat the median as a floor for an experienced product designer at a software company rather than a ceiling. And the spread across metros is wide enough that a national figure is only a starting point, so check local data before you commit to a band and publish the range in the posting.
Many small businesses hire a fractional or contract designer for a quarter first. It is a reasonable way to confirm the need and calibrate the level before committing to a full-time seat, and it gives you a working relationship to evaluate instead of an interview transcript.
Interviewing Without an HR Department
A large company runs this hire through a design director, a recruiter, and a five-stage loop with calibrated scorecards. You are doing it between everything else, probably without a designer on staff to consult. That reality changes what the interview should test and where the avoidable mistakes cluster.
| Signal | Mid-level designer | First or only designer |
|---|---|---|
| Executes well against a clear brief | ||
| Decides what is worth working on | ||
| Talks to customers without being asked | ||
| Sets up the design practice from nothing | ||
| Needs regular direction and review |
The simplest rule: if this person will be your only designer, interview with the product sense and collaboration sets and pay at the senior level, whatever the title says. If a founder or product lead will set direction and review the work, a strong mid-level designer is better value at the same risk. Getting that call wrong is more expensive than any individual question you might forget to ask.
From Interview to Onboarding
The interview is step one. Onboarding a designer has a few specifics: a signed offer stating the level 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 one small real project instead of a redesign.
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 five tools together. Applicant tracking is coming soon to FirstHR.
Frequently Asked Questions
What questions should I ask a product designer in an interview?
Ask questions that test four things: product sense, craft, shipping record, and collaboration. The strongest openers are what problem was this solving and how did you know that was the real problem; what shipped and how did it differ from what you designed; what did you cut and what argument did you lose; what states did you specify beyond the happy path; an engineer says your design takes three weeks instead of three days, what do you do; and how would you spend your first 30 days here. Each of those has a right shape of answer you can recognize without being a designer: specific, evidence-based, and honest about compromises. Avoid asking a candidate to critique your product cold, because it rewards confident opinions over judgment. The six sets on this page group these questions by area and pair each one with what a good answer sounds like.
How do I evaluate a product designer if I am not a designer myself?
Judge the reasoning, not the pixels. You cannot grade a layout, but you can absolutely grade whether someone can explain what problem they were solving, what evidence they had, what they cut and why, and what happened after launch. Those are business answers and a vague one is obvious. Three specific tells separate strong candidates: they ask about your customers and your revenue before proposing anything, they can say what they personally did rather than what the team did, and they know how the live product differs from the file they designed. Ask the same core questions of every candidate and write down a 1-to-5 score immediately afterward, anchored to something the person actually said. If you want a second opinion on craft, pay a senior designer for one hour to sit in on the final round.
What is the difference between a product designer and a UX designer?
A product designer typically owns the whole experience plus the business context: what to build, why it matters commercially, the interface itself, and what happens to the metric after launch. A UX designer focuses on understanding the user problem, mapping flows, structuring information, and testing whether people can complete the task, often with a separate person handling visual and interface craft. In practice the titles overlap heavily and the market uses them interchangeably, so read the actual scope rather than the label. On a small team one person covers all of it, which is why the product designer title is more common at startups. Decide which gap you are filling before you write the posting, because interviewing for the wrong one is the most expensive mistake in this hire. The job description templates on this site cover the digital, UX/UI, industrial, and design-engineering meanings of the role separately.
Should I ask a product designer to do a design test?
Only when the interview left a specific question unanswered, and only if you pay for it. A walkthrough of work the candidate already shipped tells you more than a take-home in most cases, because you can probe the real constraints and the real outcome. Use an exercise when a candidate is strong on craft but you cannot tell how they frame a problem, or when they have very little shippable work to show. If you do run one, keep it under four hours, pay a fair fee on delivery regardless of outcome, use an invented problem rather than live work you would otherwise pay for, send the grading criteria with the brief, and give every candidate the same brief and time cap. Unpaid multi-day exercises filter out the experienced designers you most want. A paid exercise brief and grading sheet is included on this page.
How many interview rounds does a product designer hire need?
Two or three rounds is usually right for a small business. A first conversation of 30 to 45 minutes covers product sense and motivation and confirms basic fit. The second round is the important one: 60 to 90 minutes on a single shipped project, driven by the candidate and interrupted by your questions about what they personally did, what shipped, what got cut, and what the metric did. A third round, if you need one, brings in the engineer who will work with them daily, or runs the paid exercise walkthrough. Resist adding rounds because you feel uncertain, since uncertainty usually means you have not asked the deep-dive questions properly rather than that you need another meeting. Tell candidates the full process up front; strong designers have options and drop out of vague, sprawling loops.
What are the biggest red flags when interviewing a product designer?
The clearest red flag is a candidate who proposes redesigning your product before asking a single question about your customers or your business model, because that is taste being sold as judgment. Close behind: an answer that stays in the plural after you ask twice what they personally made; a portfolio of finished screens with no sketches, no discarded directions, and no explanation of what changed; not knowing whether the work shipped or how it performed; treating accessibility as a late checklist; and describing engineering constraints as obstacles rather than design inputs. Defensiveness about feedback during the interview itself is worth weighing heavily, because a small team gives blunt feedback constantly. None of these is automatically disqualifying on its own, but two or more together usually means the person will be expensive to manage.
How much does a product designer cost to hire?
There is no separate federal wage category for product designers, so the closest benchmark is web and digital interface designers. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), that occupation had a median annual wage of $104,000, about $50.00 an hour, with the lowest 10 percent at or under $53,750 and the highest 10 percent at or above $201,550. Treat the median as a floor rather than a ceiling for an experienced product designer at a software company, because the category mixes web designers with product-focused roles. Adjust for your metro, since the spread across states is wide, and for level, since a first designer who has to decide what to work on is a senior hire regardless of the title. Many small businesses start with a fractional or contract designer for a quarter before committing to a full-time seat.
Are these product designer interview questions legal to ask?
Yes. Every question in these sets is about the work: how the candidate frames problems, what they designed, how they collaborate, and what happened after launch. Job-related questions asked consistently of every candidate are exactly what employment law expects. The general cautions apply as always: do not ask about age, race, religion, national origin, disability, pregnancy or family plans, or genetic information, even as small talk, and do not let a portfolio conversation drift into personal territory. Using the same structured question set and the same scorecard for everyone is itself a safeguard, because it documents that you evaluated candidates on the same job-related criteria. Several states and cities also restrict salary history questions, so check your local rules before asking what someone earned previously. This is general information, not legal advice.
Make HR the easy part of running your business
Onboarding, e-signatures, training and core HR in one place. Up and running in 5 minutes.
- 7-day free trial
- No credit card required
- Cancel anytime