Candidate success profile template: an ideal candidate profile written from the work
On this page
- Success profile, job description or requisition: what is the difference?
- What goes in a candidate success profile?
- The candidate success profile template
- How do you write criteria an interviewer can actually check?
- Variants for common situations
- A filled example
- How to use it, stage by stage
- Mistakes that make a profile useless
- Questions people ask
A candidate success profile, also called an ideal candidate profile, is a one-page document that says what the person in a role must achieve in their first year and which three to five capabilities predict that, each written as evidence an interviewer can actually collect. The hiring manager and recruiter agree it at the intake meeting, before the job is posted. Everything after it, the job description, the screening questions, the interview guide and the scorecard, is derived from it, which is why a vague profile produces a vague search.
Below: how a success profile differs from the documents it gets confused with, a copy-ready template, how to turn vague criteria into checkable ones, four variants, a filled example and how to use it at each stage. If you are hiring your own replacement, the shorter profile in how to hire your replacement is built for that case.
Success profile, job description or requisition: what is the difference?
| Document | Written for | Its job | When |
|---|---|---|---|
| Requisition | Approvers and finance | Get the role approved and funded | Before the search |
| Success profile | The hiring team | Define good performance and how each criterion is tested | At intake, before posting |
| Job description | Candidates | Attract the right people and let the rest self-select out | After the profile |
| Interview guide and scorecard | Interviewers | Collect and rate evidence against the profile | Before the first interview |
Some teams also write a "candidate persona" for sourcing: where these people work now, what they care about, what would make them move. That is useful, but it describes the market, not the job. Keep it as an optional section of the profile rather than a substitute for it.
What goes in a candidate success profile?
- Why the role exists now: the problem the hire solves, in two sentences.
- Outcomes: what the person will have achieved at 90 days and at 12 months, concretely enough to check.
- Must-haves (three to five): each with the outcome it serves, the evidence that shows it, and the interview stage that tests it.
- Nice-to-haves: useful, but nobody is rejected for lacking them.
- Deliberately excluded: criteria the team agrees not to use, such as a degree, a specific employer or years of experience as a proxy.
- Working conditions: location, schedule, travel, on-call, pay range. These end searches late if nobody says them early.
- Where this person is today: likely current titles and employers, for sourcing.
- Sign-off: hiring manager and recruiter, with a date, and a line for changes later.
The candidate success profile template
CANDIDATE SUCCESS PROFILE: [Role title], [Level]
Req ID: [ ] Hiring manager: [name] Recruiter: [name] Date: [date]
1. WHY THIS ROLE, WHY NOW
[Two sentences: the problem this hire solves, and what happens if the
seat stays empty.]
2. OUTCOMES
By day 90: [specific, checkable outcome]
[specific, checkable outcome]
By month 12: [specific, checkable outcome]
[specific, checkable outcome]
3. MUST-HAVES (3–5)
# Capability Serves outcome Evidence we'll accept Tested at
1 [ ] [ ] [what they've done / show] [stage]
2 [ ] [ ] [ ] [stage]
3 [ ] [ ] [ ] [stage]
4. NICE-TO-HAVES (no one is rejected for lacking these)
- [ ]
- [ ]
5. DELIBERATELY EXCLUDED (we will not screen or score on these)
- [e.g. a specific degree, "X years" as a proxy, named employers]
6. WORKING CONDITIONS
Location: [ ] Schedule: [ ] Travel: [ ] On-call: [ ]
Pay range: [$min–$max] Start by: [date]
7. WHERE THIS PERSON IS TODAY (for sourcing)
Likely titles: [ ] Likely employers or sectors: [ ]
Why they might move: [ ]
8. SIGN-OFF
Hiring manager: [name, date] Recruiter: [name, date]
Changes after sign-off: [date, what changed, why, agreed by]
How do you write criteria an interviewer can actually check?
The test for every must-have: could two interviewers, independently, agree whether a candidate has shown it? If not, rewrite it as something the candidate has done or can do in front of you.
| Vague | Checkable |
|---|---|
| Strong communicator | Has explained a technical change to non-technical customers and can describe how they knew it landed |
| Self-starter | Has started a piece of work nobody assigned, and can say why and what came of it |
| 5+ years' experience | Has owned [the specific outcome] end to end at least once |
| Data-driven | Can walk through a decision they changed because of a number, and where the number came from |
| Culture fit | Remove it, or name the actual behavior, such as giving direct feedback to a peer |
Starting from the work rather than from the last person in the seat also has a compliance logic. The US Uniform Guidelines on Employee Selection Procedures say validity studies "should be based on review of information about the job" (29 CFR 1607.14, as of October 2026). A success profile built from outcomes and tasks is a practical version of that review; this is general information, not legal advice. For an outside starting list of tasks, the O*NET database, sponsored by the US Department of Labor's Employment and Training Administration, lists tasks, skills and work context for each occupation. Use it to prompt the conversation, then cut everything that is not true of your role.
Must-haves map naturally to competencies, so if your team already uses a competency library, borrow its wording; competency-based interviewing explains how the two fit.
Variants for common situations
Short version for high-volume or hourly roles
[Role], [Location] Hiring manager: [name] Date: [date]
Good at 30 days looks like: [one line]
Must-haves (max 3): [ ] / [ ] / [ ] Tested by: [screen / trial shift]
Hard requirements: [schedule, license, lifting, start date]
Not required: [ ]
Pay: [$ / hour] Shifts: [ ]
Keep it to what a screener can check in ten minutes. Anything else slows a hiring process measured in days.
Agency version, from the client intake
Add two lines to the full template: "What the client said about their last good hire in this role" and "Reasons the client has rejected candidates before". Then read the must-haves back to the client and get agreement in writing before you source. The client intake call agenda covers the conversation; the profile is what you send afterwards.
First-of-its-kind role
When nobody has done the job at your company before, write the outcomes as hypotheses and mark them that way. Agree to revisit the profile after the first three to five candidates, because early interviews often reveal that a must-have was a guess.
Replacing someone who is leaving
Ask what should change before you copy the old profile forward. A resignation is the cheapest moment to rebalance work, and "hire the same again" is often the wrong answer.
A filled example
An invented role and company, to show the level of detail:
Role: Customer Success Manager, mid-market accounts. Why now: two managers each carry about 60 accounts and renewals are being handled late; the new manager takes 40 accounts in the manufacturing segment.
Outcomes: by day 90, has met the main contact at all 40 accounts and flagged every renewal due in the next two quarters with a risk rating; by month 12, owns the segment's renewals with no renewal handled in the final two weeks before its date.
Must-haves:
- Has run renewals for a book of accounts, and can describe one they saved and one they lost. Tested at the recruiter screen and hiring manager interview.
- Can explain a product change to a non-technical buyer. Tested in a 15-minute role-play.
- Prioritizes a book by risk, not by who emails loudest. Tested with a short exercise: rank ten invented accounts and explain the order.
Nice-to-haves: manufacturing customers; experience with the CRM the team uses.
Excluded: a degree; a minimum number of years; SaaS-only backgrounds (account managers from distribution businesses are in scope).
Working conditions: hybrid, two office days; quarterly customer visits; pay range set by HR.
Where they are today: account managers and customer success managers at software and distribution companies selling to factories.
How to use it, stage by stage
- Intake. Fill sections 1 to 3 in the meeting itself, using the intake meeting questions. Send the draft the same day and get sign-off within two working days.
- Job description. Write requirements from the must-haves, duties from the outcomes, and leave out anything in the excluded list.
- Screening. Turn each must-have tested at the screen into one question, with what a strong answer includes.
- Interview plan. Assign every must-have to exactly one interviewer, and build each interviewer's interview guide from their assignment.
- Scorecard. One row per must-have, rated against the evidence column. The interview scorecard template has the format.
- Debrief. Discuss must-haves in order, and do not add new criteria in the room. If the team discovers a missing criterion, update the profile, date the change, and apply it to every remaining candidate.
- 90 days after the hire. Check the day-90 outcomes. Where the hire succeeded or struggled in a way the profile did not predict, fix the profile before the next search for the same role.
Mistakes that make a profile useless
| Mistake | What happens | Fix |
|---|---|---|
| Ten must-haves | Nobody meets them, so the team quietly ignores half | Three to five, each one a real dealbreaker |
| Traits instead of evidence | Each interviewer reads "strong communicator" differently | An evidence column for every must-have |
| Written after interviews start | The profile describes the favorite candidate | Sign off before posting |
| Criteria added in the debrief | Candidates judged on things nobody tested | Change the profile, date it, apply it to all |
| No working conditions | Finalists drop out over pay, travel or office days | Section 6 filled at intake |
| Never revisited | The same mis-hire, twice | Check it at 90 days |
Questions people ask
What is a candidate success profile?
A candidate success profile, also called an ideal candidate profile, is a short document that says what the person in a role must achieve in their first year and which few capabilities predict that, each written as evidence an interviewer can collect. The hiring manager and recruiter agree it at intake, before the job is posted, and it drives the job description, screening questions, interview guide and scorecard.
What is the difference between an ideal candidate profile and a job description?
A job description is written for candidates and sells the role while listing duties and requirements. A success profile is written for the hiring team and defines what good performance looks like and how each criterion will be tested. The job description should be derived from the success profile, not the other way round.
How many must-have criteria should a success profile have?
Usually three to five. Each one should be something a person without it would fail in the role, tied to an outcome in the profile and assigned to an interview stage. If a hiring manager would hire someone strong who lacked a supposed must-have, it belongs in the nice-to-have list.
Who should write the candidate success profile?
The hiring manager owns the content, because they know what the work requires. The recruiter runs the conversation, pushes vague criteria into observable ones and checks the profile against the market. Interviewers should read it before they are assigned questions.