Drawing Effective Architecture Diagrams on Whiteboards

A system design whiteboard diagram is your primary communication interface with the interviewer. Interviewers evaluate hundreds of candidates every year; messy, unstructured diagrams with crisscrossing lines, unlabelled boxes, and floating arrows instantly signal cognitive disorder.

The Golden Rules of Visual Architecture:

1. Flow Directionality (Left-to-Right or Top-to-Bottom): Place traffic origin (Clients, Mobile, Web) on the far left or top, intermediate processing tiers in the center, and persistent storage / async message brokers on the far right or bottom.
2. Strict Layered Separation: Group components by architectural tier (Edge Tier → Stateless App Fleet → In-Memory Cache → Relational / Document Persistence → Asynchronous Event Pipeline).
3. No Unlabeled Arrows: Every line connecting two boxes must specify the network protocol (HTTPS, gRPC, WebSocket, TCP) and the action / payload (e.g., POST /api/v1/posts, gRPC getUserProfile, Kafka produce(event)).
4. Visual Distinction for Async Paths: Use dashed lines (-.->) or distinct notations for asynchronous background workflows (Kafka workers, CDC pipelines, email dispatchers) versus synchronous request-response cycles.