1 min lesson
The loop mirrors the job
Rebuild the main list in "The loop mirrors the job", then say what each item changes.
Step 1 of 2
The phrase that should reframe the whole interview is everyone does everything. On a flat team the PM writes a prototype in the morning, runs a demo for an enterprise prospect after lunch and drafts the changelog before they log off. The work is defined by the outcome, not by a job boundary.
- Truth-seeking and spirited debate with low ego - you argue the idea, then commit and you don't need rank to be heard.
- Crazy ideas are welcome, but they have to ship; a brilliant doc that never reaches users counts for nothing here.
- Shipping code and running demos are PM work, not someone else's job you coordinate.
- Direct, clear communication at high pace, because the team is small enough that vagueness compounds fast.
The onsite hands you a small project and a live "discuss ideas" session precisely because the job is open-ended building, not ticket execution. If the org is flat and process-free, you should expect to be tested on whether you can self-direct from a vague prompt to a shipped, opinionated thing. Read the org correctly and the interview format stops being a surprise.
Learn more
Full explanation
The Loop at a Glance
Interactive diagram. Step through it with the Next and Previous controls below, or Tab to a region to read its detail.
Each stage maps to a charter duty - the loop tests building, not process.