Comparison Card 182 — Pair Programming / Assess
Situation
Pair-programming rounds test collaboration, communication, and shared problem solving in real time. 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. Because the steps are explicit, BASIC makes it easier to keep the partner aligned on where the solution currently is. 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 centers on solo retrospective narrative, which is the wrong shape for collaborative live work. 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
The signal is shared context, not just individual brilliance. 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 pair 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?”