Question
Prepare one project story and one reason for the role. The project story is five to eight minutes. Open on a constraint and the choice you made. ## Requirements - State why you chose that approach, what you turned down, and what you measured. - Lead with the technical choice, not a business result. - Be ready for a redirect to recent work, a deeper bottleneck, or an option you did not use. - The motivation names a real direction you can contribute to, tied to a skill you have already used. - Keep two depths ready: the system shape, and the kernel or model detail. Pick the depth the conversation asks for. - Keep a short reset so a redirect does not lose the thread. ## Review checklist 1. Does the opening name one constraint and one choice before any result? 2. Can the story stand alone if the listener stops the setup after about a minute? 3. Is the motivation tied to a skill you can demonstrate, rather than a general compliment? 4. Can you answer "what would you decide differently today?" without changing the facts of the story? ## Staged follow-ups 1. Tell the project in one minute, centered on the choice. 2. Take the interruption "go deeper on the bottleneck" and stay on that bottleneck. 3. Answer what you would decide differently today. 4. Give the motivation in under a minute and connect it to the same project.