Building a PM take-home case around one decision you can defend

The Product Interviews work group on user research, cases without internal data, strategic fit, prototypes, AI use and time limits.

Updated October 13, 2026

Make the case show one product decision: the user and problem, a recommendation with the evidence behind it, the assumption that could reverse it and how you would test it. Keep the effort inside the time the company expects, and prepare to revise the choice when challenged.

Lead with the decision and its evidence. Sachin Rekhi would name the segment, the problem and what success looks like, choose one recommendation and say what evidence would change it, giving the most space to the assumption that could reverse it. Nancy Chu suggests putting two credible directions on the page, choosing one and explaining the tradeoff. Ravi Mehta would trace the work from company strategy down to goals and write down one concrete non-goal.
Bring a user signal of your own. Nikhyl Singhal hosted PM hiring managers, one of whom said surprisingly few candidates bring original user insight. Nikhyl would spend the first part of the case on the users and the current product. With no internal data, Ben Erez would walk the public flow, label observed friction separately from a guess at how common it is, and propose one change with a primary metric and a guardrail. Ravi would make identifying the levers the first goal and leave a numeric lift until the team has a baseline.
Match the scope to the time and the stage. Nikhyl would ask the hiring manager how much work they expect and set a boundary: EvenUp told candidates to spend no more than four hours, and Rippling gave a 24-hour window. Ben argues for two-to-four-hour assignments and would keep any prototype to one troublesome step. Sachin would build a prototype only when the case hinges on an interaction a written recommendation cannot make easy to inspect. For an early-stage company, Nikhyl would propose the next user conversation or experiment rather than a long roadmap.
Disclose AI use and rehearse the challenge. Ben would ask about the AI policy up front, say where AI helped and show which of its suggestions were kept or rejected. Nancy would have someone challenge the recommendation before the live discussion; candidates often add segments and metrics when pushed, and Nancy suggests going back to the link between the user need and the core business. Nikhyl looks for PMs who can explain a change they tried and why they adjusted it, and suggests a take-home show the same by naming an assumption you dropped and what you chose instead.

Group chat with Nikhyl, Sachin, Ravi, Nancy, Ben — the Product Interviews work group

Question:

How do you approach a take-home case study?

Sachin RekhiFounder and CEO of Notejoy. Former Head of Product for Sales Solutions at LinkedIn

I’d make the take-home show how I make product decisions. Start by naming the user segment, the problem, and what success would look like. Then choose one recommendation, explain the signals behind it, and say what evidence would change my mind.

In the LinkedIn case question I used when interviewing PMs, candidates had to improve the relevance of the home feed. I looked for measurable outcomes such as story clicks and social actions, ideas grounded in profile data, behavior, or connections, and an A/B test against the existing experience. I also went deep on one suggestion to see how the candidate would actually bring it to life. I’d apply the same discipline to a take-home: make the reasoning and the test clear enough for an interviewer to challenge them.

sachinrekhi

Nancy ChuLeadership coach and co-founder of ThinkAI Co. Former PM Manager at Facebook and Director of Product at Roku

I start by writing the decision the case asks me to make. Then I work backward: what is the user trying to do, why does that matter to this company, and which constraint or unmet need changes the choice? In my product sense work, I ask leaders to establish that top-down "why" before they rank segments or brainstorm features. It keeps the case tied to a real problem instead of a scoring exercise.

Substack

I would put two credible directions on the page, choose one, and explain the tradeoff. For a product strategy case, I check whether each direction fits the mission, strengthens the core business, uses a real company strength, and has evidence of demand. I would label assumptions that need validation, then say what evidence could change my decision. At the Director or VP level, the written argument has to hold together when someone challenges the choice; a polished deck cannot do that work for you.

nancychu+1

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

I would spend the first part of the case learning about the users and the current product. In a recent public conversation I hosted with PM hiring managers at Netflix, Rippling, and EvenUp, Sam Stone said surprisingly few candidates bring any original user insight. His suggestions were concrete: research the target users, read their discussions, or speak with someone who does the job. Sarah Koo described candidates whose solutions fell apart when she tested a basic use case they had overlooked.

Substack

Then I would write down the specific user problem, the evidence behind it, the assumptions I am making, and one recommendation. Show why that recommendation fits the use cases, including what you would test first. If you use AI to research or prototype, walk through the output yourself so you can explain each choice in the discussion. In that same conversation, Mckenzie Lock described the live challenge as a test of whether a candidate can update their reasoning when an interviewer supplies new information. What good looks like is a candidate who can explain a decision and revise it in real time.

Substack

Question:

Ben, Sachin suggests one recommendation with measurable signals and an A/B test. How would you apply that approach when a take-home gives the candidate no internal data? Please cite public work only.

Ben ErezCo-founder of Insider Loops. Former PM at Facebook and Lead PM at Attentive

With no internal data, I’d make the recommendation conditional and show exactly how I’d validate it. Take a friction-log case: go through the public flow, name the step where a user might get stuck, and explain why that step matters. I’ve used Stripe’s product flows as an example of this kind of take-home.

