The product sense interview, and how to answer it

A product sense interview tests whether you can take an open product prompt, choose who it is for, find the problem that matters most and design a solution worth building. Meta runs it as a 45-minute interview in both its initial screen and full loop, scored on four focus areas. Google's APM pages name a close skill, product insight: understand your users, address their needs and weigh trade-offs. Soreno, an AI voice app for PM interview practice, asks a product sense question and then pushes on why this user and why this problem. If an interviewer asks how big your user group is, our free market sizing builder sizes it top-down and bottom-up, no sign-up needed.

Updated

  • It tests judgment. Who is the user, what is their biggest problem, and what would you build first.
  • Meta names four areas. Product landscape and motivation, target audience, the problem, and creative solutions.
  • 45 minutes at Meta. Spend most of it on one user, one problem and one solution you can defend.
  • Pick, then go deep. One user group and one problem, explained well, beat a long feature list.
  • Say it out loud. 12 practice questions below, with our example outlines for three.

How Meta, Google and Amazon describe it, plus 3 example answers

Each company words it differently, but they ask for the same thing: a user you understand, a problem you chose on purpose and a solution you can defend. Everything below is from each company's own careers pages, read on October 28, 2026. The last three rows are example answers we wrote, one for each common type of prompt.

Meta: Product Sense

A named round in both the initial screen and the full loop.

Length
45 minutes, per Meta's PM guide
Initial screen
Product Sense and Analytical Thinking
Scored on
Four focus areas
May ask you to
Sketch the interface

Google: product insight

One of the skills Google's APM pages say its interviews look for.

First interview
A phone interview with a Google PM
Then
A written assignment and more interviews
Product insight
Users, needs, trade-offs, roadmaps
Its tip
Outline your answer at the start
Meta's four focus areasFrom its guide

Meta's PM interview guide says the Product Sense interview covers product knowledge, creativity, problem solving and awareness, and lists four areas the interviewer assesses.

  1. 1

    Understanding the product landscape and motivation

    Why the product exists and where it sits. Meta says questions can start from a product you think is great and what you would do as its PM or CEO.

  2. 2

    Determining target audience

    Who you are building for. Pick one group and say why.

  3. 3

    Identifying and prioritizing the problem

    The pain points that group has, and which one you will solve first.

  4. 4

    Developing creative and impactful solutions

    Ideas that solve that problem. Meta says it may ask you to sketch what the interface could look like and how people would use it.

What Google's APM pages say about product questions1 skill, 4 tips

Google's APM application process page lists the skills its interviews look for and tips from current APMs.

  1. Skill

    Product insight

    Understand your users, address their needs, analyze trade-offs, create long-term roadmaps and know the industry landscape.

  2. Tip

    Give a roadmap first

    Outline the structure of your answer at the very beginning, so the interviewer knows what to expect.

  3. Tip

    Show empathy

    Google calls the PM the main advocate for users inside the company, and asks you to step into their shoes when you think about needs and features.

  4. Tip

    Consider edge cases

    For a product question, Google names internationalization, accessibility and ethics, but asks you to state your core idea before branching out.

  5. Tip

    Evaluate your solution

    Note trade-offs, constraints, and security and privacy issues, and say what belongs in the minimum viable product and what is a nice-to-have.

How Amazon describes product skillsNo named round

Amazon's PM interview prep page does not name a product sense round, as of October 2026. It describes the product skills it wants and says a significant portion of each interview focuses on its Leadership Principles.

  1. The job

    Products built on behalf of customers

    Amazon says a PM creates products and features on behalf of customers, from idea to execution.

  2. The skill

    Purpose, audience and market

    Amazon says PMs have a deep understanding of the product's purpose, target audience and market, and place a strong emphasis on meeting user needs.

  3. The screen

    Half product, half principles

    Its 60-minute phone screen spends half the time on Leadership Principles and half on questions about your product management experience.

    Amazon product manager interview
Our example outline: design a product to help people find a roommateOurs

