##### Scenario A key revenue metric on Coinbase's dashboard suddenly declines—for example, weekly trading-fee revenue drops noticeably week-over-week. You are the data scientist asked to investigate. ##### Question Describe a structured, step-by-step approach to investigate and diagnose the root cause of the revenue drop. In your answer, address each of the following: 1. **Triage and validation** — How would you confirm the drop is real (not a measurement/data-quality artifact) and pinpoint exactly when it began? 2. **Revenue decomposition** — How would you decompose revenue into its underlying drivers (e.g., volume × take rate, or traffic × conversion × price) and quantify which driver moved the most? Show the math. 3. **Priority metrics** — Which metrics and KPIs would you inspect first, and why? 4. **Data cuts / segmentation** — Which segments and dimensions would you slice by to localize the drop, and how do they help you avoid Simpson's paradox? 5. **Funnel diagnostics** — How would you use the trade and funding funnels to find the failing step? 6. **Releases & experiments audit** — How would you check whether a recent deploy, config/fee change, or running A/B experiment caused the drop? 7. **External / market factors** — How would you separate macro/market-driven effects (e.g., crypto volatility) from internal product/ops causes? 8. **Hypothesis testing & attribution** — How would you turn observations into testable hypotheses and quantify each cause's contribution (with methods like ITS, diff-in-differences, synthetic control)? 9. **Action & monitoring** — How would you communicate findings, choose remediations, and add monitoring to prevent recurrence? ##### Hints Think in terms of decomposition (volume × take rate; or sessions × conversion × AOV), segmentation (asset, geo, platform, cohort, payment rail), funnels, recent changes/experiments, seasonality, and external market factors. Remember this is a crypto exchange: trading volume is highly sensitive to price volatility.

This interview question evaluates metric design, causal reasoning, experiment setup, diagnostics, SQL/statistical checks, and recommendations in a realistic interview setting. A strong answer for Diagnose a Sudden Revenue Decline: Analyses, Metrics, and Root-Cause Tests states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

How do I approach Analytics & Experimentation interview questions?

Analytics & Experimentation questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master analytics & experimentation interviews.

What difficulty level is this interview question?

This is a medium difficulty Analytics & Experimentation question, commonly asked during Technical Screen rounds at Coinbase.

What role is this question designed for?

This question is commonly asked for Data Scientist candidates at Coinbase during technical interviews.

Diagnose a Sudden Revenue Decline: Analyses, Metrics, and Root-Cause Tests

Scenario

A key revenue metric on Coinbase's dashboard suddenly declines—for example, weekly trading-fee revenue drops noticeably week-over-week. You are the data scientist asked to investigate.

Question

Describe a structured, step-by-step approach to investigate and diagnose the root cause of the revenue drop. In your answer, address each of the following:

Triage and validation — How would you confirm the drop is real (not a measurement/data-quality artifact) and pinpoint exactly when it began?
Revenue decomposition — How would you decompose revenue into its underlying drivers (e.g., volume × take rate, or traffic × conversion × price) and quantify which driver moved the most? Show the math.
Priority metrics — Which metrics and KPIs would you inspect first, and why?
Data cuts / segmentation — Which segments and dimensions would you slice by to localize the drop, and how do they help you avoid Simpson's paradox?
Funnel diagnostics — How would you use the trade and funding funnels to find the failing step?
Releases & experiments audit — How would you check whether a recent deploy, config/fee change, or running A/B experiment caused the drop?
External / market factors — How would you separate macro/market-driven effects (e.g., crypto volatility) from internal product/ops causes?
Hypothesis testing & attribution — How would you turn observations into testable hypotheses and quantify each cause's contribution (with methods like ITS, diff-in-differences, synthetic control)?
Action & monitoring — How would you communicate findings, choose remediations, and add monitoring to prevent recurrence?

Hints

Think in terms of decomposition (volume × take rate; or sessions × conversion × AOV), segmentation (asset, geo, platform, cohort, payment rail), funnels, recent changes/experiments, seasonality, and external market factors. Remember this is a crypto exchange: trading volume is highly sensitive to price volatility.

Constraints & Assumptions

Preserve the scope, facts, inputs, and requested outputs from the prompt above.
If the prompt leaves a detail unspecified, state a reasonable assumption before relying on it.
Keep the answer interview-ready: concise enough to present, but concrete enough to implement or evaluate.

Clarifying Questions to Ask

Clarify the business objective, unit of analysis, time window, exposure definition, and primary metric.
State assumptions about instrumentation, randomization, sample size, and data quality.
Separate descriptive analysis from causal claims.

What a Strong Answer Covers

A metric framework with primary, guardrail, and diagnostic metrics.
A credible analysis or experiment design with clear assumptions and bias checks.
SQL/statistical logic for segmentation, variance, confidence, and data validation where relevant.
An actionable recommendation that explains trade-offs and next steps.

Follow-up Questions

What sanity checks would you run before trusting the result?
How would you handle novelty effects, seasonality, or selection bias?
What decision would you make if metrics disagree?