Interviewing with AI as a review loop
When AI is allowed, the scarce skill moves from raw generation toward decomposition, verification, and repair ownership.
Current explanation
A practical AI-assisted interview loop is: state the contract, split the work, ask for a bounded candidate, inspect the diff, run the actual path, and explain which evidence changed your mind. The model is a fast collaborator, not the source of authority. Production readiness still includes tests, failure behavior, performance, accessibility, and explicit nonclaims.
Lesson path
- 01
Frame
currentWrite the contract and tool policy before prompting.
- 02
Delegate
nextAsk for one bounded implementation slice.
- 03
Review
nextFind one correctness risk the generated patch missed.
Open questions
- What evidence distinguishes orchestration from unexamined code generation?
Selected Q&A
What should I narrate?
The ownership map, the test that can falsify your theory, and the reason you accepted or rejected the candidate.
Next actions
- Run a 30-minute bug-squash rehearsal.
- Practice rejecting a plausible but overbroad patch.
Sources
- OpenAI interview guide
First-party description of pair coding, take-homes, and expertise-focused interviews.
- Canva AI-assisted interviews
First-party account of decomposition, delegation, review, and debugging.
Revision trail
· learning:interviewing-with-ai-as-a-review-loop@r1
Turned current interview research into a repeatable review loop.