Analytics
494 bites tagged Analytics — interview questions with model answers, and 60-second explainers.
Explain event schemas and the purpose of a schema registry
This tests your grasp of data governance in event-driven systems. A good answer defines a schema as a contract, a registry as the enforcer, and then details specific downstream failures like broken pipelines and bad analytics. A red flag is being too vague.
How would you design a data model for a feature adoption dashboard?
Tests applying dimensional modeling to a business need. A good answer defines a central fact table (e.g., `feature_usage`) and related dimensions (`user`, `feature`, `date`). A red flag is designing a transactional model or being too vague about the schema.
Track a user event from frontend code to a BI tool
Tests your understanding of the modern data stack. A good answer traces the event from frontend capture, through an ingestion pipeline, into a data warehouse, and finally to a BI tool for analysis. A red flag is describing only one part of the journey.
Prove API Latency Affects User Engagement
This tests your ability to design a controlled experiment for a backend attribute. A great answer outlines an A/B test that artificially adds latency for a treatment group, details the necessary logging with shared IDs, and explains how to join and analyze…
Design a real-time anomaly detection system for 'add to cart' events
Tests real-time data pipeline design and nuanced anomaly detection. A good answer outlines ingestion (Kinesis), processing (Lambda/Flink), seasonal modeling for 'a drop', and alerting (SNS).
How would you capture and persist UTM parameters for attribution?
Tests your grasp of state management and data persistence for analytics. A good answer covers capturing UTMs with JS, persisting them in a cookie, and associating them with a user record on the server during a conversion event.
Describe the client-side event for an 'Add to Cart' button
This tests your ability to design analytics events for future analysis. Name a standard event like `add_to_cart` and list item parameters (`item_id`, `price`, `quantity`).
Forecasting inventory with trend and weekly seasonality?
This tests mapping a business problem to a statistical tool. A good answer names Holt-Winters, explains its level, trend, and seasonal components, and discusses additive vs. multiplicative seasonality.
Explain stationarity in a time series
This tests your grasp of core time series modeling assumptions. A strong answer defines stationarity (constant mean/variance), explains its importance for ARIMA (stable patterns), and names a test (ADF) and a fix (differencing).
How would you measure a sales forecast model's accuracy?
This tests your ability to connect statistical metrics to business impact. A great answer defines MAE (linear error cost) and RMSE (penalizes large errors), explains the choice depends on business context, and stresses using a test set.
Describe EDA for a 3-year daily user sign-up dataset.
Tests your structured approach to time series EDA. A good answer identifies trend, seasonality, and anomalies before modeling. A red flag is jumping to forecasting models or only mentioning the overall average growth, ignoring cyclical patterns.
Primary vs. Guardrail Metrics in Experiments
This tests if you can balance improving a key metric with not harming the user experience. Define primary (the goal) and guardrail (don't harm) metrics. Give an example where a guardrail regression (e.g., latency) blocks a feature ship.
Handling the novelty effect in experimentation
This tests your grasp of second-order effects in A/B testing. A great answer defines the novelty effect, explains how it inflates initial metrics, and suggests mitigating it by running tests longer or segmenting by user tenure. A red flag is ignoring it.
Explain Simpson's Paradox with a user engagement example
This tests your understanding of statistical pitfalls in A/B testing. A good answer defines the paradox, gives an example where a feature fails in aggregate but wins in every segment, and attributes it to a confounding variable.
How to Statistically Test a 10% DAU Drop?
Tests your knowledge of hypothesis testing. A good answer outlines the steps: state a null hypothesis, choose a test (e.g., Z-test), calculate a p-value, and compare it to a significance level (alpha).
Explain the difference between correlation and causation
Tests if you can avoid statistical fallacies. First, define correlation (association) and causation (cause-effect). Then, explain the difference via a confounding variable. A red flag is giving an example where one metric actually could cause the other.
Mean vs. Median for API Response Times?
Tests if you know latency data has outliers. A good answer chooses median because it's robust to extremes. Explain that mean gets skewed by a few slow requests (e.g., GC pauses), hiding the typical user experience.
How would you architect a fast, multi-dimensional analytics dashboard?
This tests your grasp of analytics architectures and trade-offs between pre-computation and real-time querying. A great answer clarifies needs, then proposes a hybrid model using an OLAP cube for core metrics and a columnar store for ad-hoc queries.
How would you validate a PM's claim about feature success?
This tests your grasp of causal inference vs. correlation. A great answer acknowledges self-selection bias, proposes a quasi-experimental method like Propensity Score Matching to create a synthetic control group, and then compares outcomes for the matched…
An A/B test has imbalanced traffic. What do you do?
This tests your ability to spot confounding variables and Simpson's Paradox. A good answer first invalidates the aggregate result, then proposes segmenting by device to salvage insights, and finally investigates the root cause.
Generate a monthly cohort retention table from user events
This tests your ability to translate a business metric into a multi-step SQL query. A great answer defines cohorts by first activity, maps subsequent activity to period indices, counts distinct users, and pivots the result.
Average latency is up, but p99 is flat. Why?
This tests your grasp of latency distributions. Hypothesize that a large group of typical requests slowed, pulling up the average but not crossing the p99 threshold. Segment by endpoint or customer to find the cohort.
Is 20% higher retention from Feature X causal or correlational?
This tests your ability to distinguish correlation from causation. A great answer questions the data, identifies confounding variables (e.g., power users), and proposes a randomized A/B test as the gold standard to prove causality.
DAU dropped 10%. What user segments do you investigate first?
Tests your systematic problem-solving. First, clarify the metric and timeline. Then, segment by platform, geography, and user tenure (new vs. returning). A red flag is jumping to external causes before ruling out internal issues like a bad deployment.
Get Analytics bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.