**STAR**: **Situation**: Nightly job took 6 hr; SLA 2 hr. **Task**: Optimize. **Action**: Profiled—found full scan and skew. Partition pruning; broadcast join for dimension; salting for skew. **Result**: 1.5 hr; 4x improvement....
Pro-Move: 'Spark UI showed 1 partition at 4hr—salted the key, added pruning; 6hr to 90min; documented in runbook.' Red Flag: We added more resources—optimization, not scaling.
This medium-level System Design/Architecture 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, partition) 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.
STAR: Situation: Nightly job took 6 hr; SLA 2 hr. Task: Optimize. Action: Profiled—found full scan and skew. Partition pruning; broadcast join for dimension; salting for skew. Result: 1.5 hr; 4x improvement. Quantify: Before/after; techniques.
This answer is partially locked
Unlock the full expert answer with code examples and trade-offs
Practice real interviews with AI feedback, track progress, and get interview-ready faster.
Pro starts at $24/mo - cancel anytime
Paste your answer and get instant AI feedback with a FAANG-level improved version.
Analyze My Answer — FreeAccording to DataEngPrep.tech, this is one of the most frequently asked System Design/Architecture interview questions, reported at 1 company. DataEngPrep.tech maintains a curated database of 1,863+ real data engineering interview questions across 7 categories, verified by industry professionals.