Candidate Persona: How to Build One (Template and Example)

November 21, 2026
By Jürgen Ulbrich

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

DocumentAnswersTypical contentUsed for
Job descriptionWhat does the role need?Tasks, requirements, salary rangeThe job ad, the contract
Ideal candidate profileWhat does the person bring?Skills, experience, certificatesScreening and search criteria
Candidate personaWhy would this person move, and how do we reach them?Situation, motives, objections, channels, message angleOutreach, ad targeting, interview opening
Employer value propositionWhat do we offer that is provable?Differentiators with proofThe promise inside the message

How do you build a candidate persona? Seven steps

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Fill the template below. One page, no stock photo, no invented first name and hobby.
  6. 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.
  7. Test and revise. After about 30 messages per angle, compare reply rates and rewrite the angle that failed.

The template

FieldWhat goes inCheck
Role family and levelName, seniority, scopeCould two recruiters read it the same way?
SituationTypical employer type, team size, tenureTaken from real hires, not guessed
Top 3 motives (ranked)What makes them move, from interviewsEach one traceable to a source
ObjectionsWhy they stay or declineFrom declined offers
Title variantsOther names for the same jobNeeded for the search string
ChannelsWhere they answer: LinkedIn, email, XING, communitiesFrom how past hires were reached
Message angleThe one differentiator from your EVP that fitsProvable in one sentence
DisqualifiersObjective 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.

FieldEntry
Role familySales engineer / solutions engineer, 4–8 years, customer-facing
SituationWorks at a software vendor with 50–500 staff; often the only technical person in the sales team
Motives1. Product they can believe in. 2. Closer contact with the people who build it. 3. Travel they can plan
ObjectionsFear of a worse product; unclear commission rules; long notice period
Title variantsSales engineer, solutions engineer, presales engineer, Vertriebsingenieur, Technical Account Manager
ChannelsLinkedIn 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)
DisqualifiersNo 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.

Jürgen Ulbrich

CEO & Co-Founder of Sprad

Jürgen Ulbrich has more than a decade of experience in developing and leading high-performing teams and companies. As an expert in employee referral programs as well as feedback and performance processes, Jürgen has helped over 100 organizations optimize their talent acquisition and development strategies.

Free Templates &Downloads

Become part of the community in just 26 seconds and get free access to over 100 resources, templates, and guides.

No items found.

The People Powered HR Community is for HR professionals who put people at the center of their HR and recruiting work. Together, let’s turn our shared conviction into a movement that transforms the world of HR.