2 min lesson
The doc is how a flat org aligns
Answer this: "A founder asks you to 'get our inference costs under control.' You have a 60-minute execution round to show how you'd scope it. What's your opening move and what makes it a good scope?"
Step 1 of 2
The doc is how a flat org alignswrite it down or it isn't real
There is no thick management layer at Cursor to carry context between rooms. The scoping doc is the mechanism that lets a founder, an ML lead and a Finance partner align without sitting in the same meeting. It is also your strongest interview artifact, because the JD says the doc is the deliverable.
- Goal
- The single metric-movement line, with guardrail and date
- Why now
- Two sentences on the business pressure that makes this worth doing
- Owners
- A named person per work-stream, plus the decision-maker for tradeoffs
- Plan
- The critical-path sequence, not an exhaustive task list
- Risks
- Top risks with a leading indicator and a planned response for each
- Out of scope
- What you are deliberately not doing, so nobody assumes it later
The “out of scope” line prevents more thrash than any other section. Unstated assumptions are where programs silently grow.
When the prompt is vague, narrate the rewrite out loud before you plan. “I'd first turn ‘optimize inference' into a target - say cut COGS per active user 15% by Q3 without regressing tab latency - because I can't scope what I can't measure.” That single sentence shows the interviewer you scope from outcomes and it earns you the right to ask clarifying questions about the real constraint.