How to Communicate System Design When You Get Stuck
System design interviews evaluate communication and trade-off analysis more than whiteboard syntax. Here is how to navigate unexpected architectural bottlenecks without panicking.
Vishal VermaCTO & Co-Founder, Dehurdle
June 10, 20264 min read
The Friction
Engineers often fail system design rounds because they go silent for 3 minutes when confronted with scale bottlenecks, or jump straight into database schemas without clarifying read/write ratios.
The Spoken Architecture Framework
Vocalize your thought process in structured layers:
01
Scoping (2 min): "Before jumping into components, let's clarify DAU, write TPS, and whether our read latency SLA is sub-100ms."
02
High-Level Diagram (5 min): "I will start with a load balancer routing to stateless API instances backed by Postgres and a Redis cache."
03
Bottleneck Deep-Dive (10 min): "At 100k writes/sec, a single Postgres instance will saturate IOPS. Here is how I evaluate sharding by UserID vs. an event-driven Kafka buffer."
What to Say When You Get Stuck
Recommended Spoken Script
"I see a potential race condition here when two users write to the same inventory row. Two approaches come to mind: distributed Redis locks or optimistic concurrency control. Let me walk through the trade-offs of both in our high-traffic scenario."
The 2-Minute Practice Drill
2-Minute Spoken Drill
The 2-Minute Practice Drill
Practice vocalizing system design trade-offs in Dehurdle's Staff Engineer Interview Rehearsal.
Follow Dehurdle on Google
Add Dehurdle to your Google Preferred Sources to see our playbooks in your AI Overviews and Google Search.