Picture an engineer midway through an interview loop when a recruiter asks, “What are your salary expectations?” The job description sounds promising, but the interview has not yet clarified whether the role owns a service end to end or contributes to a larger team effort. Giving a firm number before you understand that scope can anchor a conversation around the wrong job. Refusing to discuss pay at all can leave the recruiter without a way to check whether continuing makes sense. Your answer should reflect the information you have at that point.
Do you know the role's pay range?
If the employer has provided a range, use it as a starting point and confirm what it covers. Base pay and total compensation are different measures, and a posted range alone may not tell you where this particular role sits. You can say, “I saw the posted range. Can you tell me which part of it you expect this role to fall within and what the compensation package includes?” Check the current posting before relying on its figures.
If no range has been shared, ask for one before naming a target: “Could you share the budgeted range for this role? I want to make sure we are discussing the same scope.” You may still need to answer first, but asking gives you a chance to ground the conversation in the employer's role rather than an unsupported guess.
Is the scope clear enough to name a range?
When the responsibilities remain vague, say what needs clarifying and keep the conversation moving. For an engineering role, ownership of a production service, incident response expectations, and the level of technical decision-making can change how you assess the opportunity. A useful response is, “I would like to understand the ownership and expectations before giving a precise range. Can we revisit compensation after we discuss the role in more detail?”
If the recruiter needs an answer to continue, give a researched range you would genuinely consider and identify what you have assumed: “Based on my understanding of the role so far, I am targeting a range around [your researched range], depending on the full scope and package.” Do not use a range whose lower end you would reject. Verify current information from relevant postings and conversations before settling on your numbers.
Do you already have a defensible target?
If you understand the role and have researched comparable opportunities, answer directly. State your range, indicate which compensation measure you mean, and leave room to discuss the package. For example: “For a role with this level of service ownership, I am looking for base pay in the range of [your researched range]. I would also want to understand the full package.”
Prepare the evidence behind your target before the conversation. An engineer might draw on examples of resolving a recurring reliability issue, making a consequential design choice, or helping other teams adopt a safer interface. Those examples establish the scope of work you can discuss. They do not, by themselves, prove that an employer will pay a particular amount, so keep your market research and your work evidence distinct.
What if the stated range is below your minimum?
Decide whether another part of the package or a different role scope could genuinely change your answer. If not, be direct: “Thank you for sharing the range. My minimum for a move is [your minimum], so I do not think this role is a match at the stated level.” That can save both sides further interview time.
If you need one clarification before deciding, ask it specifically. “Is that range for base pay, or does it describe total compensation?” is more useful than continuing several rounds in the hope that an unexplained gap will disappear. Once you have the answer, either continue on terms you would accept or step away.
How will you support your answer when the conversation continues?
Keep a few work examples ready that show the level of responsibility you are discussing. Record the problem, your decision, who depended on the work, and what outcome you can substantiate. Describe the substance without storing proprietary code, sensitive internal documents, or private customer details in a personal record.
If you're asked to explain your fit, this guide to answering “Why should we hire you?” shows how to turn a relevant work example into an answer.
A compensation answer can open a longer conversation about your fit for the role. Save your strongest work evidence in ImpactLogr so you can explain the scope behind your target without trying to reconstruct it during the interview.