Skip to content
Tech Interview Prep home
Technical interview guide

Metrics, KPIs & North Star Frameworks

Choosing the metric that actually reflects whether the product is succeeding, and avoiding vanity metrics.

Read
31 min
Practice MCQs
25
Interview QA
25
Edition
v3
Editorial status
Reviewed

Scope: Google HEART, Scrum.org Evidence-Based Management 2024, DORA metrics guidance, GOV.UK Service Manual, NIST statistical and privacy guidance, and FTC dark-pattern guidance current 2026-08-31.

Interview QA

Treat each question like a live interview question: answer out loud first (structure, assumptions, tradeoffs), then open the model answer to spot gaps and rehearse a tighter follow-up.

Curated: · Written: · Reviewed:

QA-1

Choose a North Star Metric for a collaboration product.

QA-2

Define activation for a new product.

QA-3

Build a metric tree for reducing customer churn.

QA-4

Diagnose a rising conversion rate with falling revenue.

QA-5

Set KPIs for a low-frequency government service.

QA-6

Design guardrails for an engagement experiment.

QA-7

Investigate a sudden KPI jump after a release.

QA-8

Create a metric contract for weekly active teams.

QA-9

Evaluate whether feature adoption predicts retention.

QA-10

When targeting aggressive growth on a primary North Star metric, how do you select and calibrate guardrail metrics to prevent system degradation or metric gaming?

QA-11

Set a target for task completion rate.

QA-12

How do you decompose a top-line North Star metric into leading input metrics for product squads?

QA-13

Plan an A/B test for a checkout change.

QA-14

Measure a platform product used by internal teams.

QA-15

Build a retention metric for a seasonal product.

QA-16

Audit a North Star for gaming risk.

QA-17

Handle conflicting definitions of active user.

QA-18

Decide what to do with a statistically significant tiny lift.

QA-19

Design metrics for an incident-reduction initiative.

QA-20

Measure accessibility improvement.

QA-21

Assess telemetry quality before a launch decision.

QA-22

Retire a vanity metric from executive reporting.

QA-23

Create privacy-conscious product analytics.

QA-24

Evaluate metrics after a product strategy change.

QA-25

Test whether a metrics program is production-ready.