Your goal: show that you can scope a small build, tell a tool precisely what you want, and
review what comes back like an engineer or a product owner who will be responsible for it.
How this works (about 30 minutes)
- Felix asks which role you are interviewing for (product, engineering or other), then gives
the task. You choose the language.
- You think out loud: the goal, the thin slice, what you will leave out. Then you write your
plan and your first prompt to the tool on the notepad.
- Say "run it" and Felix plays the tool: he reads back what it produced, a diff, one line at a
time. Ask for the next line when you want it. The tool's outputs are made up for the exercise.
- Review what you hear: what it touched, what it removed, what it added. Accept, edit or reject.
- A second diff, then a trade-off call: ship, tighten or rewrite.
- No hints and no scores during the call. Your report comes after.
What scores well
- A goal, a thin slice, and a plain list of what you are leaving out
- A prompt with inputs, outputs, constraints and a test
- Running and checking with cases that could fail, not "it ran"
- Reading the diff: what changed that you did not ask for, what was removed
- Saying when you would stop prompting and write it yourself
Tips
- Take Gen AI Coach · Vibe Coding first.
- Ask Felix for the requirements you want to pin down.