Improving candidate experience in the DACH mid-market starts with the moments where qualified people wait, repeat data, chase appointments, or receive legally risky rejection messages. The practical answer is a shorter application flow, firm response deadlines, AGG-safe rejection wording, and early works council alignment wherever forms, scorecards, dashboards, or AI touch selection. Those four moves reduce drop-off rates, protect your kununu score, and keep you DSGVO- and EU AI Act-compliant — without replacing the existing ATS.

Most readers here are not starting from a blank sheet. You probably run a working ATS, have a works council that watches each new tool, and live with hiring managers who answer late while your kununu score makes the recruiting process visible to the labor market. The fixes below assume that reality and stay inside it. The pressure is real: according to the ManpowerGroup Candidate Experience Whitepaper 2026, only 14% of European companies rate their recruiting process as excellent, while application drop-off rates reach up to 30%.

Candidates remember small operational failures faster than any campaign, so the priorities below target the moments they feel directly.

Which application frictions lose DACH candidates first?

The first fixes should target the candidate's earliest effort and your first response. Long forms, broken mobile flows, slow updates, and scheduling delays tell applicants the employer will also be slow after hiring.

The numbers are clear. Indeed data on candidate experience shows that 49% of candidates find applications too long or too complicated. A Softgarden survey in Germany adds that 57.6% of applicants accept a maximum of ten minutes for data entry, 77.3% complain about missing feedback, and 61.2% about slow responses. Mobile is the second blind spot: Talention reports that 76.1% of jobseekers use smartphones to search for jobs, yet only about 33% of Germany's top 1,000 companies have integrated mobile recruiting into daily practice.

Before candidates reach a recruiter

Treat duplicate data entry as friction point one. Cut mandatory fields to contact details and role-critical information (target: under ten minutes), then push detailed screening into a later step. When standardized application questions change, prepare a works council packet under BetrVG §94 before launch, because the law treats personnel questionnaires as approval-relevant. A short, mobile-ready application flow maps strongly here: candidates apply on a smartphone without starting from a long CV upload.

Point two is the response gap after submission. Send an automatic receipt immediately and set a first human or status update within three to five business days. Recent Stepstone data on company ghosting in Germany shows that 64% of jobseekers have been ghosted and 54% cancel applications when feedback or progress updates are missing. If you add dashboards that compare recruiter or hiring-manager response times, involve the works council before those dashboards turn into performance-monitoring tools under BetrVG §87(1)6.

Point three is the generic rejection that arrives without care. Use stage-specific templates at the application stage and reserve more specific feedback for candidates who invested interview time. The fourth point is scheduling pingpong, where one candidate waits while three calendars are reconciled. Name one owner per candidate and offer self-scheduling slots, and absorb avoidable first calls by capturing a short pre-screen before calendars get involved.

From screening to interview closure

Point five is the silent holding pattern after screening. Trigger interim updates at fixed age thresholds, for example on day seven and day fourteen, so candidates are never left guessing. That matches expectations: candidate-flow.de reports that 56.7% of applicants see 14 days as the maximum acceptable response time, yet only 25% of German companies manage it. Point six is the unprepared interviewer who repeats the CV and asks inconsistent questions. Give every interviewer a one-page pack with the role criteria, the candidate context, legal no-go questions, and a decision deadline, and treat the introduction of standardized assessment principles as approval-relevant.

Point seven is missing rejection reasoning after an interview. Careful criterion-based feedback fixes this without exposing the company. The eighth point is the mobile application that technically exists but falls apart in real use. Test every priority role from a phone and remove upload steps that break on mobile. You will find the full action plan in the 30-day reset further down.

Measuring candidate experience: KPIs and benchmarks

What you do not measure, you will not improve. Six metrics are enough to make progress visible: cNPS, time-to-hire, application completion rate, response time, interview closure rate, and candidate CSAT. They all run out of your existing ATS plus a short candidate survey — no extra system required.

The cNPS thresholds and the rejected benchmark of avg. −7 come from Starred's cNPS benchmarks, the time-to-hire ranges from Metaview's EMEA recruiting benchmarks. One compliance note: once dashboards show individual recruiter or hiring-manager performance, this falls under performance monitoring per §87(1)6 BetrVG and must be cleared with the works council first.

Which candidate-experience failures damage kununu ratings?

The candidate-experience failures that reach kununu are usually the ones candidates can describe in one sentence. They waited for weeks, nobody explained the next step, the salary stayed hidden, or the employer disappeared after an offer.

The ninth friction point is a job description written for internal insiders. Remove abbreviations that only current employees understand, separate true requirements from preferences, and describe what the person will actually achieve in the role. Salary information belongs in that discussion now, because EU markets are moving toward pre-interview pay transparency and the candidate will check kununu before reading your ad twice.

Why kununu matters here: kununu's employer-branding research shows that 3 of 4 jobseekers use employer-review portals as a central source and 83% of users read employer comments. A single weak rejection or weeks of silence becomes a public artifact that the next candidate finds before applying.

