Hiring packet template

A good hiring packet does one job: give interviewers the context, questions, and evaluation criteria they need before the loop. 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, candidate profile, interview plan, scorecards, resume, work samples, and process notes 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 hiring packet

• Role context and hiring criteria.
• Candidate summary, resume highlights, and open questions.
• Interview plan with owner for each area.
• Scorecard, competencies, and evidence to collect.
• Debrief process and decision timeline.

Prompt to use in Claude

How to create it with Send

Give Claude role requirements, candidate profile, interview plan, scorecards, resume, work samples, and process notes, plus any constraints, examples, or audience notes that matter. Ask it to create the hiring packet with the Send connector so the output becomes a page instead of another loose document.

After you share it, Send helps you see whether interview teams open it, come back to it, or share it internally. You can update the same link when details change.

Hiring packet structure

1. 1

   Role criteria

   What the team is hiring for and how fit will be judged.

2. 2

   Candidate context

   Summary, background, strengths, and open questions.

3. 3

   Interview plan

   Interviewer assignments, questions, and scorecard.

4. 4

   Decision process

   Debrief, owner, timeline, and next step.

Why send a hiring packet as a page

Interview loops are better when everyone evaluates the same role criteria. Send gives interviewers one packet and keeps updates out of scattered messages.

Frequently asked questions