Is It Normal for Recruiters to Avoid Giving a Straight Answer About Pay?
Three interviews in, and every time compensation comes up, the answer is some version of “we’ll get there.” It’s a frustrating enough pattern that plenty of job seekers wonder whether they’re being strung along or whether this is just how hiring works.
At a glance
Yes, vague answers about pay early in a hiring process are common, though the practice has been shifting as more places adopt pay transparency requirements. Recruiters often delay specifics for reasons related to internal process and negotiating room rather than dishonesty, but that doesn’t mean a candidate has to accept indefinite vagueness, especially where disclosure rules already apply.
Why recruiters often hold back early
Recruiters frequently don’t control the final number themselves; it may depend on a hiring manager’s budget, internal approval processes, or where a candidate lands on an internal pay band based on experience. Some organizations also prefer to gauge a candidate’s fit and interest before getting into compensation, treating an early number as something that could anchor negotiations in a direction they’d rather avoid. None of this means the number doesn’t exist somewhere internally — it usually does — but the sequencing of when it gets shared varies a lot by company and role.
How pay transparency laws are changing this
A growing number of states and cities have adopted laws requiring that job postings include a pay range, or that a range be disclosed at some defined point in the process, such as upon request or after an initial interview. Where these laws apply, a recruiter avoiding the topic entirely may simply not be complying, whether the location covers the specific job or not, since remote and multi-state postings raise their own complexities. Because these rules vary significantly by state and continue to change, checking current state and local requirements is a more reliable approach than assuming any single rule applies everywhere.
Common reasons this comes up in practice
- The role hasn’t been fully scoped. Sometimes a range genuinely hasn’t been finalized before candidates start interviewing.
- The company wants flexibility. A wide, unstated range can let a company adjust the offer based on how a specific candidate negotiates.
- The recruiter is following internal policy. Some companies instruct recruiters not to discuss numbers until a certain interview stage regardless of the recruiter’s own preference.
- A posting already includes a range but repeats it vaguely. In this case, the recruiter may just be reciting a broad range rather than avoiding the topic entirely.
How candidates typically approach this
Some job seekers ask directly and early, framing it as a scheduling question — wanting to know a general range is in the right ballpork before investing more time in a multi-stage process. Others research typical compensation for the role and location using general public data before interviews start, so a vague answer doesn’t leave them starting from zero. Reviewing what to ask an employer before accepting an offer can also be a useful reference point for framing these conversations more broadly, and for anyone weighing whether a lower offer is even worth accepting, thinking through what it means to take a lower-paying job just to stop a difficult situation is a related consideration.
Why this matters beyond just the number
A vague answer on pay early on can also be a signal worth folding into the broader decision of whether a role is a good fit, alongside questions about benefits, schedule, and growth. Someone weighing a relocation offer that comes with its own compensation questions often finds that pay transparency, or the lack of it, is just one part of a much larger picture worth evaluating together.
The takeaway
A recruiter avoiding specifics isn’t necessarily a red flag on its own, since it often reflects internal process rather than any intent to mislead. Where pay transparency laws apply, though, a candidate has a stronger basis to ask directly and expect an answer, and knowing which rules apply in a given location is one of the more useful things to check before assuming vagueness is just standard practice.