Most hiring teams can say how many people they hired and how long it took. Far fewer can say how the process felt to the people in it, which is what these measures answer inside the wider candidate experience platform.
Book a free, no-obligation product demo call with our experts.
Candidate experience is not one number. It is a small set, and each one is only worth collecting if somebody owns the answer.
| Metric | What it answers | Where it lands |
|---|---|---|
| Headline score | One comparable number per stage and cohort. That score is candidate NPS, calculated the same way as the eNPS you already report. | Talent leadership |
| Driver scores | Clarity of the role, speed of response, fairness of the assessment, quality of communication. Drivers are what turn a score into something you can act on. | Recruiter, hiring manager |
| Participation and silence | Who answered, and who has not. A stage nobody replies to is telling you something as clearly as a low score would. | Recruiting ops |
| Stage completion | Where in the journey feedback drops off. Falling response rates usually mean a process problem rather than an engagement one. | Process owner |
A single exit survey averages away the thing you needed to find. Tying a score to one step is what makes it fixable.
A score with no owner is trivia. Cutting results by dimension is what puts each weak spot in front of the person whose process produced it.
A useful set is small: one headline score such as candidate NPS, a handful of driver scores covering clarity, speed, fairness and communication, participation rate including the candidates who did not respond, and stage-level completion. Together those answer what the experience scored, why it scored that way, who it applied to, and where in the hiring journey it happened. Anything beyond that tends to add reporting work without adding a decision.
Measure at each decision point in hiring rather than once at the end: after application, after each interview stage, at the offer decision including candidates who were rejected or declined, and at the handoff into onboarding. Keep each survey short and specific to what the candidate just experienced. Stage-triggered measurement ties every score to a step you can actually change, which a single end-of-process survey cannot do. CultureMonkey runs this as part of a wider candidate experience platform rather than as a standalone form.
Not one we would ask you to trust. Candidate experience benchmarks are thin, inconsistently defined across sources, and rarely comparable to how your own hiring works. The more reliable read is your own baseline over time: this quarter against last, one job family against another, one recruiter's stages against the team. That comparison is internally consistent, which an external average is not.
Yes, when both are produced by the same instrument. CultureMonkey uses the same drivers and the same score math for candidates as for employees, with a candidate reporting threshold set separately, so a candidate result and an employee engagement metric sit on one continuous line rather than in two systems that never meet. That is what makes the handoff from candidate to new hire readable rather than a break in the data.
Access is role-based. Super admins see every candidate survey and report across the organization. Sub admins are scoped to the surveys, teams and candidate populations they are explicitly assigned. Hiring managers receive routed surveys and see results for their own hiring only. On top of that, a candidate reporting threshold hides any cut that falls below it, so a small cohort cannot be narrowed down to one person.
Every stage, cut by recruiter, hiring manager, job and location.