Comparison Card 127 — Dynamic Programming / Assess
Situation
DP questions require state definition, transition logic, and base-case discipline. 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 staged approach is especially useful because DP falls apart when the state model is chosen implicitly or late. 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 does not give you a place to define state or compare top-down and bottom-up strategies. 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 show state, recurrence, complexity, and edge-case handling. 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 dynamic programming 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?”