Theory Card 059 — State Modeling / Implement
Research lens
State modeling is the discipline of naming the information that must be carried forward for a solution to work. In the Implement stage of BASIC, the goal is to execute the chosen plan in controlled order. 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 appears in recursion parameters, DP tables, graph visit states, caches, and system components that hold truth. Assess and Structure together are where the candidate decides what state exists, who owns it, and how it changes. In practice, Implement is where the candidate should ask: How do we write or walk through the solution one stable layer at a time? 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 transcribe the plan instead of improvising. For State Modeling, that means deliberately naming the important units instead of juggling them implicitly. The interviewer sees cleaner reasoning, and the candidate benefits from keeps execution disciplined and easier to debug.
Common miss
The miss is burying important state in ad hoc variables without first explaining the model. When that happens, the candidate usually feels busy, but the answer is actually becoming less inspectable.
Practice prompt
“While practicing, pause at the Implement step and explain how State Modeling changes the way you would handle the prompt.”