How to write an ideal candidate profile that survives a search
An ideal candidate profile is the short written spec of what a person must be able to do to succeed in one specific role, agreed with the hiring manager before sourcing starts. It separates the few requirements that gate from the many that only rank, and it becomes the screening criteria.
What is an ideal candidate profile?
Ideal candidate profile The written spec of the skills, experience and behaviours a person needs to succeed in one specific role, agreed with the hiring manager before sourcing starts, and short enough that everyone screening can hold it in their head.
A recruiter briefs a search from it, then screens every person against the same short list. When somebody argues that a candidate is not the ideal candidate for the job, the profile is the document that settles which requirement they actually failed.
Candidate profile, ideal candidate profile, job description or persona?
| Artefact | What it is | Who writes it | What it is for |
|---|---|---|---|
| Candidate profile (ATS record) | The record of one real applicant: their CV, contact details, stage and notes. | Created by the system when somebody applies or is imported. | Tracking and deciding on one named person. |
| Ideal candidate profile | The spec of who you want, written before anyone applies. | The recruiter and hiring manager together, in the intake conversation. | Briefing a search and screening everyone against one list. |
| Job description | The public advert: the role, the duties, the company, the pay range where required. | The hiring team, usually edited for publication. | Attracting applicants and setting expectations. |
| Candidate persona (employee persona) | A narrative sketch of motivations, career stage and where these people spend time. | Usually recruitment marketing, borrowing the method from marketing. | Shaping outreach and messaging, not screening. |
How to write an ideal candidate profile in 6 steps
- Start from what the person must produce Ask what this person will have delivered 6 months in. Write 3 concrete outcomes. Everything else on the profile has to earn its place by supporting one of them. "Our payment retries are handled by a service they built and other engineers can run."
- Get the hiring manager talking about real people Ask about the last person who succeeded in this kind of work and the last who did not, and push for behaviours rather than adjectives. Capture the manager's own words. "She read the incident log before touching the code" beats "strong ownership".
- Turn each outcome into something you could verify A requirement you cannot check in a 30 minute screen is a wish. Write the requirement and the evidence you would accept for it in the same line. "Has run a migration on a live system" plus "can walk through the rollback plan".
- Sort every requirement into 3 buckets Must have, prioritise, preferred. Only must-haves remove people from consideration. Everything else moves someone up or down the list, which is a completely different decision.
- Test each must-have against 3 questions Is it noncomparative, is it objective, and is it relevant to performing this job? Those 3 conditions come from the federal contractor rule on basic qualifications at 41 CFR 60-1.3, and they are a good filter for anyone. "A Bachelor's degree in Accounting" is objective. "A technical degree from a good school" is not.
- Write it down and date it before the first search The same federal rule expects basic qualifications to be advertised or recorded before any expression of interest is considered. Setting the bar after you have seen people is how it quietly moves. Name the agreeing manager and the date at the bottom of the profile.
Cap the must-haves at 6
Every must-have is an AND. The arithmetic is unforgiving: 5 independent filters that each halve a pool leave about 3 percent of it. Past 6, you are usually removing people your hiring manager would have hired.
An ideal candidate profile template you can copy
ROLE [Title] · [Team] · [Location or remote scope] · Agreed [date] WHAT THEY MUST PRODUCE IN 6 MONTHS 1. [Outcome, stated as a finished thing] 2. [Outcome] 3. [Outcome] MUST HAVE (maximum 6, each one verifiable, each one gates) - [Requirement] -> verified by: [what you will ask or check] - [Requirement] -> verified by: [what you will ask or check] PRIORITISE (ranks people higher, never removes them) - [Requirement] PREFERRED (a plus, nothing more) - [Requirement] WHERE THESE PEOPLE WORK TODAY Titles: [ ] Adjacent titles we will accept: [ ] Company shape: [industry, stage, scale of system, not brand names] DEAL-BREAKERS - [Thing that ends the conversation, and why it relates to the job] AGREED WITH [Hiring manager name], [date]. Next review after [n] screens.
Ideal candidate examples, filled in
In 6 months, payment retries run through a service they designed, with a runbook other engineers use without asking them questions.
Has owned a service in production. Has worked on money movement or another domain where correctness is audited. Writes documentation other people actually follow. Can explain a rollback.
Naming a specific framework as a must-have when the underlying skill transfers in a fortnight.
In 6 months, they take their own patient assignment on nights, precept a new graduate, and escalate deterioration without waiting to be asked.
Current unrestricted licence for the state. Critical care experience with ventilated patients. Comfortable escalating to a physician. Available for the shift pattern the unit actually runs.
Requiring a specific number of years when the unit really needs specific competencies signed off.
In 6 months, they have closed 2 deals above the enterprise threshold and run their own multi-stakeholder cycle without the founder in every call.
Has closed deals at this size and cycle length. Has sold into this buyer, not just this industry. Builds a business case rather than a feature list. Keeps a pipeline you can inspect.
Gating on a named CRM or a logo list when what matters is deal shape and buyer type.
In 6 months, first response time is predictable, the team has a documented escalation path, and the product team gets a weekly summary of what is breaking.
Has managed a support rota. Has written a macro or help article library that reduced repeat contacts. Can read a queue and staff against it. Handles an angry customer without escalating the tone.
Asking for people management experience when the job is really a senior individual contributor with a rota.
Where ideal candidate profiles go wrong
The commonest failure is cloning. Somebody studies the 2 people currently doing the job well and writes their CVs into the requirements, which imports everything incidental about those 2 careers along with what actually mattered. The honest version of that exercise is to ask what those people do, in behaviours, and then ask whether the requirement predicts the behaviour or just describes the person who happens to have it.
The second failure is the wishlist that grows during the intake call. Every stakeholder adds one requirement, nobody removes one, and the list reaches sourcing with more must-haves than anyone would defend one at a time. The third is writing the profile after the search has started, so the bar is set by whoever turned up first. Dating the document is a small thing that prevents a large one.
Check your profile before you search
- Every must-have is objective, not "a degree from a good school"
- Every must-have is noncomparative, not "top 5 by years of experience"
- Every must-have is relevant to performing this particular position
- You can name the work behaviour each requirement predicts
- Nothing on the list describes a person rather than the work
- The profile was recorded before you looked at anyone
- Each must-have has an agreed way to verify it in a screen
- Once you have run enough screens, compare selection rates by group
- Treat a rate below four-fifths of the highest group as a signal to investigate, not a pass or fail line
Must have, prioritise, preferred, as a working control
Each requirement is set to Must have, Prioritise or Preferred, and the results re-rank in place.
The bucket you chose on paper is a control in The Cognitive. A one-line brief is parsed into structured requirements, only must-haves gate, and the rest change the order. When the pool gets thin the search relaxes its softest filters itself and tells you what it broadened.
Writing requirements that survive contact with a search
Do
- Say whether a requirement is about the person or about their current employer
- Write the skill you need, then list the titles that usually carry it
- Describe company shape by industry, stage or scale of system
- Put the verification method next to the requirement, in the same line
Do not
- Gating on a company's tech stack when you mean the person's skill
- Using years of experience as a proxy for a competency you could ask about
- Naming employer brands as a requirement rather than as an example
- Adding a must-have in the intake call without removing one
From profile to scoring criteria
Named, described and weighted criteria that have to total 100, fixed for the role before anyone is interviewed.
A profile that never becomes screening criteria changes nothing. In The Cognitive the role's evaluation criteria are set first and stay fixed, while the interview questions stay live and adapt to what each person actually says. The scorecard then scores each criterion and marks resume claims verified, refuted or unclear.
Candidate ranking and relevancy scores
A relevancy score is a ranking device. It puts a list in an order. It is not a measurement of the person, and 2 tools will score the same CV differently because they weight different fields: one leans on title matches, another on skills, another on recency. Treat the number as a sort order, not as a verdict, and never as a measured gap between 2 people.
Identifying quality candidates is therefore a question about your profile rather than about the tool. Quality is relative to one role: whether this person can produce the outcomes you wrote down, checked the same way for everybody. The Cognitive shows no match percentage. Strong results carry a Strong match label and a place in the order, with the reasons written out.
Judged against your must-haves, with what still needs verifying
A written verdict, the reasons behind it, the one thing to verify in a screen, and a note on their career shape.
If you are the one being asked
Asked to describe why you are an ideal candidate for this position, answer against the advert. Name the 2 or 3 requirements you can evidence, give one specific example of each, then say what you would do in your first 90 days.
Turn your profile into a screen
Generate an interview rubric · Generate a scorecard · Generate interview questions · Job description templates · Free Boolean search generator
Frequently asked questions
What is a candidate profile?
The phrase has 2 common meanings. Before sourcing, a candidate profile is the spec of who you want: the requirements, written down and agreed. Once people start applying, most teams use the same phrase for the record of one real applicant in their system, holding the CV, contact details, stage and notes. This page means the first sense, usually written out in full as the ideal candidate profile.
What does candidate mean, and how do you define candidate?
Dictionaries define candidate as a person who seeks to be elected or appointed to a position or privilege, and figuratively anyone thought likely or worthy to gain one. In hiring, what's a candidate comes down to a person under consideration for a job. The word comes from the Latin candidatus, from candidus meaning dazzling white, because candidates for office in Rome wore bleached white togas.
What is the interviewee meaning, and how does it differ from candidate?
An interviewee is a candidate at one particular moment: the person being interviewed, right then. Candidate is the wider word and covers everyone under consideration, including people who are sourced and never reply. Every interviewee is a candidate. Not every candidate reaches an interview.
What is the ideal candidate meaning?
The ideal candidate is the person who meets the short list of things this role genuinely requires, not somebody who satisfies every wish on the list. The phrase does double duty, which causes confusion. Recruiters use it for the written spec, while job adverts use it for the person, as in the ideal candidate for a job or the ideal candidate for a position. Ideal candidates are defined by the same requirements either way.
How do I answer why you are the ideal candidate for this job?
Answer against the advert rather than against your whole CV. Pick the 2 or 3 requirements you can actually evidence, give one specific example for each with what you did and what happened, then say what you would do in the first 90 days. Do not claim every requirement. Interviewers are scoring named criteria, so being clearly strong on 3 beats being vague on 9.
How many must-have requirements should an ideal candidate profile have?
6 at most, and 4 is usually better. The reason is arithmetic rather than fashion. Each must-have is an AND that removes everyone who lacks it, so the filters multiply: 5 independent filters that each halve a pool leave roughly 3 percent of it. Anything you would still hire without belongs in the prioritise bucket, where it improves the order instead of emptying the pool.
How to identify quality candidates?
Define the requirement, define what verifying it looks like, then verify it the same way for every person. Quality candidates are not an absolute category: quality is relative to one role, and it means the person can produce the outcomes you wrote down. If you cannot say what evidence would satisfy a requirement, you cannot assess it, and you will fall back on impressions.
What is a relevancy score in recruiting?
It is a ranking device that puts a list of people in an order, not a measurement of anybody. Two tools will score the same CV differently because they weight different fields, such as title matches, skills or recency. Use it to decide what to read first and never as evidence of a gap between 2 people. The Cognitive shows a Strong match label and rank order instead of a percentage.
What is the DEI candidate meaning?
The phrase is used loosely, and often pejoratively, to suggest somebody was chosen for their demographic rather than their ability. It is not a hiring category anyone applies to or gets placed in. The defensible practice is the same for everyone: set requirements in advance that are objective, noncomparative and relevant to performing the job, record them before you look at anyone, and apply them identically.
Is an ideal candidate profile the same as a candidate persona?
No, and many teams keep both. Candidate personas and employee personas borrow the method from marketing: they describe motivations, career stage and where these people spend their time, in order to shape outreach and messaging. The profile describes requirements in order to shape screening. A persona tells you how to write the first email. The profile tells you who should get through the screen.
Explore: What is candidate sourcing? · What is a structured interview? · What is quality of hire? · Job description templates