Comparison Card 165 — Scalability Bottleneck Discussion / Check
Situation
Some rounds are less about building from zero and more about identifying what breaks first. In this setting, the active interview task is happening now, not in the past.
Why BASIC fits better here
During Check, BASIC asks the candidate to verify correctness, quality, and risk. Assess and Check are especially strong here because the job is to reason about pressure points and mitigations. 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 tell a story about a scaling project, but the interview task is to analyze this design now. 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
Interviewers want bottleneck identification, prioritization, and credible next steps. The BASIC move at this stage is to review and stress-test before you hand the answer over. That gives the interviewer concrete evidence that the candidate can think, choose, build, and verify under pressure.
Practical script
“In this scalability bottleneck discussion situation, I’m using the Check step to review and stress-test before you hand the answer over. The main question I need to answer is: Does the answer actually satisfy the prompt, handle edge cases, and survive scrutiny?”