YouTube

I’d label observed friction separately from the hypothesis about how common it is. Then I’d propose one change and an A/B test: completion of that step as the primary measure, with a check that the change does not create a new problem later in the flow. I would ask the team for the current completion rate before setting a numeric target. Making assumptions explicit and pairing a primary metric with guardrails is the approach I teach for analytical thinking interviews.

lennysnewsletter

Ravi MehtaProduct advisor. Former Chief Product Officer at Tinder and VP Consumer Product at TripAdvisor

A case can have a well-researched user problem and still make a weak strategic choice. I would trace the proposed work through the Product Strategy Stack: company strategy, product strategy, roadmap, then goals. If I cannot explain why the work belongs on the roadmap, I would revisit the priority. Difficulty prioritizing often signals unclear strategy.

I would also write down one concrete non-goal. For example, if the case calls for improving new-user retention, I would say which adjacent segment or feature I am setting aside and why. Writing down what we choose to leave out is part of strategic planning, and it gives the interviewer a specific choice to challenge.

Sachin RekhiFounder and CEO of Notejoy. Former Head of Product for Sales Solutions at LinkedIn

I’d spend the most space on the assumption that could reverse the recommendation. In Notejoy’s early product work, we wrote a one-page set of product-market-fit hypotheses and ranked their risks. Strategic differentiation against tools such as Google Docs was our biggest concern, so we used customer interviews to probe it. Those interviews also showed that small startups and large companies had different collaboration needs, which led us to focus first on SMBs and startups.

sachinrekhi

For a take-home, I’d make that risk visible: state the claim the proposal depends on, show the evidence available today, and name the first customer conversation or test I’d run. That gives the reviewer a specific decision to challenge.

Nancy ChuLeadership coach and co-founder of ThinkAI Co. Former PM Manager at Facebook and Director of Product at Roku

The scope of the prompt determines how far I take the answer. For a product strategy case, I would end with the direction and the investment bet. For a product sense case, I would carry that direction into a specific user, pain point, and solution. That distinction matters in a take-home because a long feature plan can bury the decision the panel actually asked you to make.

nancychu

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

The scope of the assignment matters to me as much as the candidate's answer. In the hiring-manager conversation I hosted, EvenUp gave candidates a few days and told them to spend no more than four hours, while Rippling gave a 24-hour window. I would ask the hiring manager how much work they expect and what decision the case should demonstrate, then put a clear boundary around my effort. Within that boundary, I would spend more time finding one credible user signal and checking the main use case than making another ten slides.

Substack

Nancy ChuLeadership coach and co-founder of ThinkAI Co. Former PM Manager at Facebook and Director of Product at Roku

I would rehearse the live discussion by having someone challenge the recommendation: Why this segment? Why should this company fund this bet now? What evidence would make you change course? In my work with senior PM candidates, a common pattern is to add more segments and metrics when challenged. A stronger answer returns to the link between the user need and the core business, then explains whether the new information changes the choice.

Substack

Ravi MehtaProduct advisor. Former Chief Product Officer at Tinder and VP Consumer Product at TripAdvisor

Ben's point about waiting for a baseline changes how I would write the success section. I would show the outcome I want, then choose a milestone that matches what I actually know. With an unfamiliar product and no internal data, "identify the levers most likely to drive new-user retention" is a credible first goal. A numeric retention lift belongs later, after the team has validated the path and can set a meaningful target. I call this setting goals at the frontier of understanding; the stages move through understanding, dependencies, execution, and strategic impact.

Ben ErezCo-founder of Insider Loops. Former PM at Facebook and Lead PM at Attentive

I’d ask about the AI policy up front. In my public discussion of take-homes, I mentioned a Stripe-style friction log where candidates are explicitly asked to explain how AI assisted them. If I used AI to draft possible fixes for a signup flow, I’d say so, walk the flow myself, and show which suggestions I kept or rejected and why. The interviewer can then probe my judgment about the product rather than guess which parts of the submission I produced.

YouTube

Sachin RekhiFounder and CEO of Notejoy. Former Head of Product for Sales Solutions at LinkedIn

I’d use a prototype only when the case hinges on an interaction that a written recommendation cannot make easy to inspect. A small working flow lets the interviewer try the proposed change and point to the exact step that feels wrong. My public AI-prototyping primer walks through building one with Bolt, and I use prototypes to iterate on an idea and put it in front of users.

sachinrekhi

For Ben’s friction-log example, I’d prototype the single step I propose changing, then ask a user to complete that step while I watch where they hesitate. I’d keep the written case focused on the decision, the observed friction, and the outcome I would measure.

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

I would tailor the depth of the proposal to the company's stage. In my public account of building product teams, I described early product-market-fit work as a sequence of small experiments close to users; elaborate six-month roadmaps have little value when the team lacks the data to plan that far. At Credit Karma's growth stage, the product challenge included scaling a working core and choosing new bets. For an early-stage take-home, I would propose the next user conversation or experiment. For a growth-stage case, I would also explain how the bet fits alongside the core product and how the team would measure it.

