Intermediate interview questions in Analytics & Metrics, page 6
Which model for forecasting with seasonality and trend?
This tests your knowledge of classical time series models. A good answer names Holt-Winters, explaining its level, trend, and seasonal components. It also discusses choosing between additive and multiplicative methods. A red flag is jumping to complex models.
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.
How would you instrument and query P95 API latency by region?
This tests white-box latency instrumentation and safe cardinality for percentile aggregation. Strong answer: emit histograms by region, query P95 with histogram_quantile or a log percentile, and keep trace IDs in logs only.
How would you measure P95 latency by geographic region?
Tests your ability to translate a business need into a concrete observability implementation. A good answer involves instrumenting the API with a histogram metric, adding a region label via GeoIP, and querying with histogram_quantile.
How would you measure P95 latency by geographic region?
Tests your ability to design a practical metrics pipeline, considering instrumentation, data types (metrics vs. logs), and aggregation. Instrument the API with a histogram metric and a region label, then query using histogram_quantile.
Describe dbt's role and how it differs from traditional ETL
Position dbt as ELT's T with lineage, tests, docs; contrast with Python ETL using external compute and Airflow only scheduling tasks.
Describe the role of dbt in a modern analytics stack
Tests your grasp of modern ELT patterns. A good answer explains how dbt uses SQL for in-warehouse transformations, enabling software engineering practices like version control and testing. A red flag is confusing dbt with a full ETL tool or an orchestrator.
Describe dbt's role in a modern analytics stack
Tests your grasp of the ELT paradigm and applying software engineering principles to data. A good answer defines dbt as the 'T' in ELT, contrasts its in-warehouse SQL approach with traditional ETL, and clarifies its relationship with orchestrators like…
Designing a warehouse model for feature adoption
Star schema with a feature-usage fact table at a defined grain, surrounded by user, feature, date, and device dimensions.
Design a Data Model for a Feature Adoption Dashboard
This tests your ability to translate a business need into a scalable star schema. A great answer defines a central fact table (e.g., fct_feature_usage) and its dimensions (dim_users, dim_features, dim_date).
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.
Explain event schemas and why schema registries matter at scale
This tests schema evolution and data contracts in distributed systems. A good answer defines schemas as contracts, explains that a registry enforces compatibility to block breaks, and lists pain like pipeline failures. Never treat schemas as optional docs.
Explain event schemas and the purpose of a schema registry
Tests your grasp of data contracts at scale. A good answer defines schemas as contracts, a registry as the enforcer of compatibility (e.g., backward/forward), and explains how this prevents 'poison pill' messages and brittle analytics.
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.
Explain cohort retention and write a pseudo-query for May signups
Tests cohort retention vs aggregate DAU and SQL self-joins for Week 1, 2, and 4 retention from May signups. Strong answers define cohorts by signup date, use datediff, and left-join activity. Red flag: using calendar week instead of relative signup date.
Explain cohort analysis and write a retention query
Tests your grasp of user behavior metrics. First, define a cohort (e.g., May signups). Then, explain why it's better than aggregate retention. Finally, outline a query grouping users by signup week and checking for activity. A red flag is a flawed query.
Explain cohort analysis for user retention and write a pseudo-query
Tests your ability to use precise metrics. A good answer defines a cohort, explains why it isolates variables better than aggregate data, outlines the calculation, and provides a clear pseudo-query.
Design a data model for feature adoption tracking
Tests dimensional modeling for high-volume events so PMs can query Feature A not B without complex SQL. A strong answer uses an event fact table plus a materialized user-feature summary. Red flag: a wide user table with boolean columns per feature.
Design a data model for tracking feature adoption
This tests your grasp of data warehouse star schemas for analytics. Outline a fact table for events and dimension tables for users and features, explaining how this structure enables fast, ad-hoc cohort analysis for a product manager.
Design a data warehouse model for tracking feature adoption
This tests your grasp of data warehousing star schemas for efficient behavioral analysis. A strong answer proposes a central events fact table linked to users, features, and time dimension tables.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles