A product designer interview is mostly you explaining your own decisions out loud. The panel already liked your portfolio enough to call, so now they're checking whether the thinking behind it is yours and whether you'd be easy to work with on a hard week. Here's what each round looks for and how to answer the questions that come up again and again.
This is the portfolio question in its purest form. They want to hear how you frame a problem and how much of the work was actually yours.
Every design gets challenged on build cost. They want to know whether you dig in, cave, or find a third option.
Teams rarely have time for a full research phase. They want to see you pick the cheapest way to lower the biggest risk.
This is the classic whiteboard prompt. They're watching how you handle ambiguity, not whether you produce a beautiful answer.
Consistency speeds up the whole team. They want someone who respects shared components but isn't trapped by them.
Accessibility bugs are expensive to fix after launch, and many teams expect designers to catch them early.
They want proof that you look at outcomes and can talk about failure without getting defensive.
Critique is a weekly ritual. They want to know if you'll be pleasant to review and still hold a line when you should.
Messy handoffs cause rework and resentment. This question shows how much you think about the people who build your work.
Designers often get caught between competing asks. They want to see you steer toward a decision instead of pleasing everyone.
They want to know you looked at the product and have a real opinion about it.
Ask at least two. It shows you're picking them too.
