How to create a "What happens when you say yes to an interview" asset.
1-minute read
What happens when I say yes to an interview?
We recently created a doc for a customer that answers this question. The doc outlines the process a technical candidate would go through if they were to say yes to a conversation with one of their recruiters.
(Here's an example. Have at it.)
Why we created this asset:
Sharing this information upfront with a prospective candidate decreases sourcing friction and makes it easier for the candidate to say yes. It removes all guesswork—they know exactly what they’re saying “yes” to.
This is how we created the asset:
1. We had a 1-hour intake call with their lead recruiter.
- This call was for us to learn every detail of the hiring process and who is involved in each stage.
2. We then took all of our notes and turned them into 2 main sections:
- Section 1: Overview of the technical interview process.
- Section 2: Interview details. (Shown in steps.)
3. Added a personable intro and outro paragraph.
4. Added links to LinkedIn profiles (where specific names were mentioned) and linked to supplemental information where applicable to help candidates learn more about the people, team, and company.
Tactical notes:
- We intentionally created this in a Google doc and left off all branding. This is to keep the focus on the information. Branding is distracting. A Google doc is easily shareable and eliminates all desire to add shine to this asset.
- This doc was designed to be an outbound sourcing tool to share with candidates via email and DM.
- Copywriting is everything. Intake notes are one thing. Turning those notes into a well-structured piece of information that has a flow, feels personable and human, and is direct and succinct takes time. Invest here. It makes all the difference.
Recruiter enablement assets don't need to be sexy. They just need to be relevant, informative, and easily shareable.