**Causes**: Uneven key distribution. Null, default, or popular keys (e.g., tenant_id=0, country=US) dominate.
**Solutions**: (1) **Salting**—add random suffix; distribute; merge. (2) **Two-phase aggregate**—partial agg, then final. (3) **AQE skew join**—Spark 3.x splits large partitions. (4) **Filter skewed keys**—process separately; union. (5) **Increase shuffle partitions**—marginal; doesn't fix severe skew.
**Why It Matters**: One task runs 10x longer; stage waits for straggler....
The complete answer continues with detailed implementation patterns, architectural trade-offs, and production-grade considerations. It covers performance optimization strategies, common pitfalls to avoid, and real-world examples from companies like PWC. The answer also includes follow-up discussion points that interviewers commonly explore.
Continue Reading the Full Answer
Unlock the complete expert answer with code examples, trade-offs, and pro tips - plus 1,863+ more.
Or upgrade to Platform Pro - $39
Engineers who used these answers got offers at
AmazonDatabricksSnowflakeGoogleMeta
According to DataEngPrep.tech, this is one of the most frequently asked Spark/Big Data 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.