An example we wrote to show the shape of a strong answer, not a real candidate's answer and not a script. Say it in your own words, in about 25 to 30 minutes with questions.

  1. Clarify

    Set the frame

    Ask whether this is a new company or a feature inside an existing app, and whether we care about one city or many. Assume a new app in large US cities, with the goal of helping people find a roommate they still get along with after six months.

  2. Users

    Pick one group

    List groups: students, young professionals moving for work, people whose roommate just left. Pick young professionals moving to a new city, because they have the least local network and the least time to search.

  3. Problems

    Rank their pain points

    Trust (is this person who they say they are), fit (habits, schedule, cleanliness), and logistics (lease timing, budget). Pick fit as the problem to solve first, because a verified stranger with clashing habits is still a bad outcome.

  4. Solutions

    Three ideas, then choose

    A habits profile with matching, a paid trial week in a short stay, and video calls with a short shared house rules draft. Choose the habits profile plus a house rules draft, because it is cheap to build and tackles fit directly.

  5. MVP

    What ships first

    A short profile on sleep, guests, cleaning and budget, matches ranked on those, and a house rules template both people edit before they meet. Leave payments and lease signing out of version one.

  6. Measure

    How you know it works

    The goal is roommates who still live together at six months. Early signals: share of matches that lead to a meeting and share of meetings that lead to a signed lease. Risks: fake profiles, and bias in matching, which needs a review before launch.

Our example outline: evolve Facebook Groups for neighbors who lend and swap thingsOurs

Meta's guide names Facebook Groups as the kind of existing product a question can start from. This prompt and outline are ours, written as an example.

  1. Why

    Motivation

    Groups already gather neighbors. Lending and swapping could build the local ties that keep people coming back to a group, which we would argue matters more to Meta than one more listing.

  2. Users

    Pick one group

    Members who borrow, members who lend, and group admins. Pick lenders, because without people willing to lend, there is nothing to borrow.

  3. Problems

    What stops lenders

    Worry about getting items back, effort to post, and awkwardness asking for them back. Pick getting items back as the top problem.

  4. Solutions

    Choose one

    A lend post with a return date and automatic reminders, a lender rating visible only inside the group, and admin-set lending rules. Start with the lend post and reminders, the smallest change that removes the biggest worry.

  5. Measure

    Success and guardrails

    Success: items lent per active member and repeat lenders. Guardrail: reports of disputes in the group. Say what you would watch to make sure lending doesn't crowd out the group's normal posts.

Our example outline: improve a public library's appOurs

A shorter example we wrote for the improve-a-product type. It shows how to narrow fast when the prompt is wide.

  1. Clarify

    Goal

    Ask what the library wants: more members, more checkouts or more event visits. Assume more people using the library each month.

  2. Users

    Pick one group

    Parents of young children, students, retirees, people who only read ebooks. Pick parents, because they borrow often and plan visits around their kids.

  3. Problem

    The pain to solve

    Popular picture books are always out and holds take weeks. Pick that over search or event discovery.

  4. Solution

    What to build

    Holds that suggest similar books available now at the nearest branch, ready for pickup that day. Measure monthly active members and pickups per hold.

From Meta: PM interview prep, Meta: PM interview Q&A, Google: APM application process, Google: APM preparation materials and Amazon: PM interview prep.

What does the interviewer look for in a product sense answer?

No company publishes a full scoring rubric. This is our reading, built on Meta's four focus areas and Google's APM tips.

  • A user you chose on purpose

    Meta scores determining the target audience. Google asks for empathy for users' needs and constraints.

    Show what they listen for
    What interviewers listen for
    Two or three groups named, then one picked with a reason.
  • A problem worth solving

    Meta scores identifying and prioritizing the problem. Ranking pain points out loud shows judgment.

    Show what they listen for
    What interviewers listen for
    Why this problem first, not just what it is.
  • Creative, buildable ideas

    Meta scores creative and impactful solutions and may ask you to sketch one. Google asks what belongs in the first version.

    Show what they listen for
    What interviewers listen for
    Several ideas, one chosen, and a clear first version.
  • Trade-offs and edge cases

    Google asks you to note trade-offs, constraints, privacy and security, and to think about accessibility and other edge cases.

  • You lead the conversation

    Meta says the interviewer can guide you, but you should lead. Google suggests outlining your answer at the start.

    Show what they listen for
    What interviewers listen for
    A plan up front and check-ins at each step.

