Reviewed by Aditya Kumar · Last reviewed 2026-03-24
**Architectural Logic**: Star vs snowflake is a trade-off between join complexity and storage/normalization. **Star**: One fact table; denormalized dimensions; fewer joins. **Snowflake**: Normalized dimensions (dim→sub-dim); more joins, less redundancy. **Why Star for Swiggy**:...
This medium-level SQL question appears frequently in data engineering interviews at companies like Swiggy. While less common, it tests deeper understanding that distinguishes strong candidates. Mastering the underlying concepts (join, snowflake) will help you answer variations of this question confidently.
Break this problem into components. Identify the core trade-offs involved, then walk the interviewer through your reasoning step by step. Demonstrate awareness of edge cases and production considerations - this is what separates good answers from great ones.
Architectural Logic: Star vs snowflake is a trade-off between join complexity and storage/normalization. Star: One fact table; denormalized dimensions; fewer joins. Snowflake: Normalized dimensions (dim→sub-dim); more joins, less redundancy. Why Star for Swiggy: Food delivery reporting (orders, delivery, restaurants, users) requires fast, concurrent dashboards. Star schema minimizes join depth—critical for BI tools and sub-second response. Snowflake adds joins (e.g., dim_restaurant→dim_chain→dim_brand); every report pays that cost. Scalability: At Swiggy's scale, query concurrency matters more than storage savings. Star's denormalization improves cache hit rates. Cost: Simpler joins = less compute per query. Recommendation: Star for reporting; consider snowflake only if dimension hierarchies are deep and storage is a constraint.
Red Flag: Defaulting to snowflake 'for normalization' in analytics—often wrong. Pro-Move: Quantify join count and row amplification; for Swiggy, star wins on latency and concurrency.
Some links below are affiliate links. If you buy through them we may earn a small commission at no extra cost to you — it helps keep DataEngPrep free.
According to DataEngPrep.tech, this is one of the most frequently asked SQL interview questions, reported at 1 company. DataEngPrep.tech maintains an editor-reviewed database of 1,863 data engineering interview questions across 7 categories.