InterviewStack.io LogoInterviewStack.io

Data Warehouse and Dimensional Modeling Questions

Design and model scalable analytical data systems using dimensional modeling principles and data warehouse architecture patterns. Core concepts include fact and dimension tables, defining and enforcing grain, surrogate keys, degenerate and role playing dimensions, conformed dimensions, and handling slowly changing dimensions including Type One, Type Two, and Type Three. Understand schema choices and trade offs such as star schema versus snowflake schema, normalization versus denormalization, and fact table types including transactional, periodic snapshot, and accumulating snapshot. Apply design decisions to meet query patterns and performance goals by considering partitioning, indexing, compression, columnar storage, and aggregation strategies. Be able to design schemas for different business domains, reason about data integration and consistency, and optimize for common analytical workloads and reporting requirements.

MediumSystem Design
88 practiced
Design an accumulating snapshot fact table to track an order fulfillment lifecycle with stages: order_placed, picked, packed, shipped, delivered. Define the grain, recommended schema (timestamp columns for each stage), measures, and explain how to handle updates for stages that occur out of order, retries, or stage rollback. Provide example queries to compute average time from placed to shipped.
EasyTechnical
75 practiced
Explain role-playing dimensions and provide a clear example using a date dimension with fields such as order_date, ship_date, and delivery_date. Describe the implementation approaches (aliasing the same date table vs duplicating attributes in the fact table) and trade-offs in query clarity, storage, and ETL simplicity.
EasyTechnical
80 practiced
Define fact table and dimension table in the context of dimensional modeling. Using a concrete e-commerce example (orders, customers, products), identify which entities are facts and which are dimensions, explain what measures belong in the fact table versus attributes in dimensions, and describe how slow-changing customer attributes should be represented.
MediumTechnical
76 practiced
Describe partitioning strategies for large fact tables: time-range partitions, list partitions, hash partitions, and composite (multi-column) partitions. For each strategy explain how it affects partition pruning, maintenance (e.g., compaction/vacuum), query performance, and examples of workloads where composite partitioning is preferable.
HardSystem Design
85 practiced
Design retention and cold-archive policies to satisfy 7-year regulatory retention of historical fact data while keeping essential analytics performant. Describe hot/warm/cold tiers, compaction and snapshotting schedules, query routing to archived partitions, and cost/latency trade-offs for retrieving archived records for audits or model retraining.

Unlock Full Question Bank

Get access to hundreds of Data Warehouse and Dimensional Modeling interview questions and detailed answers.

Sign in to Continue

Join thousands of developers preparing for their dream job.