Designing a Conformed Dimension

Concepts covered: dmStarSchema

The interviewer will ask you to design a dimension that serves multiple fact tables. The trap: candidates over-stuff the dimension with domain-specific attributes that create unnecessary coupling. The signal they are looking for is whether you know what belongs in the conformed core versus what belongs in an extension. The Date Dimension: The Example Every Interviewer Expects Your conformance answer: 'Every fact table references the same dim_date via date_sk. When I GROUP BY dim_date.quarter, I get the same quarter definition whether I am querying sales, returns, or marketing. That is conformance in action: one definition, shared everywhere.' Say 'one definition, shared everywhere.' That is the sentence the interviewer is listening for. What Belongs in the Conformed Core vs the Extension Y

About This Interactive Section

This section is part of the Conformed and Role-Playing Dimensions: Advanced lesson on DataDriven, a free data engineering interview prep platform. Each section includes explanations, worked examples, and hands-on code challenges that execute in real time. SQL queries run against a live database. Python runs in a sandboxed Docker container. Data modeling problems validate against interactive schema canvases. All content is framed around what data engineering interviewers actually test at companies like Meta, Google, Amazon, Netflix, Stripe, and Databricks.

How DataDriven Lessons Work

DataDriven combines four interview rounds (SQL, Python, Data Modeling, Pipeline Architecture) with adaptive difficulty and spaced repetition. Easy problems get harder as you improve. Weak concepts resurface until you master them. Your readiness score tracks progress across every topic interviewers test. Every lesson section ends with problems you solve by writing and running real code, not by picking multiple-choice answers.