Interview archetype
The Scale Breaker
Multiplies your traffic, adds celebrity users and hot keys, kills a region.
Set The Scale Breaker as your interviewer and the app will pick follow-ups in their categories and weight your rubric their way.
How they behave
- Every time you settle on a design, they multiply something. 10x traffic. 100x one user. A region gone.
- They are looking for the specific component that breaks first, and whether you know what it is before they tell you.
- They love distributions. They will take your average and ask about the 99th percentile, then the maximum.
- They rarely care about the happy path. They are interested in your design at its limits.
What a failing answer looks like under this style
- "It scales horizontally." Some part never does, and not naming it means you have not looked.
- You designed for the average and have no answer for the tail. The average follower count tells you nothing about the account with 30 million.
- You add capacity as the answer to everything, including problems capacity does not fix, like a single hot key.
- You have no ordering. "Several things would struggle" is not an answer; they want first, second, third.
How to survive them
- Know your own bottleneck before they ask, and volunteer it. "The thing that breaks first here is X, at about Y times current load."
- Answer with an ordered list, not a single component. Failures cascade in a sequence and knowing the sequence is the skill.
- Always check the tail of any distribution you used. Whenever you say "average", ask yourself what the maximum does.
- Distinguish problems that capacity solves from problems it does not. A hot key, a lock, a single-threaded component: more machines do nothing for these.
Say this
"The first thing that breaks is [component], at roughly [N]x, because [reason]. Then [second], for a different reason. And [hot key / lock / single-threaded part] is not a capacity problem at all. More machines do nothing for it, so it needs [specific technique]."
How they weight the rubric
Same design, graded differently. This is why the archetype changes your score.
Requirements
×0.8
Lifecycle
×1.1
Numbers
×1.6
Design
×1.4
Tradeoffs
×1.0
Defence
×1.4
They reach for:Break the scaleKill somethingAttack consistency
Three-question drill, in their voice
Same rule as everywhere else: you answer before you see anything.
1
Traffic is 100x tomorrow. Not 10x. What is the first, second and third thing to break?
0 / 30 characters
2
One key is now 95% of your traffic. Sharding does not help. What do you do?
0 / 30 characters
3
Your average request touches 3 shards. What is your p99 when you fan out to 100?
0 / 30 characters