Product Designer interview questions
48 questions asked in Product Designer interviews, on research, design systems, critique and working with engineers. They are built from thousands of real job ads. Under each one: what the interviewer is listening for, and the follow-up they may ask. For the recruiter call, see the HR screen questions.
Behavioral questions
Questions about how you work in this role. More in behavioral questions for any tech role.
-
1
Tell me about a design you cared about that didn't ship. What happened?
All levels
Listening for Accepting a decision without bitterness and learning from it.
Follow-up Ask what they would do differently to give it a better chance.
-
2
Tell me about a time testing with users proved your design idea wrong.
All levels
Listening for Letting evidence beat their own taste and changing the design.
Follow-up Ask what exactly users did that changed their mind.
-
3
Tell me about a time what engineers built didn't match your design. How did you handle it?
Junior, Mid
Listening for Finding out why and fixing it together without blame.
Follow-up Ask what they changed in their hand-off afterwards.
-
4
Tell me about a time you defended a design decision to someone more senior than you.
Mid, Senior
Listening for Arguing from user evidence and goals, not taste, and staying open.
Follow-up Ask how it ended and whether they were right.
-
5
Tell me about a time you and a product manager saw the user's problem differently.
Mid, Senior
Listening for Resolving it with shared evidence rather than opinion.
Follow-up Ask how they work with that PM now.
-
6
Tell me about a time you pushed for accessibility when the team didn't see it as a priority.
Mid, Senior
Listening for Making the case with real users and low-cost fixes.
Follow-up Ask what actually changed in the product.
-
7
Tell me about a time you raised the quality bar for a whole design team, not just your own work.
Senior
Listening for Changing habits, tools or critique across people.
Follow-up Ask how they knew quality really improved.
Technical discussion questions
Talking through your experience and decisions, not a coding test. Grouped by topic.
Interaction design
-
1
Walk me through your design process on a recent project, from the problem to what shipped.
All levels
Listening for Understanding the problem before drawing, and their own decisions at each step.
Follow-up Ask which step they skipped and why.
-
2
An engineer says an animation in your design is too expensive to build. How do you decide what to keep?
All levels
Listening for Knowing what the animation does for the user and finding a cheaper way to get it.
Follow-up Ask what they would give up first.
Design systems
-
3
How do you decide whether to use an existing component from the design system or design something new?
Junior, Mid
Listening for Starting from the system and adding only with a clear user reason.
Follow-up Ask what they do when the new thing is useful for other teams too.
-
4
Let's say we have no design system and five product teams. How would you start one?
Mid, Senior
Listening for Starting small from real repeated patterns, with engineering as a partner.
Follow-up Ask what they would build first and why.
-
5
Teams keep detaching components from the design system. What would you do about it?
Senior
Listening for Finding out why the system does not meet their needs before enforcing rules.
Follow-up Ask how they would measure adoption.
Ux research
-
6
The team wants to ship in two weeks and there's no time for research. How would you still learn from users?
Mid, Senior
Listening for Quick, cheap methods and learning after launch.
Follow-up Ask which risk they would most want to check before shipping.
-
7
User interviews say one thing and product data says another. How do you decide what to believe?
Senior
Listening for Seeing both as partial and digging into why they differ.
Follow-up Ask what they would do to resolve it.
Visual design
-
8
Pick a project you're proud of. What would you change about the design now?
All levels
Listening for Honest critique of their own work with reasons.
Follow-up Ask what stopped them from doing it that way at the time.
-
9
How do you decide what's most important on a screen, and how do you make it stand out?
Junior
Listening for Starting from the user's main task and using size, contrast and space.
Follow-up Ask how they would check users see it first.
Stakeholder management
-
10
Three stakeholders give you three different opinions on a design. How do you decide what to change?
Junior, Mid
Listening for Going back to the goal and user evidence instead of averaging opinions.
Follow-up Ask how they would reply to the ones they did not follow.
-
11
How do you make sure design has a say in what gets built, not just in how it looks?
Senior
Listening for Bringing user insight early into planning and building trust with product and engineering.
Follow-up Ask for a decision they changed this way.
Usability testing
-
12
Walk me through how you'd run a usability test on a new checkout flow.
Junior, Mid
Listening for Realistic tasks, the right users, not leading them, and noting where they struggle.
Follow-up Ask how many people they would test with and why.
Accessibility
-
13
What do you check to make sure a screen works for people with poor eyesight or who use a screen reader?
Junior, Mid
Listening for Contrast, text size, focus order, labels and not relying on colour alone.
Follow-up Ask how they check it before hand-off.
-
14
A stakeholder loves a new colour palette, but it fails contrast checks. How would you handle it?
Mid, Senior
Listening for Keeping the brand feel while meeting accessibility, with real examples.
Follow-up Ask what they would do if the stakeholder still insists.
-
15
How would you make accessibility part of how the whole design team works, not a check at the end?
Senior
Listening for Building it into components, critique and definitions of done.
Follow-up Ask how they would bring engineering along.
Ai products
-
16
Our AI feature is sometimes wrong. How would you design it so users can still trust it?
All levels
Listening for Showing confidence and sources, easy undo and editing, setting expectations.
Follow-up Ask how they would test whether trust is right.
-
17
Let's say an AI writes a first draft for the user. What does the user need to see and be able to do on that screen?
Junior, Mid
Listening for Clear that it is AI, easy to edit, retry and undo.
Follow-up Ask how they would handle a slow or failed response.
-
18
What changes in your design process when a feature gives a different answer every time, like with AI?
Senior
Listening for Prototyping with real model output, designing for ranges of quality and testing with real data.
Follow-up Ask what a static mockup can't show here.
Figma
-
19
How do you hand off a design to engineers so that what ships matches what you designed?
Junior, Mid
Listening for States, edge cases, specs in Figma and staying involved during the build.
Follow-up Ask which detail engineers most often miss.
Mobile design
-
20
How does designing a feature for mobile differ from designing the same feature for the web?
All levels
Listening for Screen size, touch, context of use and platform patterns.
Follow-up Ask for an example where they made the two versions different.
-
21
Walk me through how you'd fit a long form onto a small phone screen.
Junior
Listening for Cutting fields, grouping, steps, the right keyboard and clear errors.
Follow-up Ask which fields they would remove and how they would decide.
Information architecture
-
22
Users say they can't find the settings in our app. How would you work out a better structure?
Junior, Mid
Listening for Methods like card sorting or tree testing and real user words for labels.
Follow-up Ask how they would know the new structure is better.
-
23
Our product grew feature by feature and the navigation is a mess. How would you redesign it without upsetting current users?
Senior
Listening for Research on real use, a staged rollout and measuring impact.
Follow-up Ask how they would get every team to give up space in the menu.
B2b saas
-
24
In a B2B product, the person who buys it and the person who uses it every day are often different. How does that change your design?
Mid, Senior
Listening for Designing for both admin and daily user needs and researching each.
Follow-up Ask how they would reach daily users through the customer.
Mentoring
-
25
A new designer keeps breaking a rule in our design system. How would you help them get it right?
Junior, Mid
Listening for Explaining the reason behind the rule and helping without taking over.
Follow-up Ask how they would know the rule itself needs to change.
-
26
In a design critique, someone says your design is confusing but can't say why. What do you do?
Junior
Listening for Asking open questions to find the real issue and not getting defensive.
Follow-up Ask how they would follow up after the critique.
-
27
How do you give feedback on a junior designer's work so they actually improve?
Mid
Listening for Specific feedback tied to goals, asking questions before giving answers.
Follow-up Ask how they follow up on whether it helped.
-
28
How would you run design critiques so the whole team gets better, not just the one design?
Senior
Listening for A clear format, focus on goals, and safe space for juniors to speak.
Follow-up Ask what they would change if critiques became too polite.
Experimentation
-
29
Product wants to A/B test two versions of your design. How would you make sure the test tells you something useful?
All levels
Listening for Versions that differ in one clear idea, one main metric and enough users.
Follow-up Ask what they would do if both versions perform the same.
-
30
After your design ships, how do you find out if it actually worked?
Junior, Mid
Listening for Agreeing a success measure before launch and looking at data and feedback.
Follow-up Ask what they did the last time a design did not work.
-
31
An A/B test shows the less polished design converts better. What do you do with that?
Senior
Listening for Taking the result seriously, understanding why, and not throwing away long-term quality.
Follow-up Ask what follow-up test they would run.
Data visualization
-
32
How would you design a dashboard for an operations team that looks at it all day?
Junior, Mid
Listening for Learning which decisions they make and showing what needs action first.
Follow-up Ask how they would find out what the team looks at most.
-
33
How would you show a user's spending over six months on a small phone screen?
Junior
Listening for A simple chart that answers the user's real question, readable at small size.
Follow-up Ask what they would show when the user taps it.
-
34
How do you choose the right chart for some data, and how do you make sure it doesn't mislead?
Mid, Senior
Listening for Starting from the question the chart answers, honest scales and clear labels.
Follow-up Ask for a chart they have seen mislead people.
-
35
Our analytics product shows so much data that users feel lost. How would you decide what to show first?
Senior
Listening for Starting from the decisions users make and layering detail behind a clear overview.
Follow-up Ask how they would handle power users who want everything.
Developer tools
-
36
How would you design a settings page for an API product whose users are developers?
All levels
Listening for Knowing developers want speed, clarity and copyable details.
Follow-up Ask what they would put first on the page.
-
37
Developers say they prefer the command line to our web console. How would you find out what the console should be for?
All levels
Listening for Learning which tasks the web does better, like overviews or rare tasks, instead of copying the CLI.
Follow-up Ask who they would talk to.
Fintech
-
38
How would you design a money transfer screen so users feel safe and don't make mistakes?
All levels
Listening for Clear confirmation, readable amounts, preventing errors and showing status.
Follow-up Ask what they would do about a transfer sent by mistake.
-
39
Sign-up for our finance app needs an ID check, and many users drop off there. How would you improve it?
Mid, Senior
Listening for Finding the exact step and reason for drop-off, clear guidance and recovery from failed checks.
Follow-up Ask what they cannot change and why.
Wireframing
-
40
How do you decide whether to show a rough wireframe or a polished prototype?
Junior, Mid
Listening for Matching fidelity to the question being asked and the audience.
Follow-up Ask when a polished prototype got them the wrong feedback.
-
41
When do you skip wireframes and go straight to high fidelity, and when is that a mistake?
Senior
Listening for Using a mature design system as a reason to skip, and new problems as a reason not to.
Follow-up Ask about a time skipping hurt them.