Skip to main content

Product manager domain knowledge interview questions

12 questions on domain knowledge for product manager candidates. Expect prompts such as “Defining and measuring product-market fit” and “The AARRR funnel and where most products fail”, each with a worked answer outline and the follow-ups interviewers push on.

Questions

Showing 1 to 12 of 12 domain knowledge questions.

As asked

How do you define product-market fit and what signals tell you that you have it or are far from it?

Sample answer outline

A strong answer references the Sean Ellis survey (40% who would be very disappointed if product disappeared), retention curve flattening, organic word-of-mouth growth, and the qualitative signal of users pulling the product rather than the team pushing features. The candidate should explain that PMF is a spectrum rather than a binary state, that it can be strong in one segment and absent in another, and that it is possible to lose PMF as the market evolves.

Expect these follow-ups

  • Can a product have strong PMF in one geographic market and none in another?
  • What do you do when you think you have PMF but growth is still slow?
domain-knowledgeproduct-sensemetricsstrategy

As asked

Walk me through the AARRR framework. In your experience, where do most consumer apps fail along this funnel and why?

Sample answer outline

A strong answer explains Acquisition, Activation, Retention, Referral, and Revenue, noting that most apps fail at activation and retention rather than acquisition, because getting people to the product is easier than delivering value fast enough to form a habit. The candidate should describe common activation failure patterns (too much friction, unclear value proposition, poor empty state) and retention failure patterns (no hooks, no notifications, no reason to return).

Expect these follow-ups

  • How does the AARRR funnel differ for a B2B SaaS product versus a consumer mobile app?
  • Is there a stage in the funnel you would sacrifice to strengthen another?
domain-knowledgegrowthfunnelproduct-sense

As asked

Your engineering manager asks why you need to wait three more weeks before calling the A/B test. Explain statistical significance and sample size requirements without using technical jargon.

Sample answer outline

A strong answer translates the concept into the risk of making a wrong call: stopping early means a higher chance that the difference you are seeing is just noise rather than a real effect, and that calling it early is like concluding a coin is biased after five flips. The candidate should explain that the sample size required depends on how small a difference you care about detecting, the baseline conversion rate, and the accepted risk of a false positive versus false negative.

Expect these follow-ups

  • What is the cost of a false positive versus a false negative in this specific experiment?
  • How do you handle the business pressure to call experiments earlier than the required runtime?
domain-knowledgestatisticsexperimentationcommunication

As asked

Walk me through the key metrics specific to a SaaS business: ARR, MRR, churn, NRR, and expansion revenue. How do they interact and which is the most important to optimize?

Sample answer outline

A strong answer correctly defines each metric, explains that net revenue retention above 100% means the business can grow without acquiring new customers, and discusses the interplay between churn and expansion. The candidate should argue that the 'most important' metric depends on business stage: early stage focuses on ARR growth, more mature business focuses on NRR and LTV. They should describe what a healthy benchmark looks like for B2B SaaS.

Expect these follow-ups

  • How does a move-upmarket to enterprise affect these metrics compared to SMB-focused SaaS?
  • What does negative net churn mean and how do you achieve it through product decisions?
domain-knowledgesaasmetricsproduct-sense

As asked

Explain product-led growth. What product characteristics make it viable, and what are the situations where a sales-led motion is better?

Sample answer outline

A strong answer explains PLG as using the product itself as the primary acquisition, conversion, and expansion channel, enabled by a self-serve onboarding experience, a viral or collaborative component, and a freemium or free-trial model. The candidate should describe that PLG works best for products with wide top-of-funnel, fast time to value, and low implementation complexity, while sales-led is better for products with high customization, long procurement cycles, or complex use cases that require human guidance.

Expect these follow-ups

  • How do you run a hybrid PLG plus sales-led motion without the two conflicting?
  • What is the leading indicator that a PLG motion is starting to work?
domain-knowledgegrowthstrategyproduct-sense

As asked

Name three concepts from behavioral psychology or behavioral economics that you actively consider when making product decisions, and give a concrete product example for each.

Sample answer outline

A strong answer picks from a rich set: loss aversion (framing a trial end as losing access rather than a subscription start), variable reward schedules (notification timing to create habits), anchoring (pricing page design), sunk cost (streaks and progress bars), or the endowment effect (personalization increases perceived ownership). The candidate should be nuanced about the ethics of using these techniques and distinguish between genuine value-creating uses and manipulative dark patterns.