From Meta: PM interview prep and Google: APM application process.

How do you answer a product sense question?

Our seven-step outline. It follows the order of Meta's four focus areas and adds what Google's tips ask for. Use it as a checklist, not a script.

Seven steps, about 30 minutes
  1. Step 1

    Clarify and lay out your plan

    Ask one or two questions about the goal and limits, state your assumptions, then say the steps you will take. Google says its questions often leave room for clarification.

    From Google: interview tips and Google: APM application process.

  2. Step 2

    Explain why the product exists

    The mission, who it serves today and what the company gains. This is Meta's product landscape and motivation.

    From Meta: PM interview prep.

  3. Step 3

    Pick one user group

    List two or three groups and pick one, with a reason such as size, unmet need or fit with the goal.

    Size a user group
  4. Step 4

    Rank their problems and choose one

    Three or four pain points, ranked by how often they happen and how much they hurt. Choose one and say why.

  5. Step 5

    Generate three solutions, then pick

    Range from simple to bold, then pick one on impact against effort. Be ready to sketch it if asked.

    From Meta: PM interview prep.

  6. Step 6

    Define the first version

    What ships first and what waits. Google asks what belongs in the minimum viable product and what is a nice-to-have.

    From Google: APM application process.

  7. Step 7

    Say how you would measure it and what could go wrong

    One success metric tied to the goal, one guardrail, and risks such as privacy, accessibility or misuse. Then sum up in two sentences.

    Metrics questions

Our outline. No company publishes a required structure for this interview.

12 product sense practice questions

Soreno's own prompts, written so none repeats our other PM guides. Example outlines for three of them are in the rows above.

Design a new product4 questions

Start from a user and a need, not a feature.

  1. Design a product to help people find a roommate.

    What a strong answer does

    Picks one group, such as people moving to a new city, makes fit the core problem and ships a small first version. Our outline is above.

    • “How would you stop fake profiles?”
    • “What would you build second?”
  2. Design a product that helps high school students choose a college major.

    What a strong answer does

    Separates students from parents and counselors, finds the real gap (not knowing what the jobs are like) and tests ideas cheaply.

    • “How would you make money?”
    • “How would you reach students?”
  3. Design a fitness app for people who have never exercised.

    What a strong answer does

    Treats starting and sticking as the problem, not workouts. Small first steps and a clear habit metric.

    • “What would make someone quit in week two?”
  4. Design an AI assistant that helps small landlords answer tenant messages.

    What a strong answer does

    Picks one kind of landlord, finds the messages that eat the most time, and says what the assistant should never answer on its own.

    • “What happens when it gives a wrong answer?”
    • “How would tenants know they're talking to an AI?”
Improve an existing product4 questions

Know the product's goal before you change it.

  1. How would you improve a public library's app?

    What a strong answer does

    Clarifies the library's goal, picks one user group and solves one pain point well. Our outline is above.

    • “What would you remove from the app?”
  2. Pick a product you think is badly designed. How would you fix it?

    What a strong answer does

    Names who it fails and why, separates taste from real problems, and keeps the fix small enough to ship.

    • “Why do you think the team built it that way?”
    • “How would you test your fix?”
  3. How would you improve a ride-hailing app for parents traveling with small children?

    What a strong answer does

    Finds the moments that go wrong, such as car seats and pickup timing, and weighs what it takes from drivers.

    • “How would drivers react?”
  4. How would you make a shared family calendar app more useful for busy households?

    What a strong answer does

    Picks the parent who plans the week, finds the coordination gap and keeps the fix simple for everyone else in the house.

    • “How would you get the rest of the family to use it?”
Evolve or grow a product4 questions

Meta's guide says questions can start from an existing Meta product.

  1. How would you evolve Facebook Groups for neighbors who want to lend and swap things?

    What a strong answer does

    Starts from why Groups exists, picks lenders as the group that unlocks the rest and ships the smallest fix. Our outline is above.

    • “What would you do if items started going missing?”
    • “How would admins feel about this?”
  2. How would you help small businesses sell more on Instagram?

    What a strong answer does

    Picks one kind of business, finds where sales drop off from discovery to purchase and fixes that step.

    • “How would you avoid cluttering the feed?”
    • “Which metric would you watch?”
  3. Users of a language-learning app quit after the first week. What would you build?

    What a strong answer does

    Diagnoses why they leave before building, then targets the moment motivation drops with one change.

    • “How would you know the change worked?”
  4. You are the CEO of a product you love. What would you build next?

    What a strong answer does

    Explains why the product is great, then picks a next step that fits its mission, not just a feature you want.

    • “What would you stop doing?”
    • “Who would you lose by doing this?”

