Interview OS
Back to Non-technical

Library

Product sense

Users, goals, tradeoffs.

Product

Overview

Product-sense questions test intuition for what to build and why. You demonstrate it by anchoring on users, articulating a problem worth solving, and reasoning about tradeoffs and success metrics.

How it works

Product
UserGoalSolveMeasureNeedpersonaMetricnorth-starPrioritizeRICEValidate
ClientServiceEdgeData

Step by step, with examples

  1. 1

    Need

    • Who they are and their pain.
  2. 2

    Metric

    • Define what success means.
  3. 3

    Prioritize

    • Trade off the features.
  4. 4

    Validate

    • Metrics and an experiment.
    • Example: retention

Overview

Anchor on a user and a metric, generate ideas, prioritize by impact/effort, and define how you'd measure success.

Common pitfalls

  • Feature lists with no prioritization
  • No success metric
  • Ignoring the user segment

Where this content comes from

For full transparency, this content is curated and verified from these sources:

Behavioral interview frameworks (STAR/CAR)Consulting case-interview casebooksOppZen-authored communication playbooks