Employer Brand

Candidate Experience Guide

Candidate experience is how applicants are treated once they enter your process, and it is mostly a logistics problem rather than a communications one. The recurring failures are the same in most companies: a long application form, silence after submitting, slow scheduling, interviews nobody prepared for, and rejections that never arrive. Each one is fixable with a rule and an owner.

Where do applicants actually drop out of your process?

Measure it before guessing. The funnel worth instrumenting has six points: job view, application started, application submitted, screened, interviewed, offer. In most companies the largest single loss sits between started and submitted, which is a form problem rather than an interest problem, since those people had already decided to apply. The second largest sits between submitted and first human response, where silence does the damage. Pull the numbers per role and per source rather than as one site-wide figure, because a high-volume role and a hard-to-fill specialist role fail in completely different places. Then count the population nobody counts: applicants who never received any decision at all. Most candidate management software can report stage-to-stage conversion and time in stage, and the report takes an afternoon to build. Do that first. Every later fix in this guide is cheap once you know which two stages are losing people, and expensive guesswork before you do. Repeat the measurement a month after each fix rather than assuming it worked. Drop-off moves around, and closing one gap frequently exposes the next one.

How long should an application take, and what should it ask?

Minutes rather than tens of minutes, and it should ask only what genuinely feeds the first screening decision. Every field is a toll. The usual offenders are compulsory account creation before a first application, re-typing a work history that is already in the attached resume, long free-text essays nobody reads, demographic questions presented with no explanation of why they are asked, and a form that breaks on a phone keyboard. Parse the resume and let the applicant correct the parsed result instead of typing it twice. Keep required fields to identity, contact details, the attachment, work authorisation where you legally need it, and at most two role-specific questions that actually change the screening decision. Offer save-and-resume for anything longer. Then apply for your own job, on your own phone, on a normal connection, and time it. A modern applicant tracking system supports all of this by configuration, so a twenty-minute application is almost always a choice somebody made rather than a limitation of the software. If a field exists because a report needs it, collect it later from the smaller group that reaches an interview.

What should a candidate hear from you, and when?

Write a communications matrix and hold to it: every stage, the message, the owner, and the maximum wait. At minimum, somebody should get an immediate confirmation on submitting that states when they will hear back, a decision after screening, a clear invitation with logistics before any interview, an outcome after each stage inside the window you promised, and a final answer either way. Promise a window you can actually hold, because a realistic two-week promise beats a broken three-day one. Automate the mechanical messages through your recruitment automation and keep the human stages human: anybody who has spoken to a person should hear back from a person. Give a named contact and an obvious way to ask where things stand without feeling like a nuisance. Timing beats wording almost every time. A plain message that arrives on the day you said beats a beautifully written one three weeks late, and people forgive delay far more readily than silence. Tell people what the next step is inside every message, including the rejection, because the commonest complaint is not knowing where a process stands.

How do you reject people without burning them?

Send the rejection. The silent close is the most complained-about behaviour in hiring, it costs almost nothing to fix, and it comes down entirely to whether anybody owns the queue. Keep the message short, name the stage they reached, and never promise feedback you will not deliver. Match the effort to the investment: an automated note is acceptable after an application, a personal message is the minimum after somebody spent an afternoon with your panel, and a phone call is right for a rejected finalist. Offer specific feedback where you genuinely can, bearing in mind that what may be said varies by jurisdiction and company policy, so agree the boundaries with HR or counsel rather than leaving each recruiter to improvise. Never dress a template up as personal, since people recognise it and the pretence costs more than the template would have. Add strong rejected candidates to talent pool software with a note on why, because this role's runner-up is often the next role's fastest hire. Set a maximum age for anyone sitting without a decision and review that list weekly, because backlogs rebuild quietly.

Why does scheduling cause so much of the delay?

