Make talent quality your leading analytic with skills-based hiring solution.
Candidate Net Promoter Score (CNPS) is a recruiting metric that asks candidates how likely they are, on a 0 to 10 scale, to recommend applying to your company to someone else. Subtract the percentage of detractors (scores 0 to 6) from the percentage of promoters (scores 9 to 10) and you get a single number, from negative 100 to positive 100, that tracks how your hiring process actually feels from the candidate’s side.
That single sentence is where most CNPS content stops. The more useful question for a talent acquisition team is what comes next: how do you actually run this as an ongoing program, the way a product team runs NPS on customers, rather than as a one time survey that gets reported once and forgotten? That is what this guide covers: the calculation, the survey mechanics, real benchmark numbers by hiring stage, and a repeatable process for using CNPS to find and fix friction in your hiring funnel.
Candidate Net Promoter Score adapts the standard Net Promoter Score framework, invented by Fred Reichheld and popularized in customer experience work, to the hiring process. Instead of asking customers if they would recommend a product, you ask candidates if they would recommend applying to your company, based on their experience going through your recruitment process.
The score treats candidate experience as measurable and comparable over time, not as a vague reputational concern. A hiring team that tracks CNPS by stage, role, and recruiter can see exactly where in the funnel candidates lose confidence in the process, the same way a product team uses NPS to see exactly where users lose confidence in a product. It is the quantitative counterpart to the qualitative case for winning over top talent through candidate experience: the survey score is what tells you whether that experience is actually working.
The standard survey question, used consistently across CNPS vendors and glossaries, is a variant of:
“Based on your experience as a candidate, how likely are you to recommend applying to [Company] to a friend or colleague?”
Candidates answer on a 0 to 10 scale. You can adapt the wording slightly depending on where in the process you send it (swapping “your experience as a candidate” for “your interview experience” or “the application process so far”), but the 0 to 10 scale and the “how likely are you to recommend” framing should stay consistent across every touchpoint so the resulting scores are comparable to each other over time.
Once responses come in, sort them into three groups:
The formula is:
CNPS = % Promoters − % Detractors
Worked example: say 100 candidates respond to a post interview survey. 45 score you 9 or 10 (45% promoters), 30 score you 7 or 8 (passives, excluded), and 25 score you 0 through 6 (25% detractors). CNPS = 45 − 25 = +20.
The resulting number always falls between negative 100 (every respondent a detractor) and positive 100 (every respondent a promoter).
Benchmarks vary by source, but there is broad agreement on the shape of a good scale. Eddy’s HR encyclopedia frames it as: a score of 0 to 30 is good, 30 to 70 is great, and above 70 is excellent, with any score at or above zero indicating candidates view the process favorably overall.
The more useful benchmark data, though, is not a single average score, it is how much CNPS varies by stage of the hiring journey, because that variance is exactly what tells you where to focus. Starred, which collects candidate NPS responses from job seekers and publishes an annual benchmark report, has found scores swing dramatically depending on where and how a candidate exits the process:
Read that progression carefully and a pattern emerges: candidates who get more personal contact and clearer communication (an interview, a self initiated withdrawal, an offer) score the process far better than candidates who get rejected by a system with little or no human touch, especially right after an automated skill assessment step. That gap between negative 23 at the assessment stage and positive 1 at the interview stage is not really a story about the assessment tool itself, it is a story about communication and closure. This is exactly why an assessment step should be paired with clear, prompt feedback regardless of outcome, not left as a silent filter, and why the interview stage that follows tends to score so much better once a human is back in the loop.
Product teams do not run NPS once a year and file the result away. They trigger it at defined moments in the user journey, track it on a live dashboard, segment it by feature and by user cohort, and review movement in it on a regular cadence alongside other product health metrics. Recruiting teams should run CNPS the same way, for three reasons.
First, hiring is a funnel with distinct stages, just like a product has distinct features, and a single blended CNPS number hides which stage is actually broken. A team that only surveys hired candidates will only ever see the positive 80s number and miss the negative 20s hiding earlier in the funnel.
Second, CNPS correlates with outcomes recruiting leaders already track. A candidate who scores you a 9 or 10 mid process is more likely to accept an offer, refer other candidates, and apply again for a future role. This is also why CNPS pairs so naturally with the broader set of talent acquisition metrics most teams already track: a run of detractor scores at a specific stage is an early warning sign that shows up in offer acceptance rate and employer review sites (Glassdoor, Indeed, Comparably) well before it shows up in a quarterly retro.
Second only in the sense that it repeats: CNPS is also one of the few candidate experience signals you can act on quickly. Unlike time to fill or cost per hire, which are largely functions of market conditions and headcount planning, CNPS at a given stage is usually a direct function of process design choices your team controls this quarter.
A CNPS from 0 to 30 is generally considered good, 30 to 70 is great, and above 70 is excellent, per commonly cited HR benchmarks. In practice, judge your score against the specific hiring stage it was collected at rather than a single flat target: an interview stage score near 0 is roughly in line with reported benchmarks, while a hired candidate score should be well into positive territory, often 70 or higher.
Survey candidates on a 0 to 10 “how likely are you to recommend applying here” question, then subtract the percentage who answered 0 to 6 (detractors) from the percentage who answered 9 to 10 (promoters). Candidates who answered 7 or 8 (passives) are counted in the response total but excluded from the subtraction itself.
Trigger it automatically at every major funnel exit point (post application, post screen, post assessment, post interview, post offer), not on a fixed calendar schedule. The point is to capture the experience while it is fresh and to be able to compare CNPS stage by stage, which a single annual survey cannot do.
Candidate NPS measures the experience of people going through your hiring process, whether or not they are ultimately hired. Employee NPS measures the experience of people already working at your company. They use the same 0 to 10 promoter, passive, detractor methodology but sample a different population and typically move for different reasons.
Yes, and this is arguably the more valuable half of the program. Rejected candidates make up the majority of everyone who ever touches your hiring process, and their CNPS is a leading indicator for employer brand damage on review sites, future reapplication rates, and referral behavior, all of which happen whether or not you are watching for them.
There is no single universal threshold, but treat any segment (a specific recruiter, role, or stage) with fewer than roughly 20 to 30 responses as directional rather than conclusive, and avoid making process changes off a segment score built on a handful of responses.
Not automatically. Benchmark data shows rejection stages, especially right after an automated step like an assessment, commonly land negative even at companies with a strong overall process, since being told no rarely feels good regardless of how well it is handled. The number worth watching is the trend and the gap between stages, not whether any single rejection stage clears zero.
Candidate Net Promoter Score only earns its place on a recruiting dashboard if it is treated the way a product team treats NPS: measured at defined moments, segmented until it points at a cause, and reviewed on a cadence that leads to action. Used that way, it turns candidate experience from an anecdote into an operating metric your team can actually manage.
Hiring overqualified candidates is not automatically a mistake, but it is a decision that carries real, well documented risk if the role and the offer are not restructured around it. Recent survey data shows most employers already do this regularly: 70 percent of hiring managers say they typically consider candidates who are overqualified for the […]
Salary benchmarking is the process of comparing what your company plans to pay a role against real market pay data for comparable roles, then setting a range around a deliberate target point in that market rather than guessing. Done well, it turns “what should we pay this req” from a debate into a documented, defensible […]
Adverse action, under the Fair Credit Reporting Act (FCRA), is the legally required notice process an employer must follow before rejecting, terminating, or otherwise taking a negative action against someone based wholly or partly on a background check. It is not optional and it is not a courtesy: skip a step, and even an accurate, […]
