The Salary Mismatch That Wastes Three Interview Rounds

The hidden variable in most “candidate declined salary” codes

When a strong finalist declines because of pay, the immediate explanation is often “expectations too high.” But the original error may be an unapproved salary band, a mismatched level or a bonus presented as guaranteed salary. The consequence is interview hours expended on a role whose realistic offer was never aligned.

Use a compensation decision record instead of a vague budget field: grade, country/currency, base minimum and maximum, permitted positioning within the range, variable-pay target and conditions, equity treatment if relevant, approval authority, and expiry date. “Up to 100k” is not sufficient unless the organization can explain the conditions for reaching that amount.

Do not ask for past salary to solve a pay-banding problem

The EU Pay Transparency Directive 2023/970 requires information on initial pay or its range for applicants and prohibits questions about their pay history under its framework. The transposition deadline was 7 June 2026; the precise local implementation and enforcement require a country-specific check. The directive is not interchangeable with UK or US rules. Read Article 5.

Even where salary-history questions might be permitted, they are a poor substitute for valuation. A prior employer may have underpaid someone or compensated them using a different mix of location, equity, benefits and risk. Ask what the candidate would need to consider the new role and, more importantly, disclose what the organization has actually approved.

Useful language: “The approved base range for this level is €70k–€85k gross annually, with separately described variable compensation. Does this make sense for the scope and location? If not, we can check a different level before asking you to interview.” No implied request for current salary.

Why a numerical overlap is necessary but not sufficient

Suppose the approved base range is €70k–€85k and a candidate states that €82k–€95k is the base-pay range they would consider. The arithmetic overlap is €82k–€85k. This is a conversation window, not evidence the person will accept €82k: positioning, location, sign-on pay, competing offers and role scope still matter.

Conversely, if the approved range is €70k–€80k and the stated minimum is €88k, do not book multiple interviews on the theory that “they might come down.” Either clarify a genuinely different grade or seek authorized budget review. Do not present an unapproved exception as a promised offer.

Currency and units must match. Base/year versus total compensation/year, full-time equivalent versus part-time actual pay, local currency versus a converted estimate and contractor day rate versus employment salary cannot be compared by subtracting the displayed numbers.

A decision matrix that the client can actually approve

Pay transparency professionals recommend setting realistic ranges and using consistent factors such as job architecture and experience. That is stronger than arbitrary negotiating headroom. WorldatWork guidance.

The five-minute recruiter conversation before assessments

1. Confirm the candidate has the correct level and location; changes can affect range and law.
2. State the employer-approved base range, currency, pay period and whether bonuses are target-based or guaranteed.
3. Ask whether that disclosed scope is worth discussing; allow the candidate not to disclose an exact number.
4. For mismatch, record the reason class, not a speculative conclusion (“candidate greedy”).
5. Escalate scope or budget to an authorized owner; ask permission before recontacting after the change.

A recruiter should not turn a first-call compensation conversation into an aggressive reverse auction. The purpose is to prevent avoidable mismatch while preserving equitable pay setting. Where regulated reporting applies, HR/legal must review local duties.

Worked example: bonus math conceals an €8k gap

Illustrative, not market evidence. A client authorizes €76k base plus a discretionary bonus target of €12k. The recruiter calls it “up to €88k.” A candidate’s stated minimum is €84k base because rent, mortgage and predictable cash flow must be covered. There is no demonstrated base overlap, even though €88k appears greater than €84k.

The fix is a scope clarification and a written compensation breakdown—not a persuasion script. If the organization can authorize €84k base at the relevant level, document the approval date and conditions before re-opening. If not, close early with a respectful explanation and a truthful referral to future roles.

A pay-equity safeguard at every exception request

Budget exceptions need an audit trail: why the job requirements changed, which objective level criteria support the proposed salary, whether comparable incumbents are treated consistently, who approved it and the effective date. Put salary range into the role intake before interviewing, not in a recruiter’s informal note.

EEOC materials describe compensation discrimination risks that extend beyond base salary to benefits and other remuneration in the United States. This does not mean an automated range tool can assess pay equity; it cannot. It means compensation alignment should plug into the employer’s existing job architecture and review controls. US guidance.

What to measure after publishing the range

Track candidate withdrawals after pay disclosure, rescoped positions, compensation exceptions and offer declines specifically attributed to a documented mismatch. Compare across job families and countries; exclude vacancies with unapproved or changed scopes from “clean” cohorts. Keep a separate candidate-experience signal: did people feel informed early enough to make a decision?

Counterintuitive inference: A higher early withdrawal rate can accompany a healthier process if pay is disclosed sooner and candidates avoid unnecessary interviews. Judge the process by wasted assessment hours, informed opt-in and fair pay outcomes—not by maximizing interview attendance at any cost.

Try the operational check

This small calculator runs entirely in the browser; no real applicant records are required. Use it to make a process assumption visible before reporting a conclusion.

Make this a repeatable standard, not a one-off hack

Capture the date, decision owner, source data, role family and exception reason every time you apply the method. Review the oldest unresolved examples with a second person. If the evidence points to another root cause, update the workflow rather than forcing a convenient metric to match your theory.

All cases and numerical values in this article are illustrative unless explicitly attributed. The operational checklists are a transparent practitioner synthesis of source guidance, not a claim of a universally validated test, legal rule or proprietary measured result. Jurisdiction-specific requirements require local review.

Research basis and further reading

Primary regulatory/professional guidance and explicitly identified vendor operational analysis. Sources are relevant reference points; the specific operational framework and synthetic cases above are our synthesis rather than findings directly measured by every linked source.

1. EU Directive 2023/970 (Article 5)
2. European Commission overview June 2026
3. EU Commission implementation notes
4. WorldatWork eight pay-transparency steps
5. WorldatWork salary negotiation and levels
6. WorldatWork pay risks and rewards
7. CIPD pay performance and transparency
8. EEOC compensation discrimination
9. EEOC equal-pay fact sheet
10. CIPD recruitment overview

Apply the finding before the next decision

Choose a single open role, review real process events, and document one falsifiable improvement. Keep the decision in human hands and show candidates what changed in their experience—not just on a dashboard.