Six question sets for the employer side of the table: product sense, craft and systems, a shipped-work deep dive, collaboration, a paid exercise brief, and a scorecard. Every question states why it is worth asking and what a good answer sounds like. Download as DOCX.
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.
Interview a product designer on four things: product sense (how they frame and prioritize problems), craft and systems (states, edge cases, accessibility, components), shipping record (what reached users and what happened next), and collaboration with engineers and founders. Spend the longest hour on one shipped project. Score six areas 1 to 5 immediately, anchored to evidence. Download six sets and a scorecard as DOCX.
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.
Product sense
Frames the problem before solving it
Cuts scope on purpose, with a reason
Names the metric that would move
Craft and systems
Specifies states beyond the happy path
Builds or maintains a component library
Designs for accessibility in the first pass
Collaboration
Brings engineers in during exploration
Disagrees with evidence, then commits
Explains decisions without craft jargon
Outcome ownership
Knows what actually shipped
Followed the metric after launch
Talks to customers without being asked
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.
Product Sense
Start here
Problem framing, prioritization, trade-offs, and how they know a design worked. The set that predicts whether the hire is useful in month one.
Craft and Systems
Can they build it
Empty and error states, edge cases, accessibility, fidelity, handoff specs, and whether they can keep a product consistent with a component library.
Shipped Work Deep Dive
The most useful hour
One project, 30 to 40 minutes: what they personally did, what shipped versus what was designed, what got cut, and what the metric did afterward.
Engineering and Founders
Where hires fail
Feasibility conversations, being overruled, presenting to non-designers, staying close to customers with no research team, and a first-30-days plan.
Paid Exercise Brief
Only if needed
A four-hour, paid, made-up brief with a grading sheet, for when the deep dive left one question unanswered. Same brief and cap for every candidate.
Scorecard + Red Flags
Decide on evidence
Six scoring areas, a red-flag checklist, and level calibration from junior to only-designer, so you compare what candidates said rather than who charmed you.
Match the Set to the Round
First conversation, 30 to 45 minutes: Product Sense. Second round, the long one: Shipped Work Deep Dive, plus Craft and Systems if no designer is on your panel. Final round with the engineer who will work with them: Engineering and Founders. Only when one question is still open after all that: the Paid Exercise Brief. The Scorecard is used with every round, filled in immediately afterward while the answers are still fresh.
6 Free Product Designer Question Sets to Download
Download all six as a single Word document 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.
Download All 6 Product Designer Question Sets
Product sense, craft and systems, shipped-work deep dive, collaboration, a paid exercise brief, and a scoring rubric. All in one DOCX.
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.
Product Sense and Problem Framing Questions
PRODUCT SENSE AND PROBLEM FRAMING QUESTIONS
Candidate: __
Company: __
Interviewer: __
Date: _
WHY THIS SET
Product sense is the difference between a designer who makes screens and a
designer who decides which screens are worth making. On a small team nobody
hands the designer a fully specified brief, so this is the set that predicts
whether the hire will be useful in month one. Ask 5 or 6 of these. Every
question below states why it is worth asking and what a good answer sounds
like, so you can score it without being a designer yourself.
QUESTIONS
1. Pick something you designed. What problem was it solving, and how did you
know that was the real problem?
Why ask: separates problem framing from screen production.
Good answer: names the evidence (support tickets, drop-off in a funnel,
sales calls, five customer interviews) and admits what was still a guess.
Weak answer: the problem was that the old design looked dated.
2. Tell me about a time the thing you designed was not the thing the business
needed. What happened?
Why ask: tests honesty and whether they connect design to outcomes.
Good answer: a specific miss, what it cost, and the habit they changed.
Weak answer: cannot recall one, or blames stakeholders entirely.
3. Our product is [describe it in one sentence]. Where would you look first for
the biggest design problem, and what would you need from us to find it?
Why ask: shows how they start on unfamiliar ground.
Good answer: asks about your customers and your revenue before proposing
anything, then names cheap sources of truth (analytics, support, sales).
Weak answer: proposes a redesign in the first two minutes.
4. How do you decide what not to build when everything is asked for at once?
Why ask: prioritization is most of the job on a small team.
Good answer: a repeatable way of weighing customer impact against effort,
with a real example of something they argued down or deferred.
5. Walk me through a trade-off you made between what was ideal and what could
actually ship that quarter.
Why ask: perfectionism is expensive when there is one designer.
Good answer: names the constraint, the compromise, and what they protected.
6. How do you know a design worked after it launched?
Why ask: closes the loop between design and business results.
Good answer: a metric chosen before launch, plus qualitative signals, and
an example where the number did not move and they responded.
7. What is a product you admire that most people would call badly designed, and
why does it work?
Why ask: tests judgment beneath taste.
Good answer: explains the user context and the business model, not the UI.
WHAT TO LISTEN FOR
•Questions about your customers and your revenue before any solution
•Evidence, even scrappy evidence, behind past decisions
•Comfort saying what they got wrong
•Outcomes described in business terms, not in adjectives
NOTES
__
__
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.
Craft, Design Systems, and Execution Questions
CRAFT, DESIGN SYSTEMS, AND EXECUTION QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHY THIS SET
Product sense without craft produces good ideas nobody can ship. This set tests
whether the candidate can actually build the interface: states, edge cases,
accessibility, and a component system that keeps the product consistent after
they move on to the next project. Use it alongside the product sense set.
QUESTIONS
1. Take one screen you designed. What states did you specify beyond the happy
path?
Why ask: empty, loading, error, and permission states are where design debt
is created.
Good answer: names them without prompting and explains one edge case they
caught that engineering would otherwise have invented on the spot.
Weak answer: only the ideal screen exists in the file.
2. Have you built or maintained a design system? What was in it, and who used
it besides you?
Why ask: at a small company the system is how one designer scales.
Good answer: describes components, tokens, and naming, plus the discipline
of keeping it current, and is honest if theirs was small.
3. How do you handle accessibility: contrast, keyboard navigation, screen
readers?
Why ask: retrofitting accessibility is expensive and carries real exposure.
Good answer: treats it as part of the first pass, names concrete checks, and
knows the common contrast and focus-state requirements.
Weak answer: treats it as a compliance pass at the end or someone else’s job.
4. At what fidelity do you work, and when do you move up from sketches?
Why ask: reveals whether they explore before polishing.
Good answer: cheap and fast early, high fidelity only once the direction is
settled, with a reason for each jump.
5. How do you write the specification an engineer needs from a design file?
Why ask: handoff quality decides how much rework you pay for.
Good answer: describes what they annotate, how they cover responsive
behavior, and how they stay available during the build.
6. Show me something you designed that you would redo now. What changed?
Why ask: growth and self-criticism are hard to fake.
Good answer: specific, technical, and unbothered by admitting it.
7. How do you keep a product consistent when several people ship into it?
Why ask: consistency erodes fastest on small, fast-moving teams.
Good answer: a shared library plus a light review habit, not a policing role.
WHAT TO LISTEN FOR
•Non-happy-path states named without prompting
•Accessibility treated as part of the first pass
•Real handoff artifacts, not just pretty files
•A system mindset rather than one-off screens
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
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.
Shipped Work Deep-Dive Questions
SHIPPED WORK DEEP-DIVE QUESTIONS
Candidate: __
Project under review: __
Interviewer: __
WHY THIS SET
Pick ONE project the candidate shipped and spend 30 to 40 minutes on it. A case
study is a rehearsed presentation; this set is the interview underneath it. The
goal is to establish three things: what this person personally did, what
actually shipped versus what was designed, and what happened afterward. Ask the
candidate to drive, and interrupt with these.
QUESTIONS
1. Who was on this project, and which artifacts did you personally make?
Why ask: portfolios blur individual and team contribution.
Good answer: names collaborators generously and is still precise about their
own scope. Ask twice if the answer stays in the plural.
2. What shipped, and how did it differ from what you designed?
Why ask: the gap between file and product is where the real story lives.
Good answer: knows the gap in detail and why each compromise was made.
Weak answer: has never checked what the live product looks like.
3. What did you cut, and what argument did you lose?
Why ask: reveals negotiation, priorities, and ego.
Good answer: a concrete cut with the reasoning, and one loss described
without resentment.
4. How long did it take from first sketch to launch, and what slowed it down?
Why ask: calibrates speed against your delivery pace.
Good answer: a real timeline with an honest bottleneck.
5. What did you learn from users before you designed, and what surprised you?
Why ask: tests whether research informed the work or decorated it.
Good answer: a specific surprise that changed the design.
6. What happened to the metric after launch, and what did you do about it?
Why ask: closes the loop; strong designers follow their work.
Good answer: knows the number, including when it was disappointing.
7. If you had another two weeks, what would you have fixed first?
Why ask: shows current judgment about their own past work.
8. What would you have needed from a founder to make this go better?
Why ask: tells you how to manage this person if you hire them.
WHAT TO LISTEN FOR
•A clear line between their work and the team’s
•Knowledge of what actually shipped and how it performed
•Discarded directions and cuts, not just the finished screens
•Curiosity about the outcome months later
NOTES
__
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.
Engineering and Founder Collaboration Questions
ENGINEERING AND FOUNDER COLLABORATION QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHY THIS SET
At a small company the designer sits between the founder, the engineers, and
the customer, usually with no design manager in between. Most product designer
hires that fail at this size fail here, not on craft. This set tests how the
candidate works when nobody is coordinating for them.
QUESTIONS
1. How do you work with engineers before a design is final?
Why ask: early feasibility conversations prevent expensive rework.
Good answer: brings engineers in during exploration, asks about cost, and
changes the design when the answer is expensive.
2. An engineer says your design will take three weeks instead of three days.
What do you do?
Why ask: this happens constantly at small companies.
Good answer: asks what is driving the cost, offers a cheaper version that
keeps the important part, and does not escalate first.
3. The founder overrules your recommendation. Walk me through the next hour.
Why ask: you are the founder; this will happen.
Good answer: states the evidence once, proposes a cheap test if the stakes
justify one, then commits fully to the decision.
4. How do you present work to someone who is not a designer?
Why ask: you have to understand the pitch to fund the work.
Good answer: leads with the problem and the outcome, keeps craft language
out of it, and asks for specific decisions rather than general reactions.
5. Tell me about the harshest feedback you received on a design. What did you
do with it?
Why ask: fragile designers are expensive on a small team.
Good answer: describes the feedback plainly and what changed as a result.
6. How do you stay close to customers when there is no research team?
Why ask: on a small team the designer is the research team.
Good answer: sits in on sales and support, reads tickets, runs short calls.
7. How would you spend your first 30 days here?
Why ask: the single most informative question in the interview.
Good answer: learn the product, meet customers, fix something small and real,
and defer the big redesign opinions until they have evidence.
WHAT TO LISTEN FOR
•Engineering treated as a partner, not a constraint to route around
•Disagreement handled with evidence, then commitment
•Plain language when explaining design decisions
•A first-30-days plan built on learning, not on redesigning
NOTES
__
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.
Paid Design Exercise Brief and Grading Sheet
PAID DESIGN EXERCISE BRIEF AND GRADING SHEET
Candidate: __
Company: __
Date sent: _ Due: _
Agreed fee: $___ Time cap: ______ hours
HOW TO USE THIS
Use an exercise only when the shipped-work deep dive left a real question
unanswered, for example when a candidate is strong on craft but you cannot tell
how they frame a problem. Keep it under four hours, pay for the time, use a
made-up problem rather than live work you would otherwise pay an agency for, and
tell the candidate exactly how it will be judged. Send the grading sheet with
the brief.
THE BRIEF (EDIT THE BRACKETS)
Context: [One paragraph about the business and the customer.]
The problem: [One paragraph. Give a real user problem, not a feature request.]
What we know: [Two or three facts: a metric, a support theme, a constraint.]
What to deliver:
•A short written statement of the problem as you understand it
•One or two flows or screens at whatever fidelity you choose
•The open questions you would want answered before building
•What you would measure after launch
Time cap: 4 hours. Do not polish beyond that; we grade the thinking.
Fee: paid on delivery regardless of outcome.
Walkthrough: 30 minutes, scheduled for [date]. You present, we ask questions.
GRADING SHEET
Problem framing: restated the problem in their own words, correctly
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Judgment: solved the important part, ignored the rest on purpose
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Craft: states, edge cases, hierarchy, accessibility considered
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Open questions: asked the things a good designer would ask
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Communication: the walkthrough was clear to a non-designer
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Total: ______ / 25
RULES FOR YOURSELF
[ ] Same brief, same time cap, same grading sheet for every candidate
[ ] Paid, every time, before the walkthrough
[ ] No live company work used as the exercise
[ ] Result scored before the group discusses it
NOTES
__
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.
Product Designer Scoring Rubric and Red Flags
PRODUCT DESIGNER SCORING RUBRIC AND RED-FLAG CHECKLIST
Candidate: __
Role level: [ ] Junior [ ] Mid [ ] Senior [ ] Only designer
Interviewer: __
Date: _
HOW TO SCORE
Score each area 1 to 5 immediately after the interview, while the answers are
fresh, and anchor every score to something the candidate actually said. If more
than one person interviews, each scores independently before the group talks, so
one confident voice does not set the tone. Use the same six areas for every
candidate at this level.
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
SCORING AREAS
Product sense: frames the problem, prioritizes, ties design to outcomes
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Craft and systems: states, edge cases, accessibility, component thinking
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Shipping record: work reached real users and they know what happened next
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Collaboration: works with engineers and founders, handles disagreement
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Customer contact: seeks evidence without a research team
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
Communication: explains design decisions to a non-designer
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ] Evidence: ___
RED FLAGS (WEIGH CAREFULLY)
[ ] Proposes a redesign of your product before asking about your customers
[ ] Cannot say what they personally did after being asked twice
[ ] Portfolio has only finished screens, no discarded directions
[ ] Does not know whether the work shipped or how it performed
[ ] Treats accessibility as a late checklist
[ ] Describes engineering constraints as obstacles rather than inputs
[ ] Defensive about feedback in the interview itself
LEVEL CALIBRATION
Junior: executes well against a clear brief; needs regular direction
Mid: owns a feature end to end; asks for the brief when it is missing
Senior / only designer: decides what to work on; sets up the design practice
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.
How did you know that was the real problem?
Why ask it: It separates a designer who frames problems from one who executes briefs. On a team with no product manager, framing is most of the value you are buying.
Strong answer: Names the evidence they had, however scrappy: a drop-off point in the funnel, a theme in support tickets, five customer calls. Says plainly which part was still a guess and how they would have tested it with more time.
Weak answer: The problem was that the old design looked dated, or the CEO asked for it. No evidence, no distinction between a symptom and a cause.
What states did you specify beyond the happy path?
Why ask it: Empty, loading, error, and permission states are where design debt gets created. Whoever does not design them leaves an engineer to invent them at 6pm on a Friday.
Strong answer: Lists them without being prompted and gives an example of an edge case they caught, such as what the first screen looks like for an account with no data yet, or what happens when a payment fails mid-flow.
Weak answer: Only the ideal screen exists in the file, and the answer treats states as an engineering concern rather than a design one.
An engineer says your design takes three weeks instead of three days. What do you do?
Why ask it: This exact conversation happens every sprint at a small company, and how the candidate handles it determines how much rework you pay for over a year.
Strong answer: Asks what is driving the cost, then proposes a cheaper version that keeps the part that mattered. Treats the constraint as information about the design rather than an obstacle to route around.
Weak answer: Escalates to the founder first, or accepts the estimate silently and quietly resents the compromise for the next six months.
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.
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
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.
Redesign before questions
A candidate who proposes rebuilding your product before asking anything about your customers or your revenue is selling taste, not judgment.
The permanent we
Team credit is healthy until you ask twice and still cannot tell what this person made. Ask which specific artifacts were theirs and who made the rest.
No idea what shipped
A designer who never checked how the live product differs from their file, or what the metric did after launch, has not been accountable for outcomes.
Accessibility last
Treating contrast, focus states, and screen readers as a late checklist creates rework and, for a customer-facing product, real legal exposure.
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
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.
Structure Beats Impression, and It Is Also the Safer Ground
Federal guidance describes the structured interview as a standardized process in which every candidate answers the same job-related questions rated against the same predefined criteria, which improves both reliability and legal defensibility. Consistency also keeps you inside the EEOC rules against decisions based on protected characteristics.
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.
Median $104,000 a Year (BLS OEWS, May 2025)
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), web and digital interface designers, the nearest category covering product designers, had a median annual wage of $104,000, or $50.00 an hour, with the lowest 10 percent at or under $53,750 and the highest 10 percent at or above $201,550 (U.S. Bureau of Labor Statistics).
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.
You are hiring a designer without being one
Most owners making this hire cannot grade a design file, and the portfolio is engineered to be persuasive to exactly that person. The fix is not to learn design in a week. It is to ask questions whose answers you can judge on your own ground: what problem was this solving, how did you know, what did you cut, what did the number do afterward. Those are business answers, and you can tell a specific one from a vague one. That is why every question in these sets carries a stated reason for asking it and a note on what a good answer sounds like.
Your first designer is a senior hire wearing a junior title
At a company with a design team, a product designer receives a brief. At yours, there is no brief and no one to write it, so the person has to decide what to work on, talk to customers directly, and set up the design practice from nothing. That is senior work regardless of what the job title says. Interview for judgment and self-direction first, and be honest in the posting about the level, because a strong mid-level designer hired into an unsupported seat usually stalls within a quarter. Applicant tracking is coming soon to FirstHR.
One interview, no panel, no recruiter to keep it consistent
A larger company runs a five-stage loop with a design director calibrating the scores. You have one or two conversations, fitted between everything else. Consistency is the substitute for scale: the same core questions for every candidate, the same scorecard filled in immediately afterward, and independent scores before anyone discusses. Structured interviewing is not bureaucracy at your size, it is the only thing standing between you and hiring whoever presented most confidently on the day.
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. The usual new-hire paperwork runs alongside it.
Offer, NDA, and IP assignment
Confirm level, pay, and scope in writing, and get confidentiality and IP assignment signed, since a designer produces work product the company needs to own outright.
Tools and access on day one
Design tool seat, the component library, the repository or handoff space, analytics, and the support inbox, all provisioned before the first morning.
One small, real, shippable project
Give week one a genuine problem small enough to ship, not a redesign. It teaches the product, earns credibility with engineering, and produces evidence fast.
Paperwork stored in one place
Signed offer, agreements, I-9, W-4, and policy acknowledgments organized where you can find them a year later without a search party.
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.
Key Takeaways
Assess a product designer on product sense, craft and systems, shipping record, and collaboration, not on how the portfolio looks.
Every question should carry a stated reason for asking it and a note on what a good answer sounds like, so a non-designer can score it.
Give one shipped project 30 to 40 minutes and push past the polish: what they personally did, what shipped, what got cut, what the metric did.
Decide first whether this person receives a brief or writes one, because a first or only designer is a senior hire regardless of the title.
Run a design exercise only when a question is still open, cap it at four hours, and pay for it every time.
Score six areas from 1 to 5 immediately after each interview, anchored to evidence, and score independently before the group discusses.
Use federal data as your pay baseline: the nearest occupation reported a median of $104,000 a year in May 2025.
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.
