Theory Card 093 — Interviewer Collaboration / Structure
Research lens
Technical interviews are partly collaborative: the interviewer is looking at how you work with constraints, hints, and feedback. In the Structure stage of BASIC, the goal is to externalize a plan, invariant, or architecture. That makes this concept especially relevant here, because it shapes how much mental work the candidate is trying to carry at once and what gets made explicit.
Why it matters in SWE interviews
This especially matters in live coding, pair-programming, and system design rounds. Because the stages are explicit, the interviewer can enter the conversation without knocking you off your entire process. In practice, Structure is where the candidate should ask: What is the sequence, helper structure, invariant, or component map that will carry the solution? That question acts like a cognitive boundary. It protects the answer from turning into an unstructured search.
BASIC move
A strong move here is to make the plan visible before full execution. For Interviewer Collaboration, that means deliberately naming the important units instead of juggling them implicitly. The interviewer sees cleaner reasoning, and the candidate benefits from reduces hidden-state thinking and makes reasoning inspectable.
Common miss
The miss is treating hints like interruptions instead of input to re-assess the current plan. When that happens, the candidate usually feels busy, but the answer is actually becoming less inspectable.
Practice prompt
“While practicing, pause at the Structure step and explain how Interviewer Collaboration changes the way you would handle the prompt.”