A candidate persona is a fact-based profile of the typical person you want to hire for a role family: their situation, what motivates them, what holds them back and where you can reach them. It is built from data on past hires and conversations, not from imagination, and it exists to make three things sharper: the search, the first message and the interview.
It is not a job description (what the role needs), not an ideal candidate profile (what the person has) and not a marketing buyer persona. The persona adds what the other two leave out: why this person would move at all.
Persona, ideal candidate profile and job description: the difference
| Document | Answers | Typical content | Used for |
|---|---|---|---|
| Job description | What does the role need? | Tasks, requirements, salary range | The job ad, the contract |
| Ideal candidate profile | What does the person bring? | Skills, experience, certificates | Screening and search criteria |
| Candidate persona | Why would this person move, and how do we reach them? | Situation, motives, objections, channels, message angle | Outreach, ad targeting, interview opening |
| Employer value proposition | What do we offer that is provable? | Differentiators with proof | The promise inside the message |
How do you build a candidate persona? Seven steps
- Pick a role family, not a single vacancy. "Sales engineers in DACH" is a persona; "the sales engineer we need in March" is a job.
- Pull the facts from your last 10 hires of that family: previous employer type, how they were found, how long from first contact to signature, the reason they gave for saying yes.
- Add the people who said no. Declined offers and runner-ups tell you the objections. Silver medalists are the cheapest source of this; see silver medalist recruiting.
- Interview three to five people in the role. Ask what would make them take a call from a recruiter and what would make them delete the message.
- Fill the template below. One page, no stock photo, no invented first name and hobby.
- Turn it into search criteria. Split into must-have and nice-to-have as described in must-have vs nice-to-have search criteria; those criteria then drive your active sourcing.
- Test and revise. After about 30 messages per angle, compare reply rates and rewrite the angle that failed.
The template
| Field | What goes in | Check |
|---|---|---|
| Role family and level | Name, seniority, scope | Could two recruiters read it the same way? |
| Situation | Typical employer type, team size, tenure | Taken from real hires, not guessed |
| Top 3 motives (ranked) | What makes them move, from interviews | Each one traceable to a source |
| Objections | Why they stay or decline | From declined offers |
| Title variants | Other names for the same job | Needed for the search string |
| Channels | Where they answer: LinkedIn, email, XING, communities | From how past hires were reached |
| Message angle | The one differentiator from your EVP that fits | Provable in one sentence |
| Disqualifiers | Objective dealbreakers (certificate, permit, location) | Job-related only |
One rule that protects you: leave out protected characteristics
Do not describe the persona by age, gender, origin, religion, disability or sexual identity. Section 1 AGG lists these grounds, section 7 forbids disadvantage because of them, and section 11 requires job ads to be neutral. A persona that says "28-year-old woman" will steer the ad, the search and the shortlist exactly there. Use situation, skills and motives instead. Also keep real people out of the document: a persona is an aggregate, and any data on identifiable individuals falls under the information duties of Article 14 GDPR.
Worked example: sales engineer, B2B software, DACH (illustrative)
The entries are examples of the format. Fill yours from your own hires.
| Field | Entry |
|---|---|
| Role family | Sales engineer / solutions engineer, 4–8 years, customer-facing |
| Situation | Works at a software vendor with 50–500 staff; often the only technical person in the sales team |
| Motives | 1. Product they can believe in. 2. Closer contact with the people who build it. 3. Travel they can plan |
| Objections | Fear of a worse product; unclear commission rules; long notice period |
| Title variants | Sales engineer, solutions engineer, presales engineer, Vertriebsingenieur, Technical Account Manager |
| Channels | LinkedIn message first, email as follow-up |
| Message angle | "You would sit next to the engineering team and see the roadmap before you sell it" (only if true) |
| Disqualifiers | No hands-on technical background; no right to work in the target country |
From persona to search: a copy-ready string
The title variants feed the search directly. On LinkedIn Recruiter or similar tools, the example above becomes:
("sales engineer" OR "solutions engineer" OR "presales engineer" OR "Vertriebsingenieur") AND (SaaS OR API OR integration) NOT intern
Boolean strings only match words. If the persona describes experience that has no standard title ("rebuilt a support team after an acquisition"), a keyword string cannot express it, which is where a search that reads profiles in context helps.
Where Sprad fits, and where it does not
Sprad does not generate personas for you; the evidence has to come from your own hires. Once you have one, you can describe it in your own words in the people search: the platform checks each profile individually against the description instead of matching keywords, and finds people with poorly maintained profiles too. A web search with the normal budget costs 100 credits for up to 50 qualified profiles (2 credits per profile shown, never more than the budget); the free plan includes 100 credits a month. Outreach runs on LinkedIn and email from one inbox, and the pitch format lets you store the message angle once. Everyone you find stays in your talent network. Prices are on the pricing page.
FAQ
How many personas do I need per role?
One to three. More than that and nobody uses them. If you need five, the role family is too broad.
Is a candidate persona the same as a buyer persona?
The method is the same, the subject differs. A buyer persona describes who purchases a product; a candidate persona describes who you want to hire and why they would change employer.
Can I let AI draft the persona?
You can let it structure interview notes and your hiring data. Do not let it invent motives: unchecked output reproduces stereotypes, which is exactly the AGG risk above.
How often should I update it?
After every 10 hires of the role family, or when reply rates for an angle fall noticeably.
Where does the employer value proposition come in?
The persona says which motive matters; the employer value proposition supplies the provable promise that answers it.






