Library
Cracking the PM Interview: How to Land a Product Manager Job in Technology · 2 of 11
Cracking the PM Interview: How to Land a Product Manager Job in Technology
Entrepreneurship HIGH

Case and Strategy Questions

case-questions strategy marketing pricing frameworks business

Problem This Solves

PM interviews regularly include open-ended business questions — "Should Google launch a TV service?", "How would you price this product?", "Why did Facebook acquire Instagram?" — that have no single correct answer. Candidates fail when they either freeze without complete data or recite memorized frameworks mechanically. This reference covers how to structure any case question, which frameworks apply when, and what interviewers are actually evaluating.

Key Principle

Interviewers evaluate your reasoning process, not the correctness of your conclusion. "An interviewer is not evaluating you on the correctness of your eventual conclusions but rather on the process you take to get there." Structure every answer, drive the conversation forward, and make decisions even under uncertainty — these behaviors signal PM capability.

A secondary principle: "Structure matters, but regurgitating frameworks does not." Frameworks are starting points to adapt, blend, or replace with your own structure as the problem demands.

The Six Case Question Types

Each type has a primary framework:

  1. Strategy — Micro/Macro split + SWOT overlay. Micro: Does the product make money? Will customers want it? Macro: Does it fit the company's vision and open new opportunities? Example: Amazon Kindle succeeds at both levels — it earns margin on hardware (micro) and secures Amazon's content marketplace position (macro).

  2. Marketing — 5-step sequence: Understand the Company, Understand the Competition, Understand the Customers, Understand the Landscape, then Market Your Product. Background analysis should consume a substantial portion of the answer; the marketing plan must flow from that analysis, not precede it.

  3. Launch — Four phases: assess the Product (vision, strengths, weaknesses, risks), set Launch Goals (acquisition, profitability, validation), design the Launch (MVP vs. full, test market, invite-only), then plan Implementation across Pre / During / Post phases. For two-sided platforms, solve the chicken-and-egg problem by prioritizing the supply side in a focused geography first.

  4. Brainstorming — "Structured creativity." Name the object's core attributes or strengths before generating ideas; this unlocks non-obvious uses. Toggle between one-unit and many-unit perspectives and between as-is and modified states.

  5. Pricing — Triangulate using three methods: Cost-Plus (establishes the floor), Value Pricing (estimates customer savings/ROI to set the ceiling), and Competitive Pricing (market anchor). Then refine with experiments, but "inconsistent pricing can frustrate or anger customers." Low prices are not always strategic: "it can signal lower quality to customers, and it might start a price war."

  6. Problem Solving — Decompose the declining metric before diagnosing a cause. Chain: falling profit → revenue or costs → sales volume or price → new customers or retention → traffic or conversion → search, referral, or direct traffic. Once the precise variable is isolated, ask scoping questions (region, product line, timing, competitor moves, recent changes) before proposing a fix.

Good Examples

  • Triangulating notebook price: estimate manufacturing cost (~$5), apply distribution margins (~50% at each level), compare to competitive products, then set price with room to experiment — rather than anchoring solely on competitor price.
  • Diagnosing a traffic decline: confirm the drop is real (not seasonal — compare year-over-year, not month-over-month), isolate whether it is search, referral, or direct, then ask what changed in that specific channel before proposing a solution.
  • Launch answer that names two user types (e.g., drivers and riders), acknowledges the chicken-and-egg problem explicitly, and proposes supply-side seeding in one city before broader rollout.
  • Strategy answer for Facebook acquiring Instagram: micro level — Instagram had no revenue, so the micro case is weak; macro level — Instagram threatened Facebook's social graph dominance and secured a potential competitor. The macro case is compelling.

Bad Examples

  • Refusing to engage because you lack internal data: "A candidate named Michael complained that a question about being CEO was 'unfair' because he lacked insider knowledge — the interviewer was unimpressed."
  • Giving short responses that force the interviewer to extract answers: "If you find your interviewer is asking many follow-up questions and you're only giving short responses each time, you might be riding and not driving."
  • Announcing "I will now apply Porter's Five Forces" and walking through all five forces mechanically regardless of whether they are relevant to the question.
  • Jumping to a marketing plan before analyzing the company, competitors, and customers.
  • Diagnosing a profit decline without first isolating whether revenue or costs are the actual source of change.

Key Quotes

  • "An interviewer is not evaluating you on the correctness of your eventual conclusions but rather on the process you take to get there."
  • "Structure matters, but regurgitating frameworks does not."
  • "Consultants will ask for (and be given) data to solve a problem while PMs will be expected to rely more on their instincts about an issue."
  • "A thorough company might use cost-based pricing, value pricing, and competitive pricing to triangulate on a good price, and then tweak it slightly with experiments."
  • "Remember the goal of these questions is showing you can apply structure to an open-ended problem, make good business decisions, and think wisely about a product's marketing. You can do all of these things even with 'bad' information."
  • "Ideally, you want to go for 'structured creativity.' Structure shows organized thinking and helps your interviewer remember your answer better."
  • "there's a difference between actively trying to ensure your prices are the cheapest and being forced to cut your price to compete. The former is a pro-active strategic decision; the latter is a consequence."

Rules of Thumb

  • Always conclude with a recap. A one- or two-sentence summary after a complex answer demonstrates organized thinking and makes the response memorable.
  • Measure change, not totals. "Measurements since beginning of time are neat, but not actionable." Focus on rate of change and compare year-over-year for seasonality-aware analysis.
  • Break metrics by cohort. Segment by gender, geography, registration date, or user type to generate decision-relevant insight rather than aggregate numbers.
  • If the interviewer flips a question back to you ("What do you think?"), you asked too many clarifying questions. Commit to an answer and explain your reasoning.
  • When a question has an obvious framework match (e.g., pricing → triangulation), name the structure briefly, then move immediately into applying it — do not explain the framework as if teaching a class.
  • For online advertising: CPM = CPC x CTR x 1,000. Maximum willingness to pay per click = conversion rate x profit per conversion. Google search ad conversion rates typically run 2%–5%.

Related References