What to fix first, once the feedback is in
An overall candidate score gives you nothing to do on Monday. This is how to find the one or two things actually costing you candidates, what to change about them, and how to tell whether it worked, inside the wider candidate experience platform.
Book a free, no-obligation product demo call with our experts.
Find the worst cell, not the worst average
A company-wide candidate score of 7.4 gives you nothing to do on Monday. The same data cut by driver and stage usually points at one or two cells, and they are frequently the same problem wearing two names. Start there and ignore the rest of the grid this quarter. The candidate experience metrics covers what gets scored; the candidate experience journey map covers the stages.
Sample figures. Two weak cells, both at the offer stage, both about waiting. That is one fix, not two, and it is the only one worth starting this quarter.
Five things that account for most of the damage
Candidate feedback is remarkably consistent across organisations. These come up again and again, in roughly this order of frequency, and each one is on the candidate experience checklist as something to verify rather than assume. The candidate experience best practices set the bar each one has to clear.
Silence after an application
The most common complaint in candidate feedback is not rejection, it is never hearing anything. An acknowledgement that sets an expectation costs nothing and removes the largest single source of frustration.The offer wait
Candidates accept that decisions take time. What they do not accept is a week of silence after a final interview, when they are usually holding another conversation open.Interviewers who have not read anything
Being asked to repeat your CV to the third person in a process reads as disorganisation, and it is the single strongest driver of a poor fairness score.A role that was described loosely
Vague job descriptions cost you twice: weak applicants at the top, and new joiners at month three discovering the job is not the one they read about.Rejections with nothing in them
A rejected candidate who was treated well applies again and tells other people. The candidate experience survey covers rejected candidates for this reason, and they are the cohort most organisations never ask.
It finds the problem and proves the fix
Two jobs a dashboard does better than any workshop, and one it deliberately leaves to you.
Pinpoints the weak spot
Reports surface the strongest and weakest drivers and break them down by recruiter, hiring manager, job family and stage, so the problem has a location and an owner instead of being a company average.Proves the change worked
The same question, asked the same way, over three quarters is the only reliable evidence a fix landed. The platform holds that history so you can point at it in a hiring review.Compares you against you
No dependable external candidate benchmark exists, so your own history is the honest measure, and it is the one that actually tells you whether this quarter beat last. The candidate NPS page explains why.Suggests what to change
Weak drivers come with recommended actions attached, so the answer to a low score is a specific next step rather than a blank page. Which of them is right for your process is still your team's call.
Improving candidate experience, answered
How do you improve candidate experience?
Start by finding the specific weak point rather than trying to lift an overall score. Cut the feedback by driver and stage, take the worst one or two cells, and change one thing about them. In practice the recurring problems are narrow and well known: silence after an application, the wait after a final interview, interviewers who have not read the CV, loosely described roles, and rejections that carry nothing. Then leave the survey wording alone for a couple of quarters so you can actually tell whether the change worked. CultureMonkey shows you where the problem is and whether it moved, as part of a wider candidate experience platform.
What is the fastest thing to fix?
Acknowledgement after application, in almost every case. It is the most common complaint in candidate feedback, it affects the largest number of people because most applicants never get past that stage, and it requires no change to how you interview or decide. Setting an expectation you can keep, even a vague one, removes more frustration per hour of work than anything else on the list.
How long before an improvement shows in the score?
A quarter to see movement, two to trust it. Candidate cohorts are small compared with employee ones, so a single month's figure moves around a lot on sample size alone. The bigger risk is impatience: teams change three things at once, see the number rise, and cannot say which one did it, which means they cannot repeat it. One change per driver per quarter is slower and far more useful.
Does the platform tell us what to do about a weak score?
To a point. Weak drivers surface with recommended actions against them, so a low score arrives with a specific suggestion rather than leaving you to invent one, and scores break down by recruiter and hiring manager so the result has an owner. What the platform does not do is make the decision: whether to rewrite the job description, brief the panel differently or shorten the offer window depends on your process, and choosing between those is your hiring team's judgement rather than a workflow.
Is it worth improving the experience for candidates we reject?
Yes, and it is usually the highest-leverage group precisely because it is the largest. Almost everyone who touches your hiring process is rejected by it, so the reputation your employer brand carries is mostly built by people who did not get the job. They also apply again, and they talk to people who might. A rejection that arrives promptly and reads as though a person sent it is a low-cost change with an unusually long tail.
Should we survey candidates more often to improve faster?
No. More frequent surveying of the same small population lowers response rates and makes every figure noisier, which is the opposite of what you need when deciding whether a change worked. Keep one short survey per stage, keep the wording fixed, and let the quarters do the work. The candidate experience survey page covers how the stage program is run.
Find the one thing costing you candidates
Scored by driver and stage, tracked over quarters, on your own history.