Candidate persona
Also called: ideal candidate profile, ICP for hiring
What a candidate persona contains
A useful one-page persona for a role:
- Background: typical career path, current type of company, years of experience.
- Motivations: what they care about (autonomy, scale, mission, comp, learning, brand). Pick 2-3 dominant ones.
- Where they live online: which platforms, communities, newsletters, podcasts.
- What they say no to: common objections to the role or the company.
- What earns their attention: signals in a job posting or outreach message that make them respond.
This is not a fictional character with a name and a photo. It’s a guide to where to look and what to say.
Why it matters for sourcing
Three direct uses:
- Channel selection: a persona based on “senior backend engineer in Berlin” guides you to specific Slack groups, GitHub repos, and meetups. A generic posting on Indeed misses them.
- Job-posting wording: the language that resonates with a senior platform engineer is different from what a junior generalist responds to. The persona tells you which to write.
- Outreach message templating: outbound that matches the persona’s motivations produces 2-3x reply rates compared to generic.
What goes wrong
- Personas based on the hires you wish you had, not the ones you actually attract. Aspirational personas misdirect sourcing.
- Personas written once and never revisited: the market shifts, the company shifts, the persona doesn’t.
- One persona per role becomes 12 personas across the company: the documentation is suspect.
Where Join fits
Persona notes attach to the role in Join, visible to anyone sourcing or writing the posting. The persona evolves with the role’s hiring data. See the features page.
