Whiteboard design is the in-person variant of the system design round, with one critical difference: you must draw clearly while you talk and think. About 14% of onsite Data Engineer loops still include a physical whiteboard component (down from 30% pre-2020 but stable since), and the format is back at FAANG companies for senior roles. Even virtual whiteboards (Excalidraw, Miro, Google Drawings) test the same skill. This page is one of eight rounds in the the full data engineer interview playbook.
Interviewers do not grade the prettiness of your diagram, but they do grade legibility and consistency. Use the conventions below and your diagram will read like an architecture, not a sketch.
| Element | Shape | Common Examples |
|---|---|---|
| Stateless compute | Rectangle | API service, Spark job, Lambda |
| Stateful compute | Rectangle with thicker border | Flink job, stream processor |
| Object storage | Cylinder | S3, GCS, Azure Blob |
| Database / warehouse | Cylinder with horizontal lines | Postgres, Snowflake, BigQuery, Redshift |
| Message queue / stream | Long thin rectangle | Kafka topic, Kinesis stream, SQS queue |
| Cache | Small cylinder | Redis, Memcached |
| External system | Cloud shape or dashed rectangle | Stripe API, third-party data feed |
| Data flow | Solid arrow with format label | JSON, Parquet, Avro, Protobuf |
| Control flow | Dashed arrow | Trigger, schedule, callback |
| Failure path | Red or labeled arrow | DLQ, retry, alert |
Every data architecture has 7 component slots. Not every problem needs all 7, but listing them helps you remember what to consider before drawing.
The physical mechanics matter. Candidates who fumble with the marker, write upside down, or run out of space halfway through lose points even when their architecture is right. Three tactics that prevent this:
Plan the layout first. Spend 30 seconds touching the corners of the board with the marker cap, deciding where the source goes (top-left), where the consumer goes (bottom-right), and roughly where the 5 to 7 components in the middle will sit. This prevents the “ran out of space” failure mode.
Write component names first, draw boxes around them after. This forces you to use only as much space as the name needs, which prevents the “huge box, tiny label” mess that hard-to-read whiteboards become.
Color code if multiple markers are available. Black for the main flow, blue for monitoring or control flow, red for failure paths. Even on a virtual whiteboard, a 3-color palette dramatically improves legibility.
How a real candidate drew an attribution pipeline at a major ad tech company in 2025. The sequence below is what got them the L5 offer.
Whiteboard design is the format under which data pipeline system design interview prep is conducted in person. The reasoning is identical; the medium is the constraint. The schema sketches you draw here borrow from schema design interview walkthrough, and the cloud-service references are deeper if you've prepped AWS Data Engineer interview prep or Google Cloud Data Engineer interview prep.
Companies most likely to use a physical whiteboard: Netflix's onsite design rounds are still whiteboard-first, Airbnb uses Excalidraw for virtual loops, and most FAANG onsites at L5+. If you're prepping for L6 / staff Data Engineer interview prep, expect at least one whiteboard round.
Run system design mock interviews against real prompts. Get feedback on your framework, your trade-offs, and your failure-mode reasoning.
Start the Design Mock Interview30+ design problems with worked architectures and trade-off analysis.
Architecture-level questions with reference designs.
Pillar guide covering every round in the Data Engineer loop, end to end.
Window functions, gap-and-island, and the patterns interviewers test in 95% of Data Engineer loops.
JSON flattening, sessionization, and vanilla-Python data wrangling in the Data Engineer coding round.
Star schema, SCD Type 2, fact-table grain, and how to defend a model against pushback.
Pipeline architecture, exactly-once semantics, and the framing that gets you to L5.
STAR-D answers tailored to data engineering, with example responses for impact and conflict.
What graders look for in a 4 to 8 hour Data Engineer take-home, with a rubric breakdown.
Continue your prep
50+ guides covering every round, company, role, and technology in the data engineer interview loop. Grounded in 2,817 verified interview reports across 929 companies, collected from real candidates.