Above Band: The Trap of the Fake Limit

The "above band" trap is when a recruiter blocks your ask by citing an abstract pay band as an absolute limit. Don't treat the band as fixed: ask what it is based on, reposition yourself at its upper level using your results and the market, then ask what would unlock the next cell.

The "above band" trap is one of the most effective in a salary negotiation, because it sounds technical and sounds final. The recruiter raises an abstract "band" against your ask, as though an invisible wall simply ruled it out. Once you realise that band is almost never an airtight border, you're already back in control. Here's how the trap works, and how to reopen the range without putting the recruiter on the back foot.

What the recruiter says

"That number is above our band for this role; it's simply not something we do."

What gives it away: the recruiter reaches for an abstract "band" to shut the ask down without ever discussing it. The word "band" does all the work — it implies a rigid system, signed off somewhere above their head, that nobody in the room has any power over. "Not something we do" closes the door before you've made your case. The trap works because most candidates respect the rules: faced with a standard presented as untouchable, they back off rather than risk looking unreasonable.

Why the recruiter does it (the stakes)

A salary band almost always exists, but it's rarely unique and never as fixed as it sounds. It depends on a job title, a seniority level, sometimes a region — all parameters that are, in practice, open to discussion. By presenting the band as a raw fact, the recruiter sidesteps the only question that matters: which point in that band do you actually belong at?

Two things are going on here. First, there's a budget angle: if the band holds, they spend less. Second, it doubles as a test of how well you've prepared. A candidate who accepts "above band" without a single follow-up question signals they know neither the company's pay structure nor their own market value. A sharp question about what the band is based on does the opposite — it shows you understand exactly how these systems work, and that alone shifts the balance of power.

Why a precise answer changes everything

Respond to "above band" with a soft "oh, okay, I understand" and you've validated the limit and closed the subject yourself. A precise answer doesn't dispute that the band exists — it disputes your placement within it. That distinction matters: you're not attacking the system, you're asking to be positioned correctly inside it.

Asking what the band is actually based on forces the recruiter to spell out what they'd rather leave vague. More often than not, a slightly different title, recognised seniority, or a broader scope is enough to tip you into the higher bracket. The "impossible" number turns out to be a matter of framing.

The counter

The rules at work here are preparation (rule 1) and questioning (rule 3): without references and without questions, a band stays a wall. The counter has three steps:

1. Have them spell out the band's criteria. "Just so I understand, what is this band based on — the title, the seniority, the scope of the role?" You turn a fact into a topic of discussion.
2. Reposition your ask via your value. "Given the responsibilities described and my results on X, my profile fits the upper level of your band; market references point the same way."
3. Ask what would unlock the next level. "What would move this role to the cell above — a different title, a broader scope?" You offer a path rather than a deadlock.

Good answer versus excellent answer

A good answer holds your ask without justifying it:

"I understand, but that's the number I need for this role."

Fair enough — you haven't caved — but there's more on the table. You're pitting stubbornness against a rule, and in that contest the rule usually wins. You've given the recruiter no reason to revise your placement, and no graceful way to do it even if they wanted to.

The excellent answer questions the band, justifies by value, and offers a path:

"I understand there's a band. To read it together: what is it based on — the title, the seniority? Because given the responsibilities described and my results — for example +30% on [metric] — my profile seems to fit the level above. What would unlock that cell?"

The difference isn't tone, it's territory: you're no longer arguing whether the band applies, but where exactly within it you sit.

Stay human: read the room

Remember there's a person on the other end of this, working within their own constraints. "Above band" isn't always a tactic — sometimes the recruiter is genuinely repeating a limit they didn't set and believe is fixed. Read the room. If the band is being wielded like a weapon, meet it with calm firmness; if it's being shared in good faith, meet it with curiosity instead ("help me understand how this role gets classified").

The goal is never to embarrass the recruiter by proving their band is negotiable — it's to help them build the internal case for placing you where you belong. Push hard on the substance, stay easy on the delivery.

Frequently asked questions

Is a salary band really negotiable? The band itself rarely, but your placement within it almost always. Title, seniority, and scope determine the cell — and all of that is up for discussion. Ask for the criteria before concluding it's impossible.

What if the recruiter won't detail the criteria? That's a signal in itself: a band no one will spell out is often more flexible than claimed. Refocus on non-base levers, or see the frozen budget trap, a close cousin of above band.

Should I accept a different cell in exchange for a better number? Often, yes: a slightly higher title can unlock the range while strengthening your CV. It's a win-win compromise.

This trap is one of the 10 recruiter traps. Continue with the lowball anchor and the peer comparison, its two direct cousins.