Skip to content
QSWEQB
hardHrScenarioMidSeniorStaffLead

We are offering you the mid-level role rather than the senior one you interviewed for. How do you respond?

Ask what the panel saw that put you at the lower level before you argue, because level drives your band and your next promotion, not just this year's pay. Then either counter with evidence against their own criteria, or get the path to re-levelling in writing.

5 min readUpdated 2026-07-28

What the interviewer is scoring

  • Does the candidate ask for the specific gap in the debrief before pushing back
  • Whether they understand that level constrains future pay, not only the current offer
  • That they counter against the company's own levelling criteria rather than their years of experience
  • Whether a fallback is proposed that the recruiter has authority to grant
  • Does the candidate know what they would accept, and say so calmly rather than as an ultimatum

Answer

Why the title matters more than the number attached to it

A down-level looks like a pay conversation and is not one. In most structured companies the level determines the pay band you sit inside, the size of work you are assigned, who reviews you, what equity refresh you receive, and how far you must travel before the next promotion is even considered. Accepting a level below the one you interviewed for therefore compounds: this year's gap is the smallest cost, and the larger one is that your next two increases are computed inside a lower band, and that a promotion you have effectively already earned now has to be earned again from a standing start.

There is a second, subtler cost. Levels tend to travel with you. The next employer asks what you were, and "mid-level for three years" is a harder starting position than the senior title you held before the move. That is the reason to take this seriously even when the money offered is acceptable.

None of which means the answer is always to fight. Sometimes the down-level is accurate, sometimes the team is genuinely worth joining anyway, and sometimes the company's mid-level covers scope that your previous employer called senior. Titles are not comparable across companies, so the first task is to find out what theirs actually means.

Ask before you argue

The single most useful move takes one question, asked without heat:

"That is different from what we discussed, so I want to understand it properly before I respond. What did the panel see that placed me at the lower level rather than the one we interviewed for? And could you tell me how the two levels differ in scope here?"

You are after two things. First, the specific gap, which is usually one of a small set: system-design breadth, evidence of leading rather than doing, ambiguity handling, or one round that went badly. Second, the levelling criteria, because that is the ground the argument has to be fought on. Recruiters will often share the level descriptions if you ask; if a company will not describe how it distinguishes two levels, that is worth knowing before you join it.

If the answer is that a single interview went weakly, ask whether an additional conversation is possible. That is a reasonable request and companies do grant it. If the answer is a genuine gap you recognise in yourself, you now know what to work on, and the conversation shifts productively to how fast it can be closed.

Counter against their criteria, not your CV

The weak counter is a restatement of seniority: years of experience, previous title, the fact that you were leading a team. The panel has already seen your CV and made a judgement in spite of it, so repeating it changes nothing and reads as entitlement.

The counter that works maps concrete evidence onto the specific criterion they named. If the gap is "led work but did not own outcomes across teams", you answer with an instance where you did precisely that, and you keep it to the shape of the criterion.

"I hear that the gap is cross-team ownership. The migration I described in the design round ran across three teams for two quarters — I wrote the plan, negotiated the sequencing with the two other leads, and I was the one accountable when the cutover slipped. If it would help, I can walk through the parts I did not get time to cover, or you are welcome to speak to the platform lead I worked with."

Make one such counter, well evidenced, and stop. Repeating it in three emails does not improve it, and levelling decisions are usually made by a committee rather than by the recruiter you are talking to, which means your argument has to be compact enough for them to relay accurately.

Fallbacks, in the order they are usually available

If the level genuinely cannot move, the goal shifts to reducing the cost of accepting it. What is available differs by company, and asking which of these the recruiter can influence is a better question than pushing on one.

Pay near the top of the lower band, rather than at its midpoint, on the argument that you are at the boundary of the two levels. This is the most commonly granted concession because it needs no committee.

A written re-levelling review at a defined point, with the criteria named. Vague assurances that you will be promoted quickly are worth nothing, and every candidate who accepts one discovers that the manager who gave it has changed roles. What has some value is a specific date, a named criterion and an email that records both, plus an honest answer to how long promotions normally take there for someone who meets it.

A one-off joining payment that offsets the first year's gap. It does not fix the band and it does not compound, so treat it as compensation for the delay rather than as a solution.

The scope itself. Ask what you would be assigned in the first two quarters. If the work is what you wanted and the title is what lags, that is a different trade from being given smaller work as well as a smaller title.

The arithmetic of accepting, on stated numbers

Do this on paper, with figures you have been given rather than figures you assume. Suppose the senior offer you expected was 100 units of base and the mid-level offer is 88, and suppose promotion at this company typically takes two review cycles from a standing start. Then the cost is not 12 units. It is 12 in year one, something similar in year two while your rises are computed off 88, and a promotion clock that restarts. Written down like that, a joining bonus of 10 units plainly does not cover it, and you can say so without raising your voice.

The same arithmetic sometimes argues for accepting. If the team, the manager and the work are what you want, and 88 still exceeds what you have now, the deal may be worth doing with a review date attached. The point of the calculation is that you make that choice knowingly rather than by relief.

Where candidates lose this

By treating it as an insult. A down-level does sting, and the injured reply — pushing back before asking what the gap was, or accepting immediately in a slightly wounded silence — is what forfeits the outcome. Ask for the reason, argue once against the reason they gave, name the fallback you would accept, and be genuinely willing to decline if the whole package is worse than staying put. Recruiters expect a candidate to challenge a level; what they cannot work with is a candidate who challenges it without giving them anything to take back to the committee.

Likely follow-ups

  • What specifically would have moved the decision the other way?
  • If the level is fixed, what is the fastest documented route to the next one here?
  • Would you take the same pay at the lower title?
  • How does a re-levelling review work if my manager changes in six months?

Related questions

compensationlevellingnegotiationoffercareer-progression