The Broadcast Question

Concepts covered: paBroadcastJoin

When an interviewer describes joining a large table to a small one and asks why it is slow, they have handed you a pattern with a known answer. The shape is unmistakable once you have seen it: a big fact table, a small lookup or dimension, a join between them, and a complaint that it takes too long. That shape is the cue, and the cue points at one technique. Your job in the first few seconds is to recognize the shape, not to start guessing at random causes. Why the shape matters Here is why the shape matters so much. A normal join makes Spark shuffle both tables across the network so that rows with matching keys land together on the same machine. Shuffling the small table is cheap; shuffling the giant one is the expensive part, and it is usually where all the time goes. The interviewer cho

About This Interactive Section

This section is part of the The Join Problem 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.