What is candidate experience?
What candidate experience is, where it starts and ends, why it decides who applies for frontline roles, and what a good one looks like on a phone.
Candidate experience is everything a person meets between first seeing one of your roles and hearing what happened to their application: the job page, the application itself, the answers to their questions, and the silence in between. It matters because it decides who applies at all, and for frontline roles most of that decision is made on a phone in a few minutes, long before anyone on your team knows the person was there.
That second part is the one most teams underestimate. When people talk about candidate experience they often mean the interview, the feedback email or the offer call. Those matter, but by the time you reach them you are only talking to the people who got through the front door. The bigger question is who never did.
Where it starts and where it ends
It starts earlier than most process maps do. A candidate’s first impression is usually a listing on Google, Indeed or an aggregator, and the second is whatever loads when they tap it. If that page is slow, built for a desktop, or drops them into a login screen for a system they have never heard of, the experience has already gone wrong, and nothing you do in the interview will reach them.
It ends when the person hears a decision, whether that is an offer, a no, or a nudge towards a role that suits them better. Everything between those two points counts, including the parts nobody on your team ever sees: the question someone wanted to ask at eleven at night about shift patterns, the form field they could not answer, the week they spent wondering whether anyone had read their application.
Why it decides who applies
A candidate for a kitchen, shop floor, leisure or care role is rarely comparing your process with a competitor’s process. They are comparing it with the last thing they did on their phone. Ordering food takes a minute. Booking a train takes two. If applying to work for you takes twenty, asks for a CV they do not have to hand, and repeats questions they have already answered, they will leave, and the people most likely to leave are often the ones with the most options.
This is also why candidate experience is a cost question and not only a brand one. The money you spent getting someone to the job page is gone whether or not they finish. A process that loses most of its visitors before they apply makes every channel look more expensive than it really is, and it quietly skews who you end up hiring towards the people with the most patience rather than the best fit.
What we see go wrong most often
Three failures do most of the damage, and they are remarkably consistent across hospitality, retail, leisure and healthcare employers.
The first is the application. It is usually the ATS’s own form, designed around the recruiter’s data model, identical for every role and unforgiving on a small screen. A barista and a regional manager get the same questions in the same order.
The second is unanswered questions. Candidates want to know about pay bands, shift patterns, whether a role suits a student, and how far the site is from home. Careers sites rarely answer these, and nobody is around to answer them on the weekend or the evening a frontline candidate finally has time to look.
The third is silence. Applications land in a queue that nobody has time to read in full, so even the people who did everything right often hear nothing, and they remember that.
What good looks like
A good candidate experience is not complicated to describe. The careers site loads quickly on a mid-range phone and meets WCAG 2.1 AA, so nobody is excluded by the design. A candidate can find a role by describing what they want rather than paging through a list. The application adapts to the role and the region, asks only what that job genuinely needs, and finishes in minutes. Questions get answered from the employer’s own approved content, whatever the hour, and anything that needs judgment goes to a person. The finished application lands in the ATS the team already uses, and the candidate knows what happens next.
The evidence for fixing the front of the process is consistent. When Compass Group rebuilt its application with us, it saw 42% more completed applications, and you can read how in the Compass Group story. PureGym’s application now completes in under a minute. In both cases the ATS stayed exactly where it was. What changed was what the candidate met.
How inploi approaches it
We think of candidate experience as a handful of things that have to work together rather than a single product. Careers sites that are fast, accessible and carry every brand and language you hire in. Conversational apply, an application that adapts to the role and finishes in one thread. The Candidate Agent, which answers questions from your policies while the candidate is still deciding and hands to a person when judgment is needed. And job distribution, so each role reaches the people who might actually want it. All of it sits on top of your existing ATS, which stays the system of record.
Where to start
If you want to know how your own candidate experience is doing, start with the numbers you probably already have but rarely look at together: how many people land on a job page, how many start an application, how many finish, and how long it takes them. Then apply for one of your own roles on your phone, on the bus, and see how it feels. The gap between those two views is usually where the work is.
We have written more about the problem, and what fixes it, on our page about candidates dropping off before they apply, and the rest of our thinking on the subject lives under candidate experience.