The tenth point is full candidate ghosting. Require every application to end in a documented disposition, even when the rejection itself is automated. Candidates who attended an interview should receive a more personal close, because they have already given the company time and attention.

The eleventh point is salary opacity. Prepare ranges or pre-interview pay information and stop asking candidates about pay history. The gap is large: only about 15.8% of German job ads currently include salary information — exactly what kununu users actively look for. For mid-market companies, that usually means a pay-band project behind the scenes rather than a quick edit to a job ad.

The twelfth point is weak post-offer onboarding. Candidates still judge the experience after signing, especially when equipment, access, or manager contact falls through before day one. Treat pre-boarding as the final recruiting stage and make the manager responsible for a short start plan that ideally fires on signature rather than on day one.

How should AGG rejection letters explain decisions?

AGG-safe rejection letters should point only to documented job-related criteria. They must not mention age, gender, pregnancy, family status, disability, health, religion, ethnicity, nationality, or sexual identity as a reason for the decision.

At the application stage, a short rejection is often safer than a detailed explanation if you have not yet documented a clear criterion. After interviews, candidates deserve more closure, but the explanation should still tie back to the advertised requirements. A safe sentence can say that another candidate matched a specific required experience more closely, without inventing a new criterion after the fact.

The risky wording is rarely openly hostile. It usually sounds harmless: culture fit, resilience, dynamism, language preference, physical suitability. As the careerbuilder.de guide on AGG rejection wording shows, those words become dangerous the moment they imply a protected trait. Give recruiters and hiring managers forbidden examples so they stop improvising under time pressure, and capture the documented reason in the ATS as the rejection is sent.

Rejection timing also matters operationally. Under §15(4) of the AGG, applicants have two months after receiving the rejection to assert claims. This is not legal advice, but friendly wording will not save you if the underlying reason is poorly documented.

Closely related is how long you keep applicant data. As the data protection authority explains, with the AGG litigation window in mind, applicant records should generally be kept for six months after the process closes and deleted afterward — longer storage, for example for a talent pool, needs consent. Anchor this deletion rule in the ATS so it does not get lost in daily operations.

When must works councils approve recruiting fixes?

Works council approval becomes likely the moment you change what candidates must answer, how interviewers assess them, how selection rules work, or how a technical system can monitor employees. Process promises alone are usually easier to land than tools and scorecards, which need earlier preparation.

Treat application questionnaires and structured interview forms as approval-relevant under §94 BetrVG, which covers personnel questionnaires and general assessment principles. The same care applies once you introduce general assessment principles, because at that point the company is no longer just improving communication. It is changing how people are evaluated.

Selection guidelines can trigger §95 BetrVG. Important for 2026: as Haufe explains on AI participation of the works council, §95(2a) BetrVG now states explicitly that selection guidelines are approval-relevant even when AI is used to set them up. So keep humans responsible for the final decision and document how the scoring works. Our GDPR and works-council checklist for talent-management software in DACH walks through the same documentation logic for adjacent people-data tools.

Dashboards need their own check. If a recruiting workflow shows which recruiter, hiring manager, or interviewer missed deadlines, the works council may read that as employee monitoring under §87(1)6. A useful sign-off packet explains the purpose, the candidate questions, the scoring logic, the retention period, the access rights, and the human decision rule.

What changes in 2026 under EU Pay Transparency and the EU AI Act?

Two EU rule sets hit DACH recruiting directly in 2026. The EU Pay Transparency Directive requires pay information before the interview, and the EU AI Act classifies recruiting AI as a high-risk system. Both change what good candidate experience has to look like.

EU Pay Transparency Directive (deadline: 7 June 2026)

The directive obliges employers to give applicants an initial salary figure or a pay range before the interview — the job ad is one allowed way to do that. Asking about pay history is banned. As remoteworkeurope.eu reports, the transposition deadline falls on 7 June 2026, yet Germany has not passed a national implementation law; the directive takes effect regardless. The framework for gender pay-gap reports and thresholds is described in the Ogletree pay transparency update for Germany.

For candidate experience, this is an opportunity: applicants decide better informed and drop off less often after the first interview. Operationally it means preparing the pay-band architecture internally before you change the first ad — otherwise pressure builds without a clean data foundation.

EU AI Act: recruiting as a high-risk system (core duties from 2 August 2026)

AI in recruiting — screening, ranking, CV filtering, video-interview analysis — counts as a high-risk system under Annex III of the EU AI Act. The core duties for such systems — documentation, audits, human oversight, EU registration — apply from 2 August 2026; prohibited practices such as emotion recognition have been banned since February 2025. As a practical guide to the EU AI Act in recruiting explains, candidates also gain a right to explanation and to contest a decision.

This is where the interplay with the GDPR comes in: Art. 22 GDPR gives candidates the right not to be subject to decisions based solely on automated processing with significant effects. In practice: no fully automated rejection process, always a human decision at the end. And the works council stays in play — §95(2a) BetrVG applies to AI-supported selection guidelines too.

What belongs in a 30-day candidate-experience reset?

