Product sense interview questions
Product sense questions ask you to design or improve a product for a real group of users. The interviewer is scoring the choices you make along the way: which user, which pain, which idea, and why.
Below: what the round tests, the method in short, and 45 practice questions, each with a first move and the outline of a strong answer. All free, no sign-up.
What the interviewer is scoring
- Whether you choose a user and a pain before you name a single feature.
- Whether your options are really different from each other, not three sizes of one idea.
- Whether you commit to one, say what you give up and say how you would measure it.
Watch a mock interview from this round
Grace’s first try, Ava’s pushback, then the stronger answer with its scorecard. The question: Design an alarm clock for people who are deaf or hard of hearing.
Read what Ava and Grace say
- Ava:
- I'm Ava. Today I'm interviewing Grace, on designing an alarm clock.
- Grace:
- I'm Grace, a PM candidate. My interviews are coming up.
- Ava:
- Design an alarm clock for people who are deaf or hard of hearing.
- Grace:
- Easy. A vibrating pillow pad. Maybe a strobe light too. Done.
- Ava:
- Who is it for? What if that one signal fails?
- Grace:
- One question first: is this a device we sell, or an app on a phone they already own? I'll assume a device. For the user, the goal is waking on time, every time. For the company, a product people recommend. My route is person, pain, options, bet, proof. Some live alone and must wake themselves. Some share a bed and must wake without waking a partner. I pick those who live alone, because nobody else can wake them, so a miss costs the most. Their pains, by how often and how much they hurt. Before sleep, they can't confirm the alarm will work. That is nightly but mild. At wake time, the one signal can fail. That is rare, maybe twice a year, but it can cost a shift or a flight. After, a bed shaker jolts them awake. That is daily and unpleasant, not costly. So the failed signal ranks first, because one miss outweighs a year of rough mornings. Three options. Near: a stronger bed shaker with a battery backup. Far: three layers, a light that brightens slowly, then a wrist buzz, then the shaker, each stepping in if the last one fails. Sideways: text a trusted contact if the alarm isn't dismissed, so a person is the backup. I bet on the layers. Value is high, because it removes the single point of failure. Effort and risk are medium, three parts to build and keep charged. I give up the contact alert for now. Proof. The headline is missed alarms per hundred nights, because reliability is the goal. Two helpers explain it: which layer woke them, and time to dismissal. The guardrail is comfort. Morning ratings must not drop below today's shaker. To sum up. The goal is waking on time, every time. The person is deaf and lives alone. The pain is a signal that fails. The options were a stronger shaker, layers, and a contact alert. The bet is layers, giving up the contact alert. The proof is missed alarms per hundred nights.
- Ava:
- One person, one ranked pain, one bet, and proof. That would score well.
The method in short
Product sense: the Design Ladder
- FrameAsk what would change the design, state the rest, set a goal for the company and the user, and say your route.
- PersonList two to four user groups by what they are trying to do. Pick one and say why.
- PainWalk through before, during and after the task. Rank pains by how often they happen and how much they hurt.
- OptionsOffer three kinds of fix: near (the obvious one), far (ambitious) and sideways (a different angle).
- BetScore the options on value, effort and risk. Pick one and say what you give up.
- ProofOne headline metric, two helpers that explain it, one guardrail you refuse to harm.
- Walk downRead your six commitment sentences back in order. That is your summary.
Example
Solo night runners: design for people who run before dawn; the pain is that nobody knows if something goes wrong; bet on an automatic check-in that alerts a friend when a run overruns, accepting some false alarms.
Most common mistake
Naming features in the first minute, before a user or a pain. Nothing was chosen, so there is no judgment to score.
45 product sense questions to practice
Pick one, answer it out loud on a timer, then open its page to compare with the outline. Start with the warm-ups if this round is new to you. Want a score? Paste your answer into the free answer grader, or answer it out loud with Ava.
Warm-up questions (11)
- What is your favorite product, and why?First move: Pick a product you actually use and can talk about in depth, then name the specific user and job it serves before praising any feature.
- Pick an app on your phone you love. How would you improve it for someone opening it for the first time?First move: Reframe the app through a new user's eyes: what do they need to understand or achieve in the first session to come back tomorrow?
- Design a refrigerator for a family of five.First move: Clarify who in the family uses the fridge and for what, then find the pain points of a busy household before suggesting any gadget.
- Design a smart shopping cart for a grocery store.First move: Ask whether the goal is shopper convenience or store economics, because a cart that saves time and a cart that raises basket size are different products.
- How would you improve the onboarding of a budgeting app?First move: Ask what the first win is for a new user. In budgeting it is usually seeing where your money went, not setting up categories.
- Design an app for a public library system.First move: Ask what the library wants: more members, more borrowing, or more people using its events and spaces.
- Design a parking app for a busy downtown.First move: Ask who the app serves (drivers, garage owners, or the city) and what success means for each before designing screens.
- Design a check-in experience for a doctor's office.First move: Ask who suffers most today: patients filling in the same forms again, or front-desk staff typing them up.
- Design an umbrella for a city where it rains every day.First move: Ask about the city: wind, crowded sidewalks, and how people get around. Daily rain makes durability and storage the real problems.
- Design an app that makes splitting bills among roommates painless.First move: Ask which bills cause the most friction: rent and utilities that repeat, or one-off shared purchases.
- Design a product for dog owners.First move: The trap is designing for every dog owner. Narrow to one owner type and one moment, such as new puppy owners in their first month.
Standard questions (25)
- Tell me about a product you use every day that you think is badly designed. How would you fix it?First move: Separate a genuine design flaw from a personal annoyance by asking who the product is for and whether the flaw hurts them, not just you.
- How would you improve Google Maps?First move: Do not start listing features. Ask what goal matters (engagement, accuracy, new users, local business revenue) and narrow to one user group first.
- How would you improve Spotify for people who listen to podcasts more than music?First move: Split podcast-first listeners into segments by how and when they listen, because a commuter catching up on news and a binge listener of true crime want different things.
- Design an alarm clock for people who are deaf or hard of hearing.First move: Start by asking about the full range of hearing loss and living situations, since someone who lives alone and someone who shares a bed need different wake signals.
- Design a product to help elderly people manage their medications.First move: Ask who the real users are. Often there are two: the older adult taking the pills and a family member or caregiver who worries.
- Design a vending machine for a hospital.First move: Ask who buys from it and when. Night-shift nurses, worried visitors and patients able to walk have very different needs from the same machine.
- How would you improve the airport security experience?First move: Clarify whose experience you are improving: travelers, security staff or the airport. Then pick a traveler type, because a family with a stroller and a frequent business flyer fail in different places.
- Design a museum experience for children under ten.First move: Ask what the museum wants from the visit: learning, repeat visits or family memberships. Then design for the child and the adult with them.
- How would you improve LinkedIn for people who are not looking for a job?First move: Set the goal first. For people not job hunting, the likely goal is regular engagement, so ask what would bring them back weekly.
- Design a carpooling app for a college campus.First move: Ask who the riders and drivers are and what trips matter most: daily commutes, weekend trips home or late-night returns.
- How would you improve YouTube for teachers using it in class?First move: Picture a real lesson: a teacher with thirty students and a projector. Ask what goes wrong in that room before suggesting features.
- Design a feature that helps Airbnb guests feel safe when booking a stay.First move: Ask what 'safe' means to different guests: physical safety, being scammed, or the listing not matching the photos.
- Design a product for people who have just moved to a new city.First move: The prompt is wide, so narrow it fast: pick one type of mover and one need (social, practical or logistical).
- How would you improve Uber's pickup experience at a crowded airport?First move: Name both sides of the problem: riders who cannot find their car and drivers who cannot reach the curb. Pick whose pain to solve first.
- How would you improve Instagram for small business owners?First move: Separate kinds of small businesses (a bakery, a freelance designer, an online shop) and ask which goal they share: getting customers, not followers.
- Design a fitness product for people who hate going to the gym.First move: Find out why they hate the gym. Cost, intimidation, boredom and lack of time each lead to a different product.
- How would you improve WhatsApp group chats?First move: Ask which type of group you are fixing. A family group, a neighborhood group of 200 people and a five-friend group break in different ways.
- Design a ticketing experience for a live concert.First move: Ask whose problem you are solving: fans, the artist or the venue. Then pick the moment that hurts most, often the on-sale rush or entry at the door.
- How would you improve Amazon's returns experience?First move: Recognize the tension upfront: easy returns help customers but cost money. Name both goals before choosing.
- Design a product that helps parents manage their kids' screen time.First move: Ask the age of the children. Rules for a six-year-old and negotiations with a fifteen-year-old need very different products.
- How would you improve Netflix for a family that watches together?First move: Picture a Friday night: four people, one screen, one remote. Ask what goes wrong before anything starts playing.
- You're the PM for a food delivery app. Design a feature for group orders at the office.First move: Picture the organizer chasing ten colleagues for orders and money. Their pain is the starting point.
- How would you improve the experience of renting a car?First move: Walk the journey from booking to return and ask where renters feel the most surprise or stress.
- How would you improve Google Calendar?First move: Ask which users and which goal matter. Personal calendars and calendars of busy professionals are different problems.
- Design a product to help people learn a new language while commuting.First move: Ask what kind of commute. Driving means audio only, while a train ride lets people use a screen.
Stretch questions (9)
- Design a product to help remote teams feel more connected.First move: Push back on the vague goal. Ask what 'connected' looks like when it works: trust, fast help, or simply knowing colleagues as people.
- Design a product for first-time home buyers.First move: Home buying spans months and many parties. Pick one stage, such as getting from offer to closing, rather than designing for the whole journey.
- Design a navigation product for people who are blind or have low vision.First move: Ask about the user's existing tools, such as a cane, a guide dog or a screen reader, so the product adds to them rather than replaces them.
- Design a product for restaurant owners to reduce food waste.First move: Find out where waste happens in a restaurant: over-ordering, prep, spoilage or plate waste. Each has a different fix.
- Design a social product for people over 70.First move: Avoid stereotypes. Ask about health, tech comfort and living situation, because a healthy 72-year-old and a 90-year-old in care need different things.
- How would you improve Slack for a company of 20,000 people?First move: Scale changes the problem. Ask who the user is here: individual employees drowning in channels, or admins worried about security and cost.
- Design a job-search product for people leaving the military.First move: Ask what makes this transition hard: translating military roles into civilian terms is often a bigger barrier than finding listings.
- You designed a feature for ride-sharing drivers. How would you know a month after launch whether it worked?First move: Tie the measure back to the problem the feature solved for drivers. Then add a guardrail so you notice if riders or the business pay for it.
- Design a voting experience for a city election.First move: Ask about constraints first: legal rules, accessibility, security and trust. In voting, trust matters more than speed.
Common questions about this round
What is a product sense interview?
A product sense interview, also called a product design interview, gives you an open prompt such as “design an alarm clock for people who are deaf or hard of hearing” or “how would you improve Google Maps”. You pick a user, find their biggest pain, propose several options, commit to one and explain how you would measure it. The interviewer scores your judgment at each choice, not how clever the final idea is.
How do I structure a product sense answer?
Use one order every time so the interviewer can follow you. The Design Ladder has six rungs: frame the prompt and the goal, pick a person, find their pain, offer options, place your bet, and say what would prove it worked. Then read your six choices back as the summary.
How should I practice product sense questions?
Out loud, on a timer, one question at a time. Answer, then open the outline and compare. Come back to the same question a day later and answer it again. Ten questions done this way teach more than forty read silently.
Get all 200 questions as a PDF
Every question in the bank, all seven round types, with its first move, a strong opening, the answer outline and the common mistake.
From PMInterviewKit
One method for each interview round, 88 short lessons to read or watch, 66 worked answers and mock interviews with Ava. The first lesson of every module is free. The full kit is $129 once.