Comparison Card 106 — Coding Easy / Breakdown
Situation
A short coding prompt with a relatively direct solution still requires clarity, not just speed. In this setting, the active interview task is happening now, not in the past.
Why BASIC fits better here
During Breakdown, BASIC asks the candidate to decompose the prompt into named parts. Even simple coding questions reward quick decomposition and verification more than retrospective storytelling. 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 optimized for narrating past situations, not for live reasoning about the prompt currently on the board. 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 still notice whether you restated the task, chose the right approach, and tested your code. The BASIC move at this stage is to split the problem before trying to solve it. That gives the interviewer concrete evidence that the candidate can think, choose, build, and verify under pressure.
Practical script
“In this coding easy situation, I’m using the Breakdown step to split the problem before trying to solve it. The main question I need to answer is: What exactly is the problem asking, what are the constraints, and what is the shape of the input and output?”