A 30-day reset should fix the moments candidates feel immediately, while you park heavier projects for a second phase. Start with mobile testing, response deadlines, KPI measurement, rejection wording, and one simplified high-volume pilot.

Longer programs sit behind that reset: scorecards, pay-band architecture, HRIS integrations, AI documentation, and onboarding redesign. The pay-band work matters sooner than many teams expect, because the EU Pay Transparency Directive 2023/970 requires applicant pay information before interview or in the job notice and sets 7 June 2026 as the transposition deadline.

Where does a mobile-first or voice-first application solution fit?

A mobile-first or voice-first layer fits the front door of recruiting, not as a rip-and-replace ATS project. It helps where candidates abandon long forms, struggle on mobile, or wait for a first screening slot.

Most DACH mid-market HR teams keep their core systems. Some run Personio or SAP SuccessFactors, others rely on rexx or P&I LOGA, and the practical question is whether you can improve the candidate entry point without rebuilding the whole stack. For most teams the answer is yes, because the application moment is reachable from a widget layer.

What DACH buyers should watch for: EU hosting, GDPR alignment, and EU AI Act-aware documentation before scaling a screening tool. These compliance prerequisites decide in practice whether a tool gets through the works council and data protection at all. The same care is advisable for any new HR software — from integration depth to the deletion and oversight concept.

The quieter work behind better hiring

Candidate experience improves when HR runs it as a controlled operating process, not as a tone exercise. The same change that feels polite to a candidate often needs a legal wording check, a works council explanation, and a system owner who makes sure the promise actually fires inside the ATS or widget.

The fastest improvements are honestly not the most glamorous ones, but candidates feel them within days. Compliance work should not slow the reset down if you prepare questions, scoring, retention, and human oversight early in the project. A better application front door can also protect employer reputation while the larger HRIS stack stays in place, which is the realistic path for most DACH mid-market teams.

Start with one role where the pain is visible and the volume is high. Measure the current form length, response time, interview closure time, and rejection quality, then ship the 30-day reset before expanding to scorecards or pay-band work.

Frequently Asked Questions (FAQ)

Can we improve candidate experience without replacing Personio or SAP SuccessFactors?

Yes, candidate experience improves significantly without replacing the core ATS or HRIS. Start with changes that sit around the system: shorter forms, clearer status messages, AGG-reviewed templates, self-scheduling, and a mobile-first application widget. This improves the candidate entry point while the company keeps its existing HR stack and avoids a multi-quarter migration project.

How do you measure candidate experience?

Through a few clearly defined KPIs: candidate NPS (cNPS) for willingness to recommend, time-to-hire, application completion rate, response time to the first reply, interview closure rate, and candidate CSAT. All of them run out of the existing ATS plus a short candidate survey. As a guide: a cNPS of 30–70 is excellent, and a drop-off rate above 30% is a warning sign.

How fast should recruiters send the first status update?

Recruiters should send an immediate confirmation and a first real status update within three to five business days. 56.7% of German applicants see 14 days as the maximum acceptable, yet only 25% of companies hit that. For longer processes, schedule interim updates at fixed thresholds rather than waiting for a final answer.

Which rejection wording is unsafe under the AGG?

Rejection wording becomes unsafe when it names or implies a protected trait as the reason for the decision. Avoid references to age, gender, pregnancy, family plans, disability, health, religion, ethnicity, nationality, or sexual identity, and watch for soft phrases like "culture fit" or "resilience" that hint at the same traits. Safer wording points to documented job-related criteria from the role profile.

Does the EU Pay Transparency Directive require salary ranges in job ads?

The directive requires employers to give applicants initial pay information or a pay range before the interview, and the job ad is one allowed way to do that. It also bans asking candidates about pay history during the process. The transposition deadline falls on 7 June 2026; Germany has not yet passed a national law, but the directive takes effect regardless.

How long may applicant data be stored?

With the AGG litigation window in mind, the general rule is to keep applicant records for around six months after the process closes and then delete them. Longer storage, for example for a talent pool, is only permitted with the applicant's explicit consent. Anchor this deletion rule directly in the ATS.

What counts as high-risk in recruiting under the EU AI Act?

High-risk covers AI systems that filter applications, rank or screen candidates, and analyze video interviews. The core duties — documentation, audits, human oversight, and EU registration — apply from 2 August 2026. Prohibited practices such as emotion recognition have been banned since February 2025.

When should we involve the works council for voice screening?

Involve the works council before voice screening changes the questions candidates answer or the way the company scores candidates. Standardized questionnaires and assessment principles can trigger approval rights under BetrVG §94, and AI-supported selection guidelines fall under §95(2a) BetrVG. Bring the purpose, question set, scoring logic, retention rules, and human decision process into the discussion from the start.

How do we stop ghosting when hiring managers delay feedback?

Stop ghosting by making closure a process requirement rather than a recruiter preference. Set a decision deadline after each interview and trigger candidate updates automatically when hiring managers miss it. If dashboards track individual manager responsiveness, check works council requirements under §87(1)6 BetrVG before using them as performance tools.