Comparison Card 152 — Frontend System Design / Assess
Situation
Frontend design rounds involve state management, rendering paths, caching, performance, and user experience constraints. 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 keeps the answer from jumping randomly between component trees, APIs, and browser behavior. 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 not built for constructing a live client-side architecture from a new prompt. 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
Good answers connect product flows, state ownership, rendering strategy, and performance review. 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 frontend system design 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?”