Interview archetype
The Scope Shifter
Changes the requirements halfway through, on purpose.
Set The Scope Shifter as your interviewer and the app will pick follow-ups in their categories and weight your rubric their way.
How they behave
- Twenty minutes into a clean design, they add a requirement that invalidates part of it.
- They are testing adaptability and whether your design has joints, or whether one change means starting over.
- They often change the requirement to the thing you explicitly scoped out in Stage 1.
- They watch how you react emotionally as much as technically. Visible frustration is a signal to them.
What a failing answer looks like under this style
- You start over. Most scope changes affect one part of a design, and rebuilding everything shows you cannot see the boundaries.
- You claim it changes nothing. It usually changes something, and pretending otherwise means you have not thought it through.
- You get visibly annoyed. In a real project, requirements change often; this is a preview of working with you.
- You bolt it on without saying what you would have done differently on day one.
How to survive them
- Say what stays first. "The ingestion path and the storage layer are unaffected" is reassuring and usually true.
- Then say precisely what changes, and how much work it is. Be honest when the answer is "a lot".
- Then say what you would have done differently on day one knowing this. That is the reflective answer they are after.
- Treat the change as normal. "That is a fair requirement, here is what it costs" is the right tone.
Say this
"What stays the same is [components], which is most of it. What changes is [specific part], and that is roughly [effort]. And knowing this from the start, I would have [decision], because retrofitting it is the expensive bit."
How they weight the rubric
Same design, graded differently. This is why the archetype changes your score.
Requirements
×1.5
Lifecycle
×1.0
Numbers
×0.8
Design
×1.3
Tradeoffs
×1.3
Defence
×1.2
They reach for:Change the scopeQuestion the choiceBreak the scale
Three-question drill, in their voice
Same rule as everywhere else: you answer before you see anything.
1
Everything you designed is single-region. Now it has to be multi-region. Go.
0 / 30 characters
2
You scoped out the search feature. The interviewer now says it is the main requirement.
0 / 30 characters
3
Actually, users must be able to edit and delete everything retroactively. Does that break your design?
0 / 30 characters