The candidate experience journey, stage by stage
A candidate experience journey map is only worth drawing if it records what actually happened at each stage. This is the shape most hiring funnels take, where listening belongs at each touchpoint, and where the journey really ends, inside the wider candidate experience platform.
Book a free, no-obligation product demo call with our experts.
Five stages, and only one of them is the interview
Most hiring funnels take roughly this shape. Teams tend to measure the interview because it is the part they run, and leave the application form and the offer window unmeasured, which is where most of the damage is done. The candidate experience checklist covers what to verify at each one.
Application
Was it clear what the role was, and how long the form tookScreening
Whether the first conversation told them anything they could not have readInterview
Fairness, preparation, and whether the panel seemed to have read anythingOffer
Speed, clarity of the package, and how the negotiation feltJoining
Whether the job matches what was described, asked once they are in
A journey map is only useful if it is drawn from what happened
A candidate experience journey map drawn in a workshop is a record of what your team believes the process feels like. The same map drawn from stage surveys is a record of what it actually felt like, and the two are rarely the same document. The candidate experience metrics are what fill it in.
Sample figures. The two only part company at the offer stage, which is exactly the part of the process a hiring team never experiences itself.
A candidate lands on a stage from your own data
Stages are not typed in by a recruiter. Candidate records come in through the API, and which stage a candidate belongs to is resolved from the fields you send, combining several of them under conditions set for your account. That is what keeps a journey map current without anyone maintaining it.
The journey does not stop at the offer
The last touchpoint most maps show is acceptance. The one that predicts whether the hire stays is the gap between what was described in hiring and what they found in the first week.
Joining day is a real boundary
Date of joining is a field on the candidate record, which is what lets the last candidate survey and the first employee one be two points on one line rather than two programs. The hiring manager feedback survey fires on the same date.The promise gets checked
Asking after a few weeks whether the role matches what was described is the only way to catch a hiring process that oversells.Rejected candidates are part of the map
A journey map drawn only from people who accepted is a map of your best case. The candidate experience survey covers candidates you turned down and candidates who declined.One score across the whole line
Because the calculation matches your employee score, candidate NPS at the offer stage and eNPS at month three read on one axis.
The candidate journey, answered
What is a candidate experience journey map?
A candidate experience journey map sets out every stage a candidate passes through, from first seeing the role to their first weeks in the job, and records what the experience was like at each one. It is sometimes called a candidate journey map or a candidate experience roadmap. The version worth having is drawn from what candidates reported at each stage rather than from what the hiring team assumes happens, which is the difference between a workshop artefact and a working document. CultureMonkey builds it from stage surveys inside a wider candidate experience platform.
What are the stages of the candidate journey?
Most funnels run application, screening, interview, offer, and joining, though the names and the number vary by organisation and by role. CultureMonkey does not impose a fixed list: which stage a candidate is in is resolved from the data you send about them, using conditions configured for your account, so the stages match your process rather than a template. What matters more than the count is that each stage has its own survey, because a single survey at the end averages five different experiences into one number.
How do you measure the candidate journey?
One short survey per stage, asked while the stage is fresh, scored on the same drivers throughout so the stages are comparable. Reading it, the useful move is down a column rather than across a row: a driver that holds up through application and screening then falls at offer is a specific, fixable problem, where the same driver being weak everywhere is a cultural one. The candidate experience metrics covers what to score, and candidate NPS is the number that compares across stages.
Where does the candidate journey end?
Later than most maps show it. Acceptance is where recruiting stops measuring, but the gap between what hiring described and what the new joiner actually found is only visible once they are in the job. Date of joining is held on the candidate record, so the final candidate survey and the first employee survey sit on one continuous line rather than in two disconnected systems.
Should the journey map include candidates who were rejected?
Yes, and leaving them out is the most common way these maps mislead. A map drawn only from people who accepted an offer describes your best case and hides the stages where you lose people. Rejected candidates and those who declined reached real stages and had a real experience of them; excluding their answers also quietly inflates every score.
See the journey drawn from what candidates actually said
Every stage scored on the same drivers, running through to day one.