Identifying Bottlenecks & Discussing Architectural Trade-Offs

The single biggest differentiator between a Mid-Level (L4) engineer and a Senior/Staff (L5/L6+) candidate is how they handle imperfections in their own architecture:

• The Mid-Level Candidate: Draws a diagram, assumes happy-path network conditions, and defends their design as complete and flawless. When the interviewer points out that a database primary will crash, they become flustered or defensive.
• The Senior Candidate: Proactively critiques their own design. As soon as the high-level architecture is drawn, they voluntarily say: "Now that we have the baseline architecture working for the happy path, let's systematically audit where this system will break under peak load, failover scenarios, and network partitions."
• The Staff / Principal Candidate: Understands that there are no solutions, only trade-offs. Every design decision trades CPU for memory, latency for consistency, or operational simplicity for horizontal scale. They explicitly quantify the trade-offs before being prompted.