Product design interview questions worth asking

Why most design questions do not discriminate

“Walk me through your process.” “Tell me about a project you're proud of.” “How do you handle feedback?” Every candidate has an answer ready, and the answer is roughly the same one, because the questions are the same everywhere and the internet has told everyone what to say.

A question discriminates when the answer cannot be prepared in advance — either because it requires specific lived information, or because it puts the candidate in a situation and watches what they do.

Questions about judgment

These four get closest to the thing you are actually hiring for. Ask them about a specific project, not in the abstract.

• “Tell me about a design decision you made that turned out to be wrong. How did you find out?” — Requires having had a belief, shipped it, and received contradicting evidence over time. Cannot be answered from a case study.
• “What did the brief say before you changed it?” — If they never changed a brief, that is the answer. If they did, you learn how they reframe.
• “What did you argue for and lose?” — Reveals whether they have opinions, and how they behave when overruled.
• “What is still broken in that product because of a decision you made?” — Strong candidates answer immediately. It is the single hardest question to fake.

Questions about prioritisation

The fastest way to see seniority is to take resources away and watch what the candidate protects.

• “You have two weeks of one engineer instead of eight. What do you build?” — Juniors cut polish. Seniors cut scope and say what they are sacrificing.
• “What did you deliberately not do on that project, and why?” — Tests whether they think in trade-offs or in features.
• “Which single metric would you move, and by how much?” — One number with a magnitude means outcome thinking. Six metrics means a dashboard.

Questions about working with other people

Ask for the artefact, not the self-description. “How do you handle disagreement” invites a rehearsed answer; “write me the message” does not.

• “An executive insists on a solution the data does not support. Write me the reply you would send.” — Two ways to fail: capitulate, or dig in. One way to do it well: reframe towards their goal and propose a cheap test.
• “Engineering says your approach is impossible this quarter. What now?” — Watches for a second gear rather than negotiation of the deadline.
• “Explain this decision to someone in operations, in four lines, with no design vocabulary.” — Produces a real writing sample under a real constraint.

Questions about self-awareness

Ask last, when they are invested in what they have described. The comfortable version of this question tells you nothing; the specific version tells you a lot.

• “What is the weakest part of what you have just described, and how would you check it?” — Textbook answers (“we'd validate with users”) score low because they are true of everything.
• “What would someone who disagreed with this decision say?” — Strong candidates can argue the other side properly. Weak ones straw-man it.

Four questions to stop asking

Each of these feels probing and measures nothing useful.

• “Walk me through your process.” — Everyone has memorised a double diamond.
• “What's your favourite app and why?” — Measures taste and opinion fluency, not judgment.
• “Where do you see yourself in five years?” — Measures interview preparation.
• “Design a lift for me.” — Measures comfort with performing under artificial pressure, which is not the job unless you are hiring for interviews.

Do not just ask better questions — control the conditions

Even good questions are hard to compare when each candidate answers about a different project, at a different level of detail, with a different interviewer having a different day.

If you can, ask the same questions about the same situation to everyone. That single change does more for your decision quality than any improvement to the questions themselves.

Frequently asked

How many questions should a design interview have?

Fewer than you think. Four or five questions explored properly tell you more than twelve asked shallowly, because the follow-up is where the real information is. Plan for one follow-up per question as a minimum.

Should the hiring manager or a designer ask these?

Ideally a designer, but a non-designer can ask all of the judgment and prioritisation questions and read the answers perfectly well. The ones that genuinely need a designer are about craft, and those are the easiest to verify separately.