1 min lesson
There's a caution that matters in a fast org
In "There's a caution that matters in a fast org", answer "Which version of a process-improvement story is strongest in this interview?" Then point to the lesson detail behind your choice.
Step 1 of 2
There's a caution that matters in a fast org: improve the system without breaking what works. Cursor is small and moving quickly, so a heavy new process that the team has to learn mid-sprint can cost more than the friction it removes. Change at the edges, prove it, then expand.
Have one polished “I saw friction and fixed it” story ready before you walk in. Structure it tight: the specific friction you noticed (no one told you to look), the small fix you shipped and the number that moved - time-to-schedule dropped, no-shows fell, error rate hit zero. End on the result, not the effort. That single story does more to prove the ops-builder half of the role than any list of responsibilities you recite.