Comparison Card 197 — Staff-Level Technical Strategy / Assess
Situation
Staff-level rounds test prioritization, architecture, risk, and decision framing across a larger technical surface. 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. The framework scales well because it separates problem framing from option assessment and review. 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 can support a past leadership story, but not the live strategic reasoning expected in this discussion. 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 judgment under ambiguity, not narrative neatness alone. 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 staff-level technical strategy 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?”