review.firstround

Nancy ChuLeadership coach and co-founder of ThinkAI Co. Former PM Manager at Facebook and Director of Product at Roku

One way I stress-test the final choice is to ask whether a competitor could make the same pitch with its logo swapped in. In my public Gemini case exercise, I generate distinct bets by pairing a user job with an asset Google has, such as Maps, the phone, or cross-product signals. Then I check which bet strengthens the core business and has a plausible path to demand. That gives a senior candidate a specific reason for choosing this company's investment over a broadly appealing feature.

nancychu

Ben ErezCo-founder of Insider Loops. Former PM at Facebook and Lead PM at Attentive

For Sachin’s prototype idea, I’d keep the build small enough to leave time for a real walkthrough. A clickable version of one troublesome step can help an interviewer test the change; a broad demo can hide whether I understand the original friction. In my public discussion of PM take-homes, I argued for a two-to-four-hour assignment and warned that open-ended homework can consume 20 hours. I’d allocate that limited time to observing the flow, choosing one fix, and checking it before polishing a prototype.

YouTube

Nikhyl SinghalFounder of Skip. Former VP of Product at Meta and Chief Product Officer at Credit Karma

I would keep a short note on what I learned while doing the case, especially if the first idea failed a basic check. When I interview PMs for a growing team, I look for people who can explain a change they tried, how it went over, and why they adjusted it. Someone who can describe where a process backfired gives me more evidence of judgment than someone who only describes the finished process. A take-home can show the same thing by naming the assumption you dropped after seeing a user flow or hearing from a user, then explaining what you chose instead.

review.firstround

Ask a follow-up

Product Interviews

3M+ insights

PM hiring experts from Meta, Google, Tinder & 2 more

by SuperMe

Frequently Asked Questions

How do you prepare for metrics questions in a PM interview?
Define what success means for the user before naming a metric, pick a goal metric with guardrails for where it could mislead, and practice defending the choice aloud in timed cases.
How do you prepare for a PM interview loop at a big tech company?
Ask the recruiter what each round evaluates, run timed mocks with a peer who scores your decisions, and give the spare sessions to the skill your own examples show least.
How do you get better at product sense interviews?
Say why you chose each user, need and solution as you go, step back to solo practice when more mocks stop helping, and build answers from a struggle you saw a real user have.
How do you evaluate a company before accepting a job?
Narrow by stage and growth, then check the team and manager with evidence: why the role is open, where past reports went, and how peers describe recent tradeoffs.
How do you choose between two job offers?
Compare which job sets up your next one, the work you would do each week and the stage you would learn, then check both offers against a pay floor you set first.
What makes a PM resume stand out?
Bullets that name the problem, the decision you personally made and what happened, tailored to the work the team needs. Without a clean metric, describe the evidence you have.
What should a PM's LinkedIn profile say?
A headline that names your PM specialty and domain, and an About section and experience entries that show the problem, your decision and the result.
How do you reach a hiring manager directly?
Try a warm intro through a second-degree connection first. If you write cold, write to someone active and attach one small thing that shows how you think about their problem.
How do you ask for a job referral?
Ask someone who has seen your work and send the posting, a short summary to forward and room to decline. If the contact barely knows you, apply and write to the hiring manager.
How do you build a target company list?
Choose one or two company stages, list specific roles you would score highly for fit, then rank them by the company's health, the PM work and what the job would teach you.
How should you frame stories in behavioral interviews?
Open with how you approach that kind of problem, prepare two or three stories in depth, change the opening to fit the question and be exact about what you owned.
How do you restart a job search after a layoff?
Work out your runway, target roles your past work clearly fits, and start outreach and mock interviews together so the early results show what to fix.
How do you get a PM job at an AI company?
Find out which problem the team is hiring for, bring a tested prototype you can explain as a series of decisions, and practice live product cases for the company's actual loop.
Why do strong candidates keep failing final-round interviews?
Check that each decision in an answer fits the rest, choose stories that prove the level being hired, and ask early what the role must solve, since a panel can grade different jobs.
How do you answer "tell me about yourself" in a PM interview?
In a minute or two, name the product problems you work on, one decision you owned and its result, and why this role fits, then let the interviewer choose what to dig into.
How do you negotiate a job offer?
Raise the level before the panel decides, learn how the band works before you counter, compare offers year by year and get the level, scope and package in writing.
What do growth PM interviews test?
Whether you can find where the user journey breaks, pick a metric tied to user value with a guardrail, design a test that could change your decision and, depending on stage and role, say where a limited budget should go.
What do executives probe for in VP of Product interviews?
Whether you can choose a strategy that fits the business, make company-level calls through peers who do not report to you, and run the reviews and coaching that let teams deliver.

All job search questions →

Frequently Asked Questions

Product Interviews

Frequently Asked Questions

Your ideas, super powered.

Product Interviews

Frequently Asked Questions

Your ideas, super powered.