# Interview copilot: working checklist

Companion to https://lunaprompts.com/blog/technical-interview-copilot-guide

LunaPrompts Editorial. Original illustrative exercise.

## Define the workflow

- Role or campaign:
- Owner:
- Decision this workflow should support:
- Candidate instructions and support route:

## Worked example: Carry one question across the handoff

A candidate’s API assessment demonstrates correct validation and data handling. Their explanation of retries is brief. Before the interview, write a focused objective: understand whether the candidate can reason about duplicate operations after an ambiguous failure.

Open with the submitted code and a concrete change: the server completes the operation, but the response never reaches the caller. Ask what the caller should do and how the service would recognize a duplicate request. Discuss the tradeoff of the proposed approach at the scope expected for the role.

Leave room for the candidate to ask questions about the team. A tightly prepared technical conversation should create that room, rather than fill the call with more generated questions. The interviewer can follow a useful explanation without treating the copilot’s outline as a script.

Afterward, record which part of the uncertainty was resolved and which part remains open. Attach the conclusion to the response or work that supports it. In a later round, the next interviewer can explore a separate architecture or collaboration question instead of asking about retries again.

## Review checklist

- [ ] Before: One objective drawn from existing evidence
  Evidence or open question:
- [ ] During: A changed condition and a specific discussion
  Evidence or open question:
- [ ] After: An evidence-linked note
  Evidence or open question:
- [ ] Next round: A new question, not the same interview again
  Evidence or open question:

## Working session

Take a recent interview plan. Mark each question as already assessed, unresolved, or new. Replace one repeated question with a focused follow-up.

## Avoid this mistake

A combined report should not flatten disagreement into a confident summary. Preserve material differences between reviewers and the work each person relied on.

## Record the next step

- Observed evidence:
- What remains uncertain:
- Person responsible:
- Next action and date:

Keep candidate examples anonymous when sharing this worksheet.