skip to content

How do you choose which two non-base levers to ask a hiring manager for when the pay band is fixed?

level: seniorimportance: should knowfreq 34%

answer

  1. Two rankings, not one
  2. Movability crossed with what you value
  3. Ask who has to approve it
  4. Two specific asks, not a wish list
  5. Top of both lists wins

basics

~20 s

Rank the non-base levers twice — by how far each usually moves and by what you actually value — then ask for the top of the intersection, checking which of them the hiring manager can approve without escalating.

solid answer

~50 s

I keep two orderings of the same six levers. One ranks them by how far each usually moves once base closes: start date first, then sign-on, then the equity grant, then remote or relocation terms, then level, and policy perks last. The other ranks them by what I actually want out of this job. The asks I make sit at the top of both lists, and I make two of them rather than six, because an unprioritised list invites one blanket no. Before asking I try to work out what the hiring manager can approve alone — usually the calendar, sometimes a slice of the grant — versus what needs a compensation partner or a calibration decision, because that changes both what I ask for and how long it takes. And I only ask for things I would genuinely be pleased to receive.

go deeper

for a junior

Prepare the two lists before the offer call rather than improvising: which components tend to move, and which ones you actually want. Bringing a written ranking is most of the skill at this stage.

for a middle

Explain why two specific asks beat six. A bundled wish list can be refused in one line, while individually reasoned asks have to be answered one at a time, and each one carries a reason tied to the role.

for a senior

Demonstrate that you read the approval map before asking, and that you can tell a lever that is slow from one that is impossible. Show you would take a clean no without inventing a third ask.

for a principal

Own the judgment about how much goodwill this negotiation is worth spending, given you will report to the person across the table. Be able to say where you would stop and why the working relationship outranks the last available lever.

## Two rankings, one intersection Once a hiring manager says the base band for the level is fixed, the question stops being *whether* to keep negotiating and becomes *which levers to spend the remaining goodwill on*. Two orderings decide it. **Ordering one: how far each lever usually moves.** This is the prepared artefact — six non-base levers, ranked by movability once base is closed: 1. **Start date** — free, and often inside the hiring manager's sole authority. 2. **Sign-on bonus** — one-time cash, separate budget line, no effect on peer parity. 3. **Equity grant** — banded per level, but the range is frequently wider than base with real discretion inside it. 4. **Remote or relocation terms** — bounded by a location policy; relocation support is often a standard package that can sometimes be topped up. 5. **Level or title** — changes which band applies, so it needs calibration evidence and sign-off beyond the manager. 6. **Policy perks (leave, learning budget)** — usually uniform across the company; local discretion is rare. This order is a prior from common practice, not a rule. It varies by company and by circumstance, and a team with a hard delivery deadline and an unspent budget can invert it. **Ordering two: what you actually value.** Written honestly, and before the call, so it is not improvised under pressure. A candidate with a running handover at their current job may rate the calendar above cash. Another may rate the grant above everything because they intend to stay for the whole vesting period. The asks come from the top of both lists at once. A lever that moves easily but that you do not care about is a wasted ask; a lever you care about that never moves is a slow no that spends your credibility. ## Why two asks and not six Six asks arrive as a wish list. The reader cannot tell which one matters, so the cheapest response is a single refusal covering all of them, or a token concession on the least valuable. Two specific asks, each tied to something about the role, can be answered individually and are much harder to bundle into one no. Being explicit that these are the two things that matter also makes it obvious what a yes would close. ## Map the approval routes before you ask Levers differ less in generosity than in **who has to sign**. Broadly, and with wide variation between employers: - The **calendar** is usually the hiring manager's alone. - A **sign-on** inside a normal range is often theirs or one step away; an unusual amount escalates. - **Grant size** inside the level's range may be theirs; above it, it is not. - **Level** is almost never theirs unilaterally — it is a calibration decision, and asking for it post-offer without new evidence rarely lands. - **Policy perks** are typically nobody's to grant locally. Asking who would need to approve something is a legitimate question and often gets a straight answer. It tells you whether a maybe means days or weeks, and whether the ask is possible at all. ## A worked example A candidate closing on a mid-level data platform role hears that the base band is fixed and that the offer already sits in its upper part. Their movability ranking puts start date and sign-on on top; their value ranking puts the calendar first, because they are mid-way through handing over a pipeline migration at their current employer, and the sign-on second, because base landed below the number they had set for themselves. The intersection is unambiguous, so they ask for exactly those two: a start **3 weeks** later than the letter proposes, with the handover as the stated reason, and movement on the sign-on, using the direct question `If base is genuinely fixed, is there room on the sign-on or the grant?` They do not mention leave, the learning budget or the title at all. The calendar is agreed on the call; the sign-on comes back improved after one internal check. Two asks, two answers, no goodwill spent on levers nobody could have moved. ## The failure this avoids The common alternative is not overreach — it is silence. A candidate hears that the band is fixed, concludes the negotiation is over, and accepts a package that had at least two movable components in it. The second most common alternative is the shotgun: every lever named at once, with no signal of priority and no reason attached to any of them. Both are avoidable with ten minutes of preparation and one honest ranking of what you want. Whatever is agreed on a non-standard lever — a start date, an unusual location arrangement — is worth reflecting in the written offer rather than a verbal understanding.

  • How would you find out which levers the hiring manager can approve without escalating?
    Ask directly — it is a normal question and usually gets a straight answer. Phrasing it as what would need a further approval, rather than what they are allowed to do, keeps it collaborative. The answer changes your ask: if the grant needs a compensation partner and the calendar does not, you know which concession lands on the call and which one takes days.
  • What do you do if both of your two asks are refused outright?
    Decide whether the package as written clears the bar you set before the loop. If it does, accept cleanly and without resentment; if it does not, say so plainly rather than manufacturing a third ask. Dropping to a lever you never wanted signals that the earlier asks were negotiating theatre, and it buys something you will not value.
  • Would you ever ask for a lever you do not personally value, to trade it away later?
    It is a poor trade in a hiring negotiation. The counterparty is someone you will work for, the exchange is short, and a manufactured ask mostly costs credibility. Making two asks you would genuinely accept keeps the conversation honest and makes a yes actually worth something.

saying these in an interview costs you the question

  • Naming every remaining lever at once with no stated priority
  • Going silent and accepting once base is declared fixed
  • Asking for a lever you would not actually be pleased to get
  • Pushing a level change post-offer with no new evidence of scope
  • Never checking whether the ask needs an approval beyond the manager

context