Comparison Card 154 — Frontend System Design / Implement
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 Implement, BASIC asks the candidate to execute the chosen plan in controlled order. 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 transcribe the plan instead of improvising. 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 Implement step to transcribe the plan instead of improvising. The main question I need to answer is: How do we write or walk through the solution one stable layer at a time?”