What did the draft leave out?
Test a one-path draft against badge check results.
The question
You review a fictional studio’s folder pickup with the interviewer. They supply an example of an AI draft.
Scan badge → Release folder
Valid badge → Release folder. Invalid badge → Desk help.
“Which path is missing, and how would you show it?”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: Which branch is missing?
What would you do here? Open the move you’d make.
Add separate valid and invalid paths
The strong move. Each result gets the destination named in the instructions.
Keep the single path and add a label to Release
Tempting, but it misses something. A label alone does not route an invalid badge to the desk.
Send every scan to the desk
Tempting, but it misses something. The instructions already allow release after a valid result.
See how a strong candidate says it
“I’ll draw a badge result decision. Valid goes to Release folder. Invalid goes to Desk help.”
Why it works: The draft connects every scan to release. The instructions require a condition.
Step 2: Which example tests the draft?
What would you do here? Open the move you’d make.
Trace only a valid badge
Tempting, but it misses something. The draft already handles that path. The missing branch remains untested.
Use a longer arrow for invalid
Tempting, but it misses something. Arrow length does not identify the destination or condition.
Trace one invalid and one valid example
The strong move. This checks both destinations against the instructions.
See how a strong candidate says it
“I’ll trace an invalid badge. It must go to Desk help. Then I’ll trace a valid badge to Release folder.”
Why it works: An invalid example exposes the missing condition. A valid example checks that the original path still works.
Step 3: Where does unreadable go?
The scanner can now return Unreadable. The desk can check the badge manually. The folder stays on hold until a valid result.
What would you do here? Open the move you’d make.
Send unreadable to Release folder
Tempting, but it misses something. The new scan result does not show a valid badge.
Add an unreadable branch and hold release
The strong move. The desk can verify it without turning an unknown result into an answer.
Label it invalid and stop checking
Tempting, but it misses something. The scanner did not determine validity.
See how a strong candidate says it
“I’ll add Unreadable to Manual check pending. I’ll keep release on hold while the desk checks it.”
Why it works: An unreadable result gives no valid or invalid result. It needs a separate path.
Step 4: Trace one unreadable scan.
What would you do here? Open the move you’d make.
Show the hold and the later valid join
The strong move. This traces the new branch through a complete example.
Route the folder before the desk result
Tempting, but it misses something. The hold lasts until validation.
Erase the valid branch when you add manual review
Tempting, but it misses something. A valid scan can still release the folder under the original instructions.
See how a strong candidate says it
“Unreadable goes to Manual check pending. A later valid manual result joins Release folder. An invalid result stays with the desk.”
Why it works: The trace tells the interviewer what must happen before the folder can move.
The answer, in short
- Decision
- Add an unreadable branch that holds the folder for a manual check.
- Because
- The draft needs a valid result before the release arrow can be used.
- What would change it
- If the desk returns a valid result, join the existing release path.
Common traps
- Treating every scan as a valid result
- Treating unreadable as invalid
Check your answer
- What condition leads to release?
- Which opening example tests the missing branch?
- What does unreadable tell you?
- Where does a valid manual check join?
Last reviewed Nov 11, 2026