Product design interview questions: why the best answers start with one user

“Design a fridge for people who live alone.” “Design a parking app for a busy city centre.” Product design interview questions all have the same shape: a product, a group of people and almost no other detail. The blank space is the test.

Most candidates fill it with features. Within a minute they're describing a smart screen, a shopping list that syncs to your phone and an alert when the milk goes off. Each idea is reasonable. Together they tell the interviewer almost nothing about how you think.

What the question is really testing

A PM's day job is deciding what not to build. Engineering time is short and every feature has a cost, so the useful skill is picking the problem worth solving before anyone draws a screen. A design question is a compressed version of that decision. The interviewer wants to watch you narrow a vague brief down to one user with one painful problem, then design for them.

Features come last because they're the easiest part. Anyone can brainstorm ten. Fewer people can explain why the third one matters more than the other nine.

The order that works

1. 01Clarify the goal. Is this a new product or an existing one? Is the company after growth, revenue or something else?
2. 02Pick a user segment. List two or three groups inside the brief, then choose one and say why.
3. 03Find their problems. Walk through a day or a task from their point of view and name the moments that hurt.
4. 04Prioritise one problem. Pick the one that is frequent, painful and badly solved today.
5. 05Then design. Two or three solutions, a quick trade-off and a recommendation.
6. 06Say how you'd measure it. One metric that tells you the problem got smaller.

Features don't appear until step five. That's the point.

A short worked example

Take “design a fridge for people who live alone”. Here's how the first couple of minutes might go.

Now walk through their week. They shop in small amounts, often on the way home. They cook a few times a week at most. Food goes off before they finish it because a bag of salad is sized for a family of four. The kitchen is often part of the living room, so noise and size matter.

That gives several problems: wasted food, a fridge too big for the space and a noisy compressor at night. Wasted food is the one to pick. It happens every week, it costs money and nothing in a standard fridge helps with it.

Only now, the features

With one user and one problem the solutions get sharper and fewer.

1. A drawer at eye level marked “eat first”, so opened food doesn't get lost at the back.
2. A door panel showing what went in and when, logged with one tap as you unpack the shopping.
3. Shelves sized for single portions rather than family packs.

Then trade them off. The drawer is cheap and needs no change in behaviour. The door panel is clever but only works if people log their food, which most won't keep doing for long. Recommend the drawer and the shelf layout for launch and test the panel later.

Finish with a measure: the share of owners who say they throw away less food after three months, asked in a short follow-up survey.

Why this lands better than a list of features

Interviewers aren't scoring the fridge. They're asking whether they'd trust you with a real roadmap. Narrowing to one user shows judgement. Naming a problem before a solution shows you won't build things nobody needs. Trading off your own ideas shows you can say no, including to yourself.

It also makes the rest of the interview easier. When the interviewer pushes back you have a reason for every choice. “Why not a touchscreen?” has a clean answer: it doesn't reduce wasted food for someone who lives alone and it adds cost to a mid-range fridge.

Say the narrowing out loud

The narrowing only earns credit if the interviewer hears it. Say which segments you're dropping and why, in a sentence each. It feels slow. It isn't. It's the part of the answer they're listening for. It only becomes natural once you've said it out loud a few times under questioning.