Comparison Card 172 — Architecture Review / Assess
Situation
An architecture-review interview asks whether you can critique and improve a proposed system. In this setting, the active interview task is happening now, not in the past.
Why BASIC fits better here
During Assess, BASIC asks the candidate to evaluate candidate directions and constraints. BASIC helps because reviewing still requires decomposition, assessment, proposed structure, and validation. That matches the live technical work of the round, because the interviewer is evaluating present-tense reasoning, not only narrative polish.
What goes wrong with a STAR-shaped response
STAR describes what happened in the past; architecture review is an active evaluation of a present artifact. If a candidate leans too hard on a story-shaped answer in this moment, they may sound organized while still leaving the technical core underdeveloped.
What the interviewer is really seeing
The signal is thoughtful critique, prioritization, and improvement with trade-offs. The BASIC move at this stage is to compare plausible approaches before committing. That gives the interviewer concrete evidence that the candidate can think, choose, build, and verify under pressure.
Practical script
“In this architecture review situation, I’m using the Assess step to compare plausible approaches before committing. The main question I need to answer is: What approaches are available, what trade-offs matter, and what complexity target is realistic?”