Interview archetype
The Domain Specialist
Picks one hard subproblem and stays inside it for thirty minutes.
Set The Domain Specialist as your interviewer and the app will pick follow-ups in their categories and weight your rubric their way.
How they behave
- You draw a whole system. They point at one box and say "let us talk about just this."
- They go several levels deeper than the rest of the interview: data structures, exact query shapes, failure modes at the level of individual operations.
- They are not interested in breadth. Covering all five stages quickly and moving on will frustrate them.
- They usually know this subproblem extremely well, so bluffing is spotted quickly.
What a failing answer looks like under this style
- You run out of depth after two levels. You can say "we would use a cache" and "cache-aside", and then nothing.
- You bluff. This is the interviewer most likely to know more than you about their chosen area, and a confident wrong answer costs more than an admission.
- You keep trying to zoom back out to the full architecture. They chose this box on purpose.
- You describe what a technology does rather than why it fits here.
How to survive them
- Go deep willingly. Have at least three levels of detail on the mechanisms you name: what it is, how it works, what breaks.
- Say "I do not know" cleanly when you reach your limit, then reason forward from what you do know. That is a strong signal, not a weak one.
- Bring the failure modes yourself. Depth is mostly knowing how a thing fails, not how it works.
- Connect the detail back to the requirement occasionally, so the depth stays purposeful rather than trivia.
Say this
"At the next level down, the thing that makes this hard is [specific mechanism]. It fails when [precise condition], and I handle that with [technique], which costs [cost]. Below that I would be guessing, so I would want to measure rather than assert."
How they weight the rubric
Same design, graded differently. This is why the archetype changes your score.
Requirements
×0.7
Lifecycle
×1.2
Numbers
×0.9
Design
×1.5
Tradeoffs
×1.4
Defence
×1.3
They reach for:Attack consistencyKill somethingQuestion the choice
Three-question drill, in their voice
Same rule as everywhere else: you answer before you see anything.
1
Let us only talk about your cache. Walk me through what happens on a miss, in detail.
0 / 30 characters
2
Just the partitioning. How do you reshard without downtime?
0 / 30 characters
3
Only the queue consumer. What happens when it restarts mid-batch?
0 / 30 characters