Mistakes, prep plan and FAQ

Mistakes to avoid in a product sense interview
  • Jumping straight to features

    Ideas before a user and a problem sound random. Meta's focus areas put the audience and the problem before solutions.

  • Serving everyone

    A product for all users solves nothing well. Pick one group and say why.

  • A long list with no choice

    Ten ideas show creativity but not judgment. Rank them and commit to one.

  • Waiting to be led

    Meta says you should lead the conversation. Lay out your plan and check in at each step.

  • No way to measure it

    Without a success metric you can't say whether the idea worked. Tie one metric to the goal you set in step one.

  • Forgetting edge cases

    Google names accessibility, internationalization and ethics. One sentence on each risk shows you thought past the happy path.

How to prepare for a product sense interview

A two-week plan in our words, drawing on what Meta and Google suggest.

  1. Days 1 to 2

    Read the company's own prep page

    Meta's PM guide spells out the four focus areas. Google's APM pages list the skills and tips. Then read our guide for that company.

    Meta PM interviewGoogle PM interview

    From Meta: PM interview prep and Google: APM application process.

  2. Days 3 to 6

    Take products apart

    Google's prep page passes on one APM's tip: take products from Google's product list and ask what you would change, how you would prioritize the changes and what trade-offs you would make. Do one a day.

    From Google: APM preparation materials.

  3. Days 7 to 10

    Answer out loud and record yourself

    Meta suggests a practice interview, recorded or with a friend. Google says to do mock interviews and record yourself. Use the questions above and time each one.

    From Meta: PM interview prep and Google: APM application process.

  4. Days 11 to 14

    Practice with pushback

    The follow-ups are where answers break. Practice with someone, or something, that asks why this user and why this problem.

    Soreno PM practiceMore PM interview questions

Practice product sense with follow-ups

Soreno's AI interviewer asks a product sense question, then pushes on your choices the way an interviewer does: why this user, why this problem, what ships first. It scores the session and shows you what to fix. The questions and example outlines on this page are Soreno's own. Soreno is not affiliated with Meta, Google or Amazon.

Questions people ask

What is a product sense interview?

A product management interview where you design or improve a product out loud. You pick a user, choose the problem that matters most, propose solutions and say what you would build first. Meta names it Product Sense, and Google's APM pages call the skill product insight.

How long is a product sense interview?

At Meta, 45 minutes, in both the initial screen and the full loop. Google doesn't publish a length on the pages we read in October 2026. Amazon has no separate product round, but its PM phone screen is 60 minutes, half on product management questions, and its loop interviews are 55 minutes each.

What is the difference between product sense and analytical thinking at Meta?

Product Sense is about the user, the problem and the solution. Meta's Analytical Thinking interview is about metrics, goals and trade-offs, with focus areas such as setting measurable goals and identifying metrics.

Is product sense the same as product design?

Mostly. Companies use different names for the round where you design or improve a product. Read the prep page for the company you are interviewing with.

Do I need to draw in a product sense interview?

Sometimes. Meta says it may ask you to sketch what your interface could look like and how people would use it, so practice on a whiteboard or paper.

How do I improve my product sense?

Use products on purpose. Google's APM pages suggest thinking about products you like and dislike and how to make them better, and practicing with mock interviews.

Is there a framework for product sense interviews?

Our seven steps above are one. Meta's guide gives four focus areas, not a framework, and Google asks you to outline your answer at the start. Any framework works if you still pick one user and one problem out loud and say why.

Can I use AI tools during a product sense interview?

Not at Meta or Google. Meta's PM guide asks candidates not to use unauthorized outside assistance, including AI tools like ChatGPT, during interviews, and Google says AI tools are not permitted during its interviews.

Keep going