Comparison Card 203 — Project Technical Deep Dive / Structure
Situation
A technical deep dive on a past project still asks for architecture logic, constraints, trade-offs, and validation. In this setting, the active interview task is happening now, not in the past.
Why BASIC fits better here
During Structure, BASIC asks the candidate to externalize a plan, invariant, or architecture. Even though the subject is historical, the best explanation follows a problem-solving order rather than only a story arc. 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 overemphasize chronology while underemphasizing design mechanics and technical review. 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
Strong candidates explain the system like engineers, not like memoirists. The BASIC move at this stage is to make the plan visible before full execution. That gives the interviewer concrete evidence that the candidate can think, choose, build, and verify under pressure.
Practical script
“In this project technical deep dive situation, I’m using the Structure step to make the plan visible before full execution. The main question I need to answer is: What is the sequence, helper structure, invariant, or component map that will carry the solution?”