Checklist for a candidate-friendly application process: 10 points

Your hiring process costs you good candidates without you noticing. Candidates drop out before the first interview, not because of the role, but because of an unclear, slow, or overly burdensome process. Use this checklist to assess how candidate-friendly your process is. Go through the points before you publish a job opening, during the process, and after a rejection. Each point is an action you can implement today. The checklist follows three phases and ends with the three points employers skip most often. For more background, read what candidate experience is and why it matters.

Before the job posting goes live

• The job posting describes the first workweek and the team, not just requirements.
  Why: A list of 25 requirements scares candidates off. For a mid-level data engineer in Rotterdam, describe the Monday and Tuesday: checking port logistics, building a dashboard with two colleagues. For example: "On Monday, you check the port logistics data, and on Tuesday, you work with two colleagues on a dashboard for the business." This attracts candidates who want to do the work, not just hold a title.
  
• Your application form asks only for information you currently use.
  Why: Every extra field costs time and increases the number of abandoned applications. Don't ask for a cover letter if you don't read it, for example for hospitality staff in Utrecht. A resume, name, and phone number are enough for an initial screening. Whatever you need later, ask for in the interview.
  
• Your job posting includes a salary indication or a clear range.
  Why: This prevents disappointments and saves questions about salary during the first contact. A range of EUR 3,200 to 3,800 per month is concrete and shows you're not hiding anything. Candidates far above or below the range won't apply, which saves you screening time.
  

During the application process

• You confirm every application immediately and state a response time.
  Why: Silence is the main reason candidates drop out. An automatic confirmation within five minutes keeps the candidate engaged. In it, mention when the candidate will hear a decision at the latest, for example by Friday. That way the candidate doesn't remain in uncertainty.
  
• You plan a maximum of three interview rounds and communicate the structure in advance.
  Why: A six-week process with four rounds costs you good candidates. Tell a candidate for a healthcare role in Eindhoven the steps: phone introduction, interview with the team lead, short practical assignment. That way the candidate knows what to expect. Long procedures feel like stalling, even if that's not your intention.
  
• You send practical information no later than 48 hours before the interview.
  Why: Location, names, duration, and preparation reduce stress and show that you're organized. A message saying "You'll speak with Jan de Vries, team lead, for 45 minutes" is enough. Also mention whether the candidate needs to bring anything, such as a portfolio.
  
• You give an update within five business days after each interview.
  Why: A candidate who hears nothing will keep applying elsewhere. A message saying "we're still in conversation with two candidates, you'll hear by Friday" keeps motivation alive. After a week of silence, the candidate wonders whether the process is still ongoing. Also read how to prevent good candidates from dropping out during the process.
  

After the interview and at the rejection stage

• You also ask rejected candidates for feedback about the process.
  Why: Rejected candidates see weaknesses you miss, such as unclear directions or silence after the second interview. A short survey with two questions is enough: what was clear, what could be better? Send it within two days after the rejection, while the experience is still fresh.
  
• You reject candidates personally and respectfully, with a concrete reason.
  Why: Ghosting damages your employer brand. For example, mention that another candidate had more experience with warehouse processes. That honesty costs nothing and ensures the candidate doesn't remember your company negatively. A standard email without a reason feels like a rejection without recognition.
  
• You keep strong candidates who just missed out in your talent pool.
  Why: A candidate who isn't quite the right fit now could be the right person for a new role in six months, such as an assistant accountant in Amersfoort. Record why someone was rejected and which role would suit them. Read more about maintaining motivation in how to keep candidates motivated during the application process.
  

The most frequently skipped points

• Salary indication in the job posting.
  Why: Many employers avoid this, but it filters on both sides and saves time in screening.
  
• Asking rejected candidates for feedback.
  Why: It takes five minutes per candidate and gives you direct improvements for your next job posting.
  
• Rejecting with a concrete reason.
  Why: A standard rejection without an explanation feels like ghosting. Candidates share that in reviews, which costs you future applicants.
  

How to approach this

Start with the three most frequently skipped points. Choose one open job posting and go through the points before publishing. Ask the candidate for feedback immediately after the next rejection. Small adjustments increase the number of candidates who complete the process. Start with one job posting and count the number of completed applications after a month.

If you want to store candidates centrally and automate updates, Applyfin helps with a shared candidate database and automatic actions per pipeline stage. You keep strong candidates in a talent pool and see the full history per candidate. Read more about this on the product page about collaboration in the hiring team.