Never freeze on a product sense question again

Product Sense

How would you improve X? Design a product for Y. Prioritization frameworks like RICE and ICE. User empathy, pain point identification, and creative product thinking.

"How would you improve Instagram Stories?"

Identify user segments: creators vs viewers. Creators want reach + engagement — add a "Story Series" feature that lets creators chain multiple stories into a narrative with a subscribe button. Measure: completion rate, series subscriptions, creator retention. Prioritize via RICE: high reach (all creators), strong impact (engagement), low effort (extends existing UI).

Metrics & Analytics

North star metrics, metric trees, A/B testing design, statistical significance, counter-metrics, and diagnosing metric movements.

"What metrics would you track for Uber Eats?"

North star: orders per active user per month. Metric tree — Acquisition: app installs, sign-ups. Activation: first order within 7 days. Engagement: orders/week, reorder rate. Monetization: AOV, take rate. Retention: 30-day cohort retention. Counter-metrics: delivery time, driver cancellation rate, restaurant churn. A/B test new features by city-level holdout.

Strategy & Roadmap

Feature prioritization, roadmap building, stakeholder alignment, competitive analysis, market positioning, and resource allocation.

"How would you prioritize features for Slack?"

Start with strategic pillars: (1) reduce noise, (2) deepen enterprise adoption, (3) improve async collaboration. Score features against pillars + RICE. High priority: threaded summaries (AI-powered) — high reach across all users, strong impact on noise reduction, medium confidence, low effort with existing LLM infra. Align stakeholders by tying each feature to a quarterly OKR.

Execution

Launching a new feature end-to-end, go-to-market strategy, cross-functional coordination, handling trade-offs, and managing technical debt.

"Walk me through launching a new feature"

Phase 1 — Discovery: user research, competitive analysis, define success metrics. Phase 2 — Spec & alignment: PRD, design review, eng scoping, legal/privacy review. Phase 3 — Build: sprint planning, weekly syncs with design + eng + QA, beta dogfood internally. Phase 4 — Launch: staged rollout (1% → 10% → 50% → 100%), monitor guardrail metrics, prepare rollback plan. Phase 5 — Iterate: analyze metrics at 2-week and 6-week marks, run follow-up A/B tests.

Technical PM

API design from a PM perspective, system architecture trade-offs, technical feasibility assessment, data pipelines, and platform vs product decisions.

"How would you design the API for a payment system?"

RESTful API: POST /payments (create), GET /payments/:id (status), POST /payments/:id/refund. Idempotency key required on POST to prevent double charges. Webhook callbacks for async status updates (pending → processing → completed/failed). PCI compliance: tokenize card data, never store raw PAN. Rate limit by merchant API key. Versioning via URL prefix (/v1/) for backward compatibility.

Behavioral for PMs

PM-specific STAR answers — stakeholder management, saying no, data-driven decisions, cross-functional leadership, and handling ambiguity.

"Tell me about a time you had to say no to a stakeholder"

Situation: VP of Sales wanted a custom dashboard feature for one enterprise client. Task: Evaluate whether to build it. Action: Pulled usage data — only 3 of 200 enterprise clients would use it. Proposed a self-serve analytics export instead (10x more clients served, 1/3 the eng cost). Presented the data to VP with a clear trade-off matrix. Result: VP agreed. The export feature drove 15% higher enterprise retention across the board.