Expect these follow-ups

  • Where is the line between applying behavioral psychology helpfully versus manipulatively?
  • Which of these has the most evidence behind it in a mobile app context?
domain-knowledgepsychologyproduct-sensedesign

As asked

You do not need to write API code, but what do you need to understand about APIs to be effective as a PM working with developers and enterprise customers who want integrations?

Sample answer outline

A strong answer covers REST versus webhooks at a conceptual level, authentication (API keys and OAuth), rate limiting and how it affects customers, versioning and the cost of breaking changes, and the developer experience of documentation and SDKs. The candidate should explain how API design decisions create long-term obligations and why PMs should be involved in scoping and naming decisions before APIs go public.

Expect these follow-ups

  • A key integration partner says your API is missing a critical field. How do you prioritize that versus other backlog items?
  • How do you balance developer-friendliness with security in an API product?
domain-knowledgetechnical-fundamentalsproduct-senseintegrations

As asked

What is the difference between direct and indirect network effects, and give me a product example of each. How do these differences affect how you build and grow the product?

Sample answer outline

A strong answer explains direct network effects (value increases as more people use the same side, e.g., messaging apps) versus indirect network effects (value increases for one side as the other side grows, e.g., app stores). The candidate should describe how direct network effects create a winner-take-most dynamic and how indirect network effects require careful balancing of both sides. They should connect this to specific product strategies like local density first, subsidizing one side, or cold-start problem solutions.

Expect these follow-ups

  • What is a data network effect and how is it different from a traditional network effect?
  • Can network effects be negative? Give me an example.
domain-knowledgenetwork-effectsstrategyproduct-sense

As asked

Compare at least three product discovery frameworks, such as Design Thinking, Lean Startup, and Continuous Discovery. When would you reach for each one?

Sample answer outline

A strong answer correctly describes the core of each: Design Thinking (empathize, define, ideate, prototype, test), Lean Startup (build-measure-learn loop with MVP), and Continuous Discovery (Teresa Torres, opportunity solution tree with continuous customer touchpoints). The candidate should argue that Continuous Discovery fits mature product teams with ongoing access to users, Lean Startup suits early-stage exploration, and Design Thinking suits well-defined problem spaces that benefit from structured ideation.

Expect these follow-ups

  • Have you used any of these in a way that felt wrong for the context?
  • How do you choose a framework for a team that has never done structured discovery before?
domain-knowledgediscoveryframeworksproduct-sense

As asked

Why does accessibility matter from a product perspective beyond compliance, and how do you make sure it is not an afterthought in your team's process?

Sample answer outline

A strong answer moves beyond legal compliance to argue that accessibility expands the addressable market, improves usability for all users (curb-cut effect), and reduces technical debt from retrofitting. The candidate should describe practical process interventions: including accessibility acceptance criteria in stories, involving QA with screen reader testing, auditing at design stage before code, and using WCAG guidelines as a shared reference point.

Expect these follow-ups

  • How do you make the business case for investing in accessibility to an executive who sees it as a cost?
  • What is the most common accessibility issue you see in products you have worked on?
domain-knowledgeaccessibilityproduct-sensedesign

As asked

What is the difference between a platform product strategy and a feature product strategy? When does it make sense to invest in building a platform?

Sample answer outline

A strong answer describes a platform as infrastructure that enables third parties or other internal teams to build on top of it, creating network effects and compounding value, whereas a product strategy focuses on delivering direct user value. The candidate should explain that a platform bet requires critical mass before it generates value, takes longer to ship, and requires thinking about backwards compatibility and developer experience as first-class concerns. They should describe the risk of prematurely platformizing before product-market fit is proven.

Expect these follow-ups

  • How do you decide when to dogfood your own platform by building products on it?
  • What is the hardest part of making the cultural shift from product-first to platform-first thinking?
domain-knowledgeplatformstrategyproduct-sense

As asked

When does it make sense to build a native mobile app versus a mobile-optimized web product? What are the product-level trade-offs, not just the technical ones?

Sample answer outline

A strong answer covers distribution (app store friction versus open web), engagement (push notifications, home screen presence), capability (camera, offline, biometrics) versus web (SEO, shareability, no install barrier), and development cost. The candidate should connect these to product context: if the use case is habitual and feature-intensive, native wins; if it is occasional or discovery-driven, web wins. They should describe progressive web apps as a middle ground.

Expect these follow-ups

  • How do you handle the case where your two most important user segments prefer completely different platforms?
  • What metrics would you track to decide whether to invest in a native app after launching on web?
domain-knowledgemobileproduct-sensestrategy