How should a candidate ask a recruiter about the pay band and how the level is decided?
answer
- A band belongs to a level
- Ask for a range, never a single figure
- Two halves: the range and the mechanism
- Ask who decides the rung, and when
basics
~20 sAsk for a range attached to a named level, not a single figure: "What is the band for this level, and how is level actually decided?" That yields the range plus the mechanism that decides your rung.
solid answer
~40 sI ask it as one question with two halves, early in the screen: "What is the band for this level, and how is level actually decided?" The first half asks for a range rather than a number, which is a question a recruiter can usually answer without escalating. The second half is the one people forget -- the band only means something once you know which level the requisition is posted at, whether the loop can land you at a different level, and who makes that call. Then I ask two follow-ups: whether an up-level or down-level is possible based on how the rounds go, and where in the band a candidate at this level typically starts. I keep my own number out of the exchange until I have the range and the level.
go deeper
Rehearse the question until it is comfortable to say out loud, and ask for a range rather than a figure. Write down both ends and the level name during the call.
Know that a band attaches to a level, and be able to ask the second half -- how the rung is decided and by whom -- rather than stopping at the range.
Use the answer immediately: pitch your examples at the scope of the rung you are targeting, and probe what separates it from the level above so you know what the rounds are listening for.
You are calibrating a whole process, not one number. Decide in the screen whether the posted rung is worth your weeks, and be willing to ask for the requisition to be considered at a higher level before the loop rather than after it.
## Why band and level are one question, not two A pay band is a property of a **level**, not of a role title. "What does this pay?" is therefore an underspecified question: the honest answer depends on a rung the recruiter may not yet have fixed for you. That is why the question worth asking is the pair -- "What is the band for this level, and how is level actually decided?" -- and why asking only the first half so often produces a vague answer. The three things you are trying to learn: 1. **The range.** Both ends of it, for the level this requisition is posted at. 2. **The rung.** Which level that is, in the company's own naming, and what scope it is expected to cover. 3. **The mechanism.** How a candidate's level is settled -- typically by the interview panel's read of scope in a calibration discussion, sometimes by the requisition alone. Practice varies, so ask rather than assume. ## Asking for a range, not a number Ask for the band, not a figure. A range is a fact the recruiter usually holds and is often permitted to share; a single number is a commitment they cannot make in a screen, and asking for one tends to convert the conversation into a negotiation before there is anything to negotiate. Phrasing that keeps it factual: *what is the range attached to that level*, or *what are the bottom and top of the posted band*. Deliberately keep your own figure out of this exchange. You are gathering the range so you can decide what to say later, and once you have named a number first you have anchored the whole process against information you did not yet have. Note also that rules on whether a range is published, and on whether you can be asked about your current or previous pay, vary considerably by jurisdiction and change over time -- in some markets ranges are routinely posted, in others they are shared only on request. Treat that as local practice to check for your own situation; it is not a universal entitlement, and nothing here is legal advice. ## The leveling half The leveling half is what turns a range into information you can act on. Useful follow-ups, in the order they tend to matter: - **What level is this requisition posted at?** A single answer that recalibrates every story you plan to tell. Pitching examples at the wrong scope is one of the most common quiet loop failures. - **Can the loop result in a different level than the one posted?** Many companies allow the panel to recommend up or down; some post a range of two adjacent levels for one requisition. Both are common shapes, not universal ones. - **Who makes that decision, and when?** Knowing whether it is settled by the panel's discussion or by the manager alone tells you which conversations in the loop are actually the leveling conversation. - **Where in the band does someone joining at this level usually start?** A band's midpoint versus its top is a large practical difference, and the answer tells you how much room exists before anything is negotiated. ## Reading the answer you get Three answers are common, and they call for different next moves. **A concrete range and a clear level.** Best case. Write both on your process map and check the range against the benchmark you set for yourself before the screen. **A range but a fuzzy level** -- "it depends how you interview." That is often honest, and the right response is to ask what distinguishes the two levels in scope terms, so you know what the rounds are listening for. **No range at all.** Sometimes policy, sometimes discretion. Do not push a recruiter into breaking a rule; instead invert the question and ask for a directional check -- state the range you are targeting for a role at that level and ask whether the posted band can reach it. A yes/no costs the recruiter nothing and tells you what you needed. What you should not do is invent a rule of thumb for yourself here, or accept a number stated with no level attached to it. Both leave you calibrating against nothing. ## The failure to avoid The worst version of this conversation is skipping it and asking the panel instead. Engineers on a panel usually cannot quote a band, are frequently uncomfortable being asked, and may relay the question back in a way you did not intend. The recruiter is the correct audience precisely because compensation and leveling are the part of the process they own.
- The recruiter says the band is confidential. What do you ask instead?Invert it into a directional check: name the range you are targeting for a role at that level and ask whether the posted band can reach it. A yes or no costs them nothing and gives you the decision you needed. You can also ask what level the requisition is posted at, which is often shareable even when the range is not, and what distinguishes it from the level above.
- Can the loop change the level the role was posted at?Often, yes -- a common pattern is that the panel's read of your scope feeds a calibration discussion that can recommend a rung above or below the posting, and some requisitions are deliberately posted across two adjacent levels. It is not universal, so ask the recruiter directly rather than assuming. The practical consequence is that you should pitch your examples at the scope of the higher rung you are credibly targeting.
- Why not simply state the number you want when the band question comes up?Because you would be anchoring against information you do not have yet. Until you know the level and its range, any figure you name is either below what the level would have paid or above what the band can hold, and both cost you. Get the range and the rung first; there is time afterwards to say what you are targeting.
saying these in an interview costs you the question
- Asking what the role pays without naming a level
- Volunteering your own figure before hearing the range
- Asking a panel engineer for the band instead of the recruiter
- Accepting a number with no level or range attached to it
- Pushing a recruiter to disclose a range they have said they cannot share