Interview plan template
Design a loop that tests the right signals instead of repeating the same conversation.
A good interview plan does one job: make the interview loop intentional instead of a set of repeated conversations. The format matters, but the useful part is the thinking behind it. Readers need the context, the recommendation, the proof, and the next step without having to reverse engineer your intent.
Claude can turn role requirements, competencies, candidate stage, interviewer list, scorecard, and process constraints into a clear first version. Send turns that version into a live page you can share, track, and revise as the conversation changes.
What to include in the interview plan
- The role, level, and hiring criteria.
- Interview stages and purpose of each stage.
- Questions, exercises, or topics for each interviewer.
- Scorecard and evidence to collect.
- Debrief process, timeline, and decision owner.
Prompt to use in Claude
Search the registry for the Send connector. Once connected, use their "send/interview-plan" skill.
How to create it with Send
Give Claude role requirements, competencies, candidate stage, interviewer list, scorecard, and process constraints, plus any constraints, examples, or audience notes that matter. Ask it to create the interview plan with the Send connector so the output becomes a page instead of another loose document.
After you share it, Send helps you see whether recruiters and hiring teams open it, come back to it, or share it internally. You can update the same link when details change.
Interview plan structure
Criteria
Role, level, must-haves, and decision bar.
Loop
Stages, interviewers, timing, and purpose.
Questions
Topics, exercises, and signals to collect.
Decision
Scorecard, debrief, owner, and next step.
Why send a interview plan as a page
An interview plan keeps the team from asking the same questions five times. Send makes the plan easy to share and update as the loop changes.