picked.
Log inPost a role
picked.ai/hire/product-designer/interview-questions
30 product designer
interview questions that actually work.
Pulled from the Neuroworx item bank: nine years of calibration against twelve-month performance outcomes on 14,083 product designers. Sorted by stage (screen, assessment, on-site) and level (IC1 to IC5). Each question comes with what to listen for, what to ignore, and the failure mode it is designed to catch.
30
questions
4
stages
5
levels
14k
hires of validity data
Screen ↓Role-fit ↓On-site ↓Anti-pattern questions ↓
Stage 01 · Screen
Twelve minutes. Ten questions.
The screening conversation. Picked runs this with an AI voice; this is what a human screen would look like with the same rubric. Time-box hard. 60 seconds per answer.
10 questions
01
Tell me about a component you killed from your own design system. Why?
system thinkingspecificity
Listen for
A specific component, a specific reason (overlap, fragility, the third use never landed), the conversation with engineering.
Ignore
"We never killed a component." Worrying.
catches · Designers who only add to the system.
02
Walk me through the most recent screen you designed. What was the second version, and why is it not what we shipped?
visual judgement
Listen for
Two versions side by side in their head. A specific reason the first one lost.
Ignore
A pitch for the final design without the alternative.
catches · Designers who never iterate past the first composition.
03
Tell me about a research session that overrode your personal taste.
research that overrode personal taste
Listen for
A specific session, the moment they saw the user struggle, the change they made even though they hated it.
Ignore
"Research always confirms my taste." A lie or a worse problem.
catches · Designers who treat research as decoration.
04
Walk me through the last critique you received that landed hard. What did you change?
critique-readiness
Listen for
A specific note. The change they made by the end of the week. An honest read on what they still resist.
Ignore
"I love all critique."
catches · Designers who bring polished work to critique to avoid feedback.
05
Tell me about a time an engineer pushed back on your design. Who was right?
navigating engineering pushback
Listen for
A specific push-back, the substance of the trade, an honest read on who was right in retrospect.
Ignore
"We always agree." Suspicious.
catches · Designers who flatten engineering pushback to "engineering is slow".
06
Show me a screen you would now redesign. What is wrong with it?
self-awarenessvisual judgement
Listen for
A specific screen, three specific issues, what they would do differently.
Ignore
"They are all fine."
catches · Designers who do not revisit their own shipped work.
07
Walk me through your design system. What is the part of it you are not proud of?
system thinkingcandour
Listen for
A named area (a token, a component, a doc gap), an honest reason, a plan.
Ignore
"It is all consistent." A polite fiction.
catches · Designers who treat their system as untouchable.
08
Tell me about the last time you watched a real user use your product. What surprised you?
research instinct
Listen for
A specific session in the last six weeks. A specific surprise. A specific change.
Ignore
"I watch users all the time." Vague.
catches · Designers who design for personas, not people.
09
Tell me about a flow where you had to choose between consistency with the system and the right thing for the screen.
system vs single-screen tension
Listen for
A specific flow, the choice they made, what they did to the system afterwards (or did not).
Ignore
"Consistency is always right."
catches · Designers who cannot hold the tension between the system and the screen.
10
Why are you leaving your current role?
stage fit
Listen for
A reason about the shape of the next role. A specific thing they want to design that the current role will not let them.
Ignore
Pure complaint about the current manager.
catches · Designers running from, not to.
Stage 02 · Role-fit assessment
A scoped task. A scored rubric.
One realistic task. We score the writeup, not the polish. The candidate has the take-home equivalent of 60 minutes.
8 questions
01
Here is a one-paragraph problem statement and a screenshot of our current onboarding. Sketch the change you would ship first. Walk me through the second version you considered.
visual judgementIC2+
Listen for
A first cut that is shippable. A clear second version with a clear reason it lost.
Ignore
A pixel-perfect mockup that took the whole hour.
catches · Designers who cannot bound a sketch.
02
Read this design system doc. Identify the three components you would consolidate or kill, with one-sentence reasons.
system thinkingIC3+
Listen for
Three named components, three reasons that pay attention to the second and third uses, an honest read on the cost of removal.
Ignore
A pitch for adding a new component instead.
catches · Designers who can only add.
03
Pick a screen from our product. Critique it in five bullets. Then write the one-sentence brief for the redesign.
critique-readinessIC2+
Listen for
Five bullets that name specific issues. A one-sentence brief that fits on a single line.
Ignore
Five bullets of praise.
catches · Designers who cannot critique a real screen.
04
Here is a flow that is converting at half the rate of the rest of the product. Write the three changes you would test, in order.
research instinctIC2+
Listen for
Three changes, an order with a reason (cheapest first, biggest lever first), a way to read the result.
Ignore
A redesign of the whole flow.
catches · Designers who reach for a rebuild before a tweak.
05
Read this engineering PR for one of your components. Write the three things you would push back on and the one thing you would accept.
engineering literacyIC3+
Listen for
Three specific push-backs that engage with the code. One accept that costs them something.
Ignore
Five push-backs that ignore the trade engineering is making.
catches · Designers who do not read code.
06
Plan a 45-minute user research session for a feature we are about to ship. State the question you are answering, the participants, and the kill criteria.
research instinctIC2+
Listen for
A sharp question. A real participant profile. Kill criteria that could fire before launch.
Ignore
A research plan that runs for three weeks.
catches · Designers who treat research as discovery theatre.
07
Write the message you would send to the PM the day you realise the spec is wrong.
the trade with the PMIC2+
Listen for
A short, direct message. Owns the realisation. Names the next step.
Ignore
A message that buries the lede.
catches · Designers who let a wrong spec ship.
08
Here is a screen we shipped last week. Write the one-paragraph retrospective for the design critique on Friday.
critique-readinessIC3+
Listen for
A paragraph that names what worked, what did not, and what the team should change next time. No defensiveness.
Ignore
A defence of the design that ignores the result.
catches · Designers who cannot retrospective their own shipped work.
Stage 03 · On-site (after Picked)
Twelve questions you will still want to ask in person.
Picked screens, scores, and shortlists. These are the questions worth asking with a human in the room: the calibration questions, the dealbreakers, the chemistry probes.
12 questions
01
Where, in design craft, do you want to grow most this year?
growthmanager fit
Listen for
A specific gap. A specific plan. A name of someone they would learn from.
Ignore
"I want broader scope." Outcome, not skill.
catches · Designers without a learning agenda.
02
Tell me about a time you disagreed with the head of design on a direction call.
authority
Listen for
A real disagreement. The mechanics. What they did about it after.
Ignore
"I trust the head of design." A lie or a worse problem.
catches · Designers who cannot hold a position in front of authority.
03
What is the most uncomfortable feedback you have received from an engineer about how you hand off?
self-awareness
Listen for
A specific piece of feedback. The change they made. The thing they still get wrong.
Ignore
"Engineers love working with me."
catches · Designers who do not invite criticism from the team they design for.
04
Walk me through a design project you wish had failed faster.
judgement
Listen for
A specific moment they could have called it. What stopped them. What they would now do differently.
Ignore
A pitch for the project being secretly worth doing.
catches · Sunk-cost designers.
05
Pick two designers you admire. What do they do that you do not?
taste
Listen for
Concrete habits. Habits adopted. Habits not yet.
Ignore
Pure praise.
catches · Designers without taste for other designers.
06
Tell me the last essay or talk about design that changed how you work.
curiosity
Listen for
A specific essay or talk. The change they made the week after.
Ignore
A book they have always meant to read.
catches · Designers who do not study the craft.
07
When are you most productive?
operating model
Listen for
A specific time of day, a specific environment. A self-aware answer about energy.
Ignore
"I am always on."
catches · Designers without self-instrumentation.
08
Where would you rather be in three years? Title or shape of role.
career
Listen for
A direction (deeper IC vs design management vs founder) and a reason. Honesty about uncertainty.
Ignore
"Wherever the company needs me." Suspicious.
catches · Drifting designers.
09
If you join, what would you want to spend your first week doing?
agencyonboarding
Listen for
A specific plan. Often: sit on three customer sessions, read every recent critique deck, ship a one-screen tweak.
Ignore
"Whatever you suggest."
catches · Designers without an onboarding instinct.
10
What is the thing that would make you leave us within six months?
dealbreaker
Listen for
A specific irritant. A specific manager pattern. A specific operating condition.
Ignore
"As long as the work is interesting."
catches · Hidden dealbreakers, surfaced post-offer.
11
What would you want to ask our most cynical engineer?
probingcuriosity
Listen for
A real question about a quiet tension. "Which of my components do you most resent?"
Ignore
A softball.
catches · Designers who do not want to know what is wrong.
12
Tell me the part of the product you would not want to design. Why?
scopecandour
Listen for
A specific area. An honest reason. A boundary they have learned to draw.
Ignore
"I am happy to design anything." Worrying.
catches · Designers who do not know their own constraints.
The anti-pattern set
Eight questions that look smart
but tell you nothing.
"What is your biggest weakness?"
You will get a strength-shaped weakness. We have asked this 47,000 times. It catches no-one. Replace with: "What is the most uncomfortable feedback you have received?".
"Where do you see yourself in five years?"
Either a rehearsed answer or a stalled one. Both useless. Replace with: "Where would you want to be in three years?"
"Tell me about yourself."
Wastes the first three minutes on the CV they already gave you. Replace with: "Walk me through the most recent thing you shipped end-to-end."
"Why this company?"
Generates polished mission-talk. Replace with: "What about this role made you apply that would not have made you apply elsewhere?"
"Are you a team player?"
No-one says no. Replace with: "Tell me about a time a teammate disagreed with you and how you handled it."
"How do you handle stress?"
No-one says badly. Replace with: "Tell me about your last production incident and your precise role."
"How would you reverse a linked list?"
Probes nothing we care about. We removed it from the bank in 2019. Replace with: "Refactor this 200-line file and tell me what you changed and why."
"If you were an animal, which animal would you be?"
You know what we are going to say. Replace with: anything else.
Or, let us ask
We will ask these for you.
By Friday.
Picked runs the screen, the assessment, and the first-round interview against this exact item bank. You meet the three finalists in person, with these on-site questions in hand.
$0.99 per AI-vetted candidate. First 50 free.
Companion pages
picked.
The AI-native replacement for inbound hiring. For the hiring manager, not HR.
© 2026 Picked · Made in London · Three finalists in forty-eight hours.
Product designer interview questions · Picked.ai