Analytics
494 bites tagged Analytics — interview questions with model answers, and 60-second explainers.
How do you visually represent statistical uncertainty in a chart?
This tests your ability to communicate statistical nuance beyond simple averages. A great answer discusses error bars (specifying CI vs. SD), then moves to richer visualizations like graded error bars or violin plots.
Explain pre-attentive attributes in data visualization
Tests your grasp of visual psychology in data viz. Define pre-attentive attributes (instantly processed visuals), give examples (color, size, shape), and explain using one to highlight outliers in a dense plot.
Feature A correlates with retention. Should we invest more?
Tests your ability to move beyond clichés to propose concrete analysis. A great answer questions the correlation, suggests cohort analysis or A/B testing, and probes for confounding variables. Red flag: just saying 'correlation isn't causation' with no plan.
How would you design a product management dashboard?
Tests your ability to structure data into a decision-making narrative. A good answer moves from a high-level summary (DAU) to trends (retention) and then actionable details (feature adoption). A red flag is simply listing charts without a narrative connection.
Bar Chart vs. Line Chart for Market Share Comparison?
Tests basic chart selection: comparing static categories vs. showing trends. A bar chart is correct for comparing discrete companies at one point in time. A line chart wrongly implies a time-series relationship. Red flag: choosing a line or pie chart.
When is a pie chart an appropriate choice for visualization?
Tests data viz principles for part-to-whole data. A good answer defines this use case, gives a clear example (market share), and lists pitfalls like too many slices or similar values. A red flag is defending them for complex data or time-series analysis.
How do you manage an event schema change?
This tests your understanding of data contracts and backward compatibility. A great answer details a phased, backward-compatible rollout (add nullable field), starting with consumers (warehouse) then producers, and mentions using a schema registry for…
Challenges of Grouping by a High-Cardinality Dimension
This tests your grasp of how data shape impacts system resources. A great answer explains that high cardinality explodes memory usage for aggregation state, increases CPU load, and hurts storage compression.
Trade-offs: Pre-aggregation vs. querying raw event data
This tests your grasp of data engineering trade-offs for analytics dashboards. A great answer contrasts pre-aggregation (fast, cheap, stale) with on-the-fly queries (slow, costly, fresh) and mentions hybrid solutions.
How do you ensure accurate counts with duplicate analytics events?
Tests your grasp of data integrity under at-least-once delivery. Explain why COUNT(*) is inflated, then propose deduplication using a unique event ID. Mention trade-offs of stateful processing. A red flag is ignoring the cost or the need for a unique ID.
Explain a star schema and its advantages for analytics
Tests your grasp of data modeling trade-offs for OLAP vs. OLTP. A good answer defines fact/dimension tables, then explains how denormalization and fewer joins improve query speed for analytics. A red flag is confusing it with a snowflake schema.
How would you diagnose a slow dashboard query?
This tests your systematic approach to performance tuning. A great answer investigates query optimization, strategic indexing/partitioning, and the data model (like star schema).
How to handle schema evolution in a CDC analytics pipeline?
This tests your ability to design resilient CDC pipelines. A strong answer outlines automated schema detection, using a flexible format like Avro, and enforcing governance with a schema registry. A red flag is proposing manual fixes for every change.
Explain data lineage and how you'd implement it
Tests your practical data governance knowledge. Define lineage (origin, transforms, movement), then outline a solution: metadata collection from services, a central store (graph DB), and a visualization tool (Amundsen/OpenLineage).
What is a data schema and why enforce it on ingestion?
This tests your grasp of data governance. Define a schema as a data blueprint. Explain that enforcement on ingestion prevents "garbage in, garbage out" by validating types and formats, ensuring data is usable for analytics.
How would you handle 10% nulls in a key column?
This tests your ability to diagnose data issues before solving. First, investigate why data is null. Then, discuss trade-offs of dropping vs. imputing with the mean or median, considering the impact on the dashboard's accuracy.
Compare a data warehouse, data lake, and lakehouse
Tests your grasp of data architectures for BI vs. ML workloads. Contrast warehouses (structured) and lakes (raw), then explain how a lakehouse adds ACID/schema features to a lake's storage. A red flag is confusing schema-on-write vs. schema-on-read.
What is data partitioning in a cloud data warehouse?
Tests your grasp of performance and cost trade-offs in data systems. A good answer defines partitioning, explains partition pruning for performance, and links it directly to reduced data scan costs.
How do you handle late-arriving data in a streaming pipeline?
Tests understanding of event time vs. processing time and the mechanisms (watermarks, triggers, allowed lateness) to ensure correctness. Answer by distinguishing time types, using event-time windowing, defining watermarks, and configuring allowed lateness.
Describe star and snowflake schemas and their trade-offs.
Tests your grasp of data warehouse design trade-offs. Define star (denormalized dimensions) and snowflake (normalized dimensions) schemas. Contrast them: star is faster for queries but uses more space; snowflake is space-efficient but requires more joins.
ETL vs. ELT: Key differences and when to use each?
This tests your understanding of modern data architecture trade-offs. A good answer explains the T vs. L order, then links ETL to structured, legacy systems and ELT to flexible, cloud-native data lakes/warehouses.
Design a client-side event batching system for a high-traffic app
This tests your grasp of frontend performance and data reliability. Outline a batching strategy (timer/size), then explain using `visibilitychange` with `navigator.sendBeacon()` to prevent data loss on unload. A red flag is suggesting synchronous XHR.
How do you approach user identity stitching across devices?
This tests your grasp of event-driven data pipelines and identity management. A strong answer outlines an identifier hierarchy, the "stitch" event (login), and a backend process for retroactively applying a canonical user ID.
Build vs. Buy: Third-Party vs. In-House Analytics
Tests your grasp of the time-vs-control trade-off. A great answer weighs speed vs. customization and total cost of ownership. Advocating for 'build' without considering the massive, ongoing maintenance cost is a major red flag.
Get Analytics bites daily.
Five a day, five minutes, offline. With quizzes so it sticks.
Open testing — you’ll join as an early tester.