Your goal: hold one level across a practical build and a stressed customer, the way a startup loop is decided: working code, honest scoping, a steady voice.
How this works (about 43 minutes)
- Round 1 (about 20 minutes): a practical build. Talk it through first; the notepad is there if you want to write code or pseudo-code. Ryan reads it when you point at it and never writes the solution.
- Round 2 (about 20 minutes): Ryan plays a founder five days from launch. You are the engineer on the account. Ask him what you need; he gives facts one at a time. The details are made up for the exercise.
- Ryan tells you when he switches. This is a practice room in the style of a startup loop, built from what candidates report, not any company's real process.
- No hints and no scores during the call. Your report comes after.
What scores well
- Clarifying the input, the failure cases and the volume before writing anything
- Idempotency, ordering and retries named and handled simply
- Triage first with a founder: contain the fear, find the cause, set an update rhythm
- Saying no to the extra feature without losing the customer
- Owning the launch, not only the bug
Tips
- Take the build, extend-and-debug and customer-room coaches first.