TrialroundWhat could go wrong with your own idea
An interviewer liked the design, then asked what could go wrong with it. The candidate had never practiced disagreeing with themselves.
system design · follow-up
The second of those React interviews had a nasty little compliment. The design landed. Then: what could go wrong with this approach? Freeze. They had prepared to defend the idea, not to burgle it.
That question is how senior people talk after they have been paged. A design with no failure mode is a brochure. The interviewer is listening for whether you have seen a system embarrass you.
Keep three failures in your pocket
You do not need a catastrophe for every diagram. You need a habit:
- Too many updates, and the screen lies.
- A dependency that is slow, and you have no timeout.
- Two people editing the same thing, and you pretended that would not happen.
Say one of them before they ask. It makes you look like you have been awake at 2 a.m., which is unfortunately the job.
Then stop. Do not list twelve risks and forget the one you would fix this week. They stopped the code after five minutes is the version where you never got to this question because you were already typing.