There is no free lunch
Senior level signal comes from discussing tradeoffs. Every architectural choice gains something and gives up something. Naming both, and explaining why your choice fits the requirements, is what separates a memorized answer from real judgment.
Classic tradeoffs
- Consistency versus availability under network partitions.
- Latency versus throughput when batching work.
- Read speed versus write cost when denormalizing.
- Cost versus performance when adding caches and replicas.
How to frame one
- State the options you considered.
- Name the gain and the cost of each.
- Tie it to requirements so the choice is justified.
- Pick one and own the consequence.
Avoid false certainty
Saying one approach is simply best is a red flag. The interviewer knows the answer depends on context. Connect your choice to the scope and estimates you agreed on, and acknowledge when a different requirement would flip the decision.
Key idea
Treat every choice as a tradeoff, naming what it gains and gives up and tying the decision back to the agreed requirements.