Because it is a many-calendar problem being solved over email by somebody who controls none of those calendars. Every reschedule restarts the loop, and each loop adds days that resurface later as somebody accepting an offer elsewhere. The fixes are mechanical rather than clever. Ask interviewers to hold recurring availability blocks so slots exist without a negotiation. Send self-scheduling links so people pick from real openings instead of proposing times into a void. Build panel templates per role so nobody reassembles the sequence from memory. State time zones explicitly in every invitation and test the meeting link before sending it. Agree a reschedule policy covering who tells the candidate and how quickly. Name one owner for scheduling on each search, since shared responsibility is exactly why a message sits unanswered for two days. Dedicated interview scheduling software removes most of the back-and-forth, though the real constraint is availability: no tool can book a panel whose members have offered no time. Track scheduling cycle time as its own number, from stage approval to a booked interview, because it hides inside time to hire.

What should candidates be told before an interview?

Everything needed to prepare properly, sent at least a day ahead in a single message. Who they will meet, with names, job titles and profile links, so nobody walks in blind. The format and the length. What is being assessed in this specific session, since that differs by stage. What to prepare or bring. Whether a take-home exercise is involved, roughly how long it should take, and whether it is paid. How to request an adjustment or accessibility support. The dial-in details, or the building address with a floor and a phone number that somebody answers. What happens next and when. Sending this brief has a second effect nobody expects: it forces the panel to decide what each session is actually for, which improves the interview itself. None of it is complicated. It is a saved template with five variables, and the difference in how prepared people arrive is obvious within a fortnight to the interviewers who resisted writing it. Send it from a named person with a reply address somebody monitors, because a no-reply invitation tells the recipient exactly how much attention to expect.

What happens between offer accepted and the first day?

This is the gap nobody measures and the one where accepted offers quietly evaporate. A signed acceptance is not a start date, particularly where notice periods run long and a counter-offer arrives the same week. Keep contact deliberate rather than incidental. Name one person who checks in on an agreed rhythm. Get paperwork, background checks and equipment ordering moving immediately, because those delays are what make a company feel disorganised before day one. Have the hiring manager call within the first week of acceptance, not the week before the start date. Send the first-week plan in advance so the person can picture arriving. Ask directly whether a counter-offer has appeared, since that conversation is far easier before it is accepted than afterwards. Invite them to a team event where that fits. Renege risk rises with the length of the gap, which makes shortening it a genuine lever, and everything else here costs a few messages a week from somebody who has already been assigned to send them. Track the gap between acceptance and start as its own number, and treat anything over a month as needing active contact.

How do you measure candidate experience without guessing?

Use two surveys and four operational numbers, and treat the operational numbers as the more honest half. Survey at the point of rejection and again after an offer decision, keeping it to three rated questions and one open box, because long surveys sent after a rejection go unanswered. Response bias runs against you: the people who had the worst experience are the least likely to reply, so read the free text for repeated themes rather than treating the average as precise. Candidate net promoter score is directional at best, and comparing yours against a published benchmark is close to meaningless given how differently these surveys are administered. The operational numbers are harder to argue with: time to first response, the percentage of applicants who received any decision, average time in each stage, and scheduling cycle time. Purpose-built candidate experience software helps with collection, but the discipline that matters is reviewing the results monthly with the people able to change the process. Share the verbatim comments with recruiters each quarter, because one honest complaint changes more behaviour than an average score does.

Hiring while you work through this?

How to put this into practice

  1. 1 Apply for your own job on a phone Use a personal device on a normal connection and time it end to end. Note every place you hesitated, retyped something, or needed a document you did not have. That list is your first backlog, and it usually takes twenty minutes to produce.
  2. 2 Instrument the funnel stage by stage Report conversion and time in stage from job view through to offer, broken down by role and source. Add one number nobody tracks: how many applicants have never received a decision. Publish both alongside your existing hiring reports.
  3. 3 Cut the application to what you screen on Remove every field that does not change the first decision, drop compulsory account creation, and let resume parsing fill the work history. Re-time the application afterwards and compare the started-to-submitted rate against the previous month.
  4. 4 Write the communications matrix One row per stage: the message, the owner, the maximum wait. Automate the mechanical notes and keep the post-conversation messages personal. Publish the promised timelines publicly so the commitment is visible to candidates as well as internally.
  5. 5 Clear the silent rejection backlog Close out everybody sitting in a stage with no decision, starting with anyone who reached an interview. Then assign permanent ownership of the queue so it never rebuilds, and check the count weekly rather than quarterly.
  6. 6 Fix scheduling at the source Get recurring availability blocks from every regular interviewer, switch to self-scheduling links, and build a panel template per role. Measure scheduling cycle time before and after, since this is usually the fastest visible improvement available.
  7. 7 Run the two surveys and review them monthly Send a short survey at rejection and after an offer decision, then review the themes with recruiters and hiring managers every month. Pair it with the operational numbers so the discussion is about process rather than about tone.

Mistakes worth avoiding

  • Requiring an account and a retyped work history when the attached resume already contains all of it.
  • Promising feedback in a rejection template and then never sending any, which is worse than promising nothing.
  • Leaving people who reached a final interview to work out for themselves that they did not get the job.
  • Scheduling by email chain across three calendars, then recording the resulting delay as candidate unresponsiveness.
  • Sending an interview invitation with no agenda, no interviewer names and no indication of the format.
  • Surveying only the people you hired, which measures the one group guaranteed to describe the process positively.
FAQ

Candidate Experience Guide — FAQs

What is candidate experience? +
Everything an applicant encounters from the moment they engage with a role through to their first day or their rejection: the application form, response times, communication, interview logistics, feedback, the offer conversation and the wait before starting. It is distinct from employer brand, which is the perception formed before applying. Candidate experience is what happens after they enter the process. Both matter, and they fail for different reasons and get fixed by different people.
How long should a job application take to complete? +
For most roles, a few minutes. Identity, contact details, a resume, work authorisation where legally required, and at most two questions that genuinely change the screening decision. Anything longer needs a reason you could defend to the applicant. Test it by applying for your own role on a phone and timing it, then compare your started-to-submitted rate before and after cutting fields. Keep the same test in your release checklist for any future form change.
Should you give feedback to rejected candidates? +
Give it to anyone who reached an interview, and keep it specific and short. For applicants rejected at resume stage, a prompt clear decision is usually more valuable than generic feedback. What you may say varies by jurisdiction and company policy, so agree the boundaries with HR or counsel first. The rule that matters most is never promising feedback you will not send. Consistency across candidates matters more than depth in any one reply.
How quickly should you respond to an application? +
Immediately with an automated confirmation that states a realistic timeline, then with a real decision inside that timeline. Many teams aim for a first human response within a week, though the promise matters more than the number: a held two-week commitment beats a broken three-day one. Track time to first response beside your other [recruitment metrics](/recruitment-metrics). Publish the promised window on the careers page so the commitment is visible to applicants.
What is candidate net promoter score? +
A single question asking how likely somebody is to recommend applying to your company, scored zero to ten and converted into a net figure. It is useful for tracking your own direction over time. It is close to useless as a comparison against another company, because administration, timing and audience differ so much. Read the free-text comments for the actionable content. Ask it at the same point every time or the trend means nothing.
Do candidates really abandon long applications? +
Measure it in your own funnel rather than trusting a quoted figure. Compare application starts to submissions, then shorten the form and compare again. The started-to-submitted rate is the number that answers this for your roles, your audience and your market, and it responds quickly enough that you can see the effect within a month or two. Change one thing at a time, since two simultaneous changes leave you unable to attribute the difference.
Should you tell candidates the salary range early? +
Publishing or sharing a range early prevents processes that collapse at offer stage and saves everyone weeks. Some jurisdictions now require pay ranges in job advertisements and others do not, and the rules change, so confirm what applies where you advertise with qualified employment counsel. Where you are not required to publish, sharing the range at first contact still removes a common cause of late-stage failure. Decide once, then apply it to every role.
How do you keep rejected candidates warm for future roles? +
Record why they were rejected and what they were strong at, tag them by skill and level, and ask permission to keep in touch where your data rules require it. Then contact them individually when a genuinely relevant role opens, referencing the previous conversation. A generic mass email to a rejected pool performs badly and reminds people they were rejected. Keep the pool small enough that the outreach can stay individual.
Built for recruiters & hiring teams

Put this into a process that runs itself

See how Pitch N Hire handles the parts of this that eat a recruiter's week — posting, screening, scheduling and keeping every decision in one place.

Prefer to talk? Book a demo · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo