10 Data Analyst Metrics Interview Questions and Answers

Short answer: A good metric is measurable, comparable, understandable and hard to game, and above all actionable: it can drive a decision. A KPI is the same kind of metric but tied to a goal and a target value for a period; a KPI is a subset of metrics, not a synonym.

In depth:

1. Actionable, not vanity — a metric should change someone's decision. If the number goes up but nobody knows what to do, it's a vanity metric.
2. Comparability — prefer rates and ratios (conversion, retention %) over raw counts: they compare across periods and segments.
3. Hard to game — ask "how could this be inflated without creating value?". "Clicks" are easy to game; "activated users" are harder.
4. A precise definition — one numerator, one denominator, a fixed window and filters, or two teams will count it differently.

⚠️ Common mistake: calling everything a KPI. KPIs are the 3–5 metrics a team is actually judged on; the rest are diagnostic metrics.

Short answer: A North Star is a single metric that captures the value users get and that a team moves over the long run. A good North Star correlates with revenue but measures delivered value rather than money directly; input metrics are the levers the team controls that ladder up to it.

In depth:

1. Captures value, not activity — e.g. "weekly active teams that sent a message" (Slack), not "signups".
2. Leads revenue — it rises before the money, so it works as a steering wheel.
3. Decomposes into inputs — the North Star is a function of a few controllable levers; teams get goals on those levers.

            NORTH STAR
   (weekly active teams)
        ▲          ▲          ▲
        │          │          │
     new        activation  retention
    teams   →  (aha moment) →   W4
     ▲            ▲             ▲
  traffic     onboarding   engagement

Each lower level is an input owned by a specific team; together they roll up mathematically to the top.

⚠️ Common mistake: picking a North Star equal to revenue or total signups. That is a lagging total you can't act on directly, and it hides whether the product is actually creating value.

Short answer: DAU/WAU/MAU are the unique active users in a day/week/month. The DAU/MAU ratio is "stickiness": the share of monthly users present on an average day; ~0.2 is normal, >0.5 means a daily-habit product. It all rests on the definition of "active": shift it and the numbers move without the product changing.

In depth:

1. DAU/MAU = stickiness — roughly "how many days a month a user returns": 0.2 ≈ 6 days out of 30.
2. The windows overlap — these are unique users, so DAU does not sum into MAU.
3. "Active" is a choice — opened the app, or did a core action? A push that surfaced a screen is not value.

-- Stickiness for the month: average DAU / MAU
SELECT
  AVG(dau) / NULLIF(mau, 0) AS stickiness
FROM (
  SELECT day,
         COUNT(DISTINCT user_id) AS dau,
         COUNT(DISTINCT user_id) OVER () AS mau  -- over the month window
  FROM events
  WHERE action = 'core_action'      -- definition of 'active'
    AND day >= CURRENT_DATE - 30
  GROUP BY day
) d;

⚠️ Common mistake: counting a bare app launch as "active". That lets notifications and splash screens inflate DAU; anchor activity to a core value action.

Short answer: Retention is the share of a cohort that returns N periods after their first action; churn is the inverse (1 − retention), the share that left. A retention curve usually drops steeply, then flattens into a plateau — the plateau height signals product-market fit. Cohorts beat aggregates because aggregates mix old and new users and hide a worsening retention trend.

In depth:

1. Retention vs churn — two views of one thing: W4 retention = 35% ⇒ churn = 65% over 4 weeks. Don't confuse periodic vs cumulative.
2. The curve's shape beats a point — does it fall and plateau (good) or decay to zero (no PMF)?
3. A cohort = users grouped by start date — track each along its own age axis, not the calendar.

Cohort retention table (%)
Cohort  │ W0   W1   W2   W3   W4
────────┼────────────────────────
Jan     │ 100   48   39   36   35   ← plateau ≈ 35%
Feb     │ 100   45   37   34   33
Mar     │ 100   38   28   24   22   ← retention falling!

Aggregate DAU could have risen the whole time on marketing spend, masking the March cohort's decay.

⚠️ Common mistake: judging health by total active-user growth. Rising marketing hides falling retention — compare cohorts at the same age.

Short answer: A funnel is a sequence of steps toward a goal; at each step some users drop off. Step conversion is the share moving from one step to the next; overall conversion is the share completing the whole path — the product of all step rates. Find the biggest drop-off by the largest relative fall at a step, not by absolute counts.

In depth:

1. Step vs overall — overall = step₁ × step₂ × … Four individually-90% steps still give 0.9⁴ ≈ 66% overall.
2. Where to fix — target the step with the worst step conversion: that's the biggest upside.
3. Fix a window and order — over what timeframe, and is strict step order required; otherwise conversion is ambiguous.

Checkout funnel (step % → next step)
View       ████████████████████ 10,000
  ↓ 40%
Add-to-cart ████████          4,000
  ↓ 75%
Checkout   ██████             3,000
  ↓ 30%  ◄── biggest drop-off
Paid       ██                    900
Overall: 900 / 10,000 = 9%

⚠️ Common mistake: averaging step rates or chasing absolute counts. The biggest relative drop (here 30% at payment) is where the growth is hidden.

Short answer: First I check whether it's a real drop or a data defect, then I segment to localize it, then I separate internal causes (a release, an experiment) from external ones (a holiday, a down partner, seasonality). The goal is to narrow from "everything fell" to "segment X fell because of Y".

In depth:

1. Real or artifact? — did the logger/ETL break, are there duplicates, did the metric definition shift, is the period's data complete.
2. Segment by dimensions — platform, app version, geo, new vs returning, channel. A sharp cliff in one slice = a local cause.
3. Internal vs external — does it line up with a deploy/flag/A-B; external means a holiday, a payment-partner outage, a competitor launch.

Metric −15%
├─ Data intact? ──no──► fix the pipeline (false alarm)
│        └─yes
├─ One segment? ─yes──► iOS v4.2 → release regression
│        └─ all segments
└─ Coincides with a release? ─yes─► roll back
         └─no──► external: payment provider outage

⚠️ Common mistake: jumping to product hypotheses before ruling out broken instrumentation. Half of "crashes" are broken tracking or incomplete data.

Short answer: An average squeezes a heterogeneous audience into one number and hides differences between segments — sometimes to the point of Simpson's paradox, where the overall trend is the opposite of every group's trend. Segmenting by cohort, platform, geo, new vs returning shows who is actually moving the metric.

In depth:

1. The mean masks spread — a flat overall number can hide a rising and a falling segment cancelling out.
2. Simpson's paradox — a shift in segment mix flips the overall result even when each segment improves.
3. Useful slices — new vs returning, platform, geo/language, acquisition channel, plan.

Overall conversion "dropped" though no segment got worse — only the mix shifted. Without the slice the conclusion would be wrong.

⚠️ Common mistake: reporting one averaged number and deciding on it. Always ask "average of what?" and slice into segments before concluding.

Short answer: CAC is the cost to acquire one paying customer; LTV is the total margin profit from a customer over their lifetime. A healthy benchmark is LTV:CAC ≈ 3:1 with a payback period ≤ 12 months (for SaaS). Below 1:1 you lose money on every customer; far above 3:1 you may be under-investing in growth.

In depth:

1. CAC = all sales+marketing spend / new customers in the period (not per lead).
2. LTV = ARPU × gross margin × average lifetime (or ARPU×margin / churn rate). Use margin, not revenue.
3. Payback = CAC / (monthly revenue per customer × margin): how many months until a customer repays their acquisition.
4. The ratio = LTV / CAC: the single health gauge of unit economics.

⚠️ Common mistake: computing LTV from revenue rather than gross margin, and ignoring payback. A pretty 4:1 is useless if payback is 24 months and you lack the cash to bridge it.

Short answer: A vanity metric rises pleasantly but doesn't change decisions (cumulative signups, page views); an actionable one is tied to a decision and controllable (activation, conversion, retention). A guardrail is a protective metric alongside the goal: optimizing one can break another, and the guardrail stops you "winning" by doing harm.

In depth:

1. Vanity only goes up — cumulative counters never fall, so they're useless for decisions. Use rates and fresh cohorts.
2. Actionable = decision + control — it's clear what to do on a rise/fall and which team owns it.
3. Goal + guardrail — move the goal metric while holding the guardrail no worse than a threshold.

⚠️ Common mistake: optimizing the goal metric with no guardrail. You can juice clicks with clickbait and tank trust — the metric rises while the product erodes.

Short answer: A lagging indicator measures an outcome that already happened (revenue, quarterly churn) — accurate but late and hard to steer. A leading indicator measures early behavior that predicts the outcome (activation, week-1 engagement) — you can act on it now. An analyst needs both: leading to steer, lagging to confirm.

In depth:

1. Lagging = result — it reliably closes the books, but you learn it when it's too late to change.
2. Leading = early signal — steerable and predictive, but you must validate the link to the outcome in the data, or you chase noise.
3. Pair lever → outcome — pick a leading metric that statistically predicts the lagging one you care about.

⚠️ Common mistake: steering the product only by lagging metrics like revenue. By the time the quarterly total falls, the cause occurred weeks ago — watch the leading signals.