Comparison Card 148 — Backend System Design / Structure
Situation
Backend architecture prompts require requirements work, scale reasoning, and component choices. 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. BASIC aligns naturally with the flow from requirements to trade-offs to architecture to 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 is retrospective and anecdotal, while backend design is prospective and analytical. 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
Scoring often reflects practicality, scalability, reliability, and trade-off reasoning. 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 backend system design 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?”