How to Answer Salary Expectations Without Pricing Yourself Out Before the Interview

Your salary answer should test alignment, not negotiate the final offer before the interview. The mistake is searching for one perfect script and using it everywhere. A required number, an open text box, a disclosed range, and a recruiter conversation create different constraints, so the strongest answer changes with the interface.

Prepare three reference points, then keep one private

Before applying, define three reference points:

• Floor: the minimum base salary you would genuinely accept after considering the rest of the package. Keep this private.
• Target: a defensible base-salary outcome for the role, level, location, and your evidence.
• Research range: the plausible base-salary span you found across comparable roles and reliable sources.

Prepare the floor for your decisions, not for automatic disclosure.

The U.S. Department of Labor's interview guide recommends researching salary information before the conversation, then giving a range that reflects your skills and experience while signaling flexibility.^[1] That preparation matters because the first credible number can shape the conversation that follows. Negotiation research describes this as anchoring, which is why an unresearched low answer can become a ceiling long before anyone understands the job.^[2]

Your floor and target are not synonyms. If you give your true minimum as the desired answer, you have volunteered the lowest acceptable outcome before learning the team's scope or package.

Match the answer to the interface

When the posting includes a range

Confirm what the range represents before selecting a point inside it. Is it base salary or total compensation? Does it change by location? Is the company considering one level or several? A published band can be useful evidence, but its meaning depends on the posting. For example, Washington's rule for covered postings says the range should reflect the employer's most reasonable and genuinely expected compensation range at the time of posting.^[3] That is one jurisdiction's standard, not a universal promise about every listing.

Try:

The posted base range appears broadly aligned. Where I would land within it depends on the role's level and scope, and I would also like to understand the bonus, equity, and work arrangement.

When the form allows text

Use the space to preserve context without dodging the question:

Open to discussing the budgeted range based on level, scope, location, and total compensation.

If you already have a well-supported target, you can state a range and add the variables that could move it. Do not write "negotiable" alone if a slightly fuller answer can establish useful alignment.

When the form forces one number

First check the posting, recruiter material, and application instructions. Then enter a truthful target you could defend in the next conversation. Do not enter zero, a joke number, or your absolute floor unless the form explicitly defines the field that way. Employers do not consistently explain how these fields are used, so treat a required answer as potentially consequential without assuming it automatically rejects candidates. Keep it internally consistent with the five-gate application audit.

When a recruiter asks live

Ask for information before narrowing when the budget or level is unclear:

I want to make sure we are discussing the same scope and level. What base range is budgeted for the role, and how does the company structure bonus or equity?

If the recruiter asks again, answer directly with your researched range:

Based on the role as described, I am targeting a base range of [X to Y]. I am open to discussing where the position lands once I understand the level, location basis, and full package.

Different interfaces reveal different amounts of context. Your answer should reflect that.

Keep the number coherent with your positioning

A compensation answer does not stand apart from the rest of the application. If your resume presents staff-level scope but your target resembles a much narrower role, a recruiter may need to clarify the level you actually want. If your target implies a higher level than the application evidence supports, the expectation may look difficult to justify. Employer responses vary, so treat these as coherence risks rather than automatic outcomes.

Use comparable roles, not just broad occupation averages. Check the actual responsibilities, seniority, geography, company type, and compensation mix. The data-driven career guide explains how to treat benchmarks as context rather than promises.

If the posting reveals a different emphasis than your base resume, CoreCV can fine-tune that resume against a pasted job description or job URL. Review the changes against your real experience so the role level, evidence, and salary conversation tell one credible story. The role-specific tailoring guide shows how to change emphasis without changing the facts.

A base-salary answer becomes meaningful only when the surrounding package is clear.

Save negotiation for the offer, but learn enough now

An early salary discussion should prevent obvious mismatch. It should not force either side to settle every term before the interviews reveal the actual scope. At the offer stage, compare salary with bonus, equity, level, remote terms, and expectations as one package. The tech offer negotiation guide provides that fuller framework.

Follow the CoreCV Blog via RSS for weekly practical guidance on making technical value legible in an AI-shifting hiring market.

The best salary-expectations answer is neither evasive nor prematurely precise. It gives enough information to test whether the opportunity is viable, stays consistent with the role you can prove, and leaves room to evaluate the job that actually emerges from the interview.

Sources

1. U.S. Department of Labor Veterans' Employment and Training Service, Interview Skills Participant Guide: https://www.dol.gov/sites/dolgov/files/VETS/files/OBTT_InterviewSkills_PG_OCT23.pdf

2. Harvard Law School Program on Negotiation, Meet Your Salary Expectations: https://www.pon.harvard.edu/daily/business-negotiations/meet-your-salary-expectations/

3. Washington Administrative Code 296-123-060, Disclosure of wage or salary range by employer: https://lawfilesext.leg.wa.gov/law/WACPDF/WAC%20296%20%20TITLE/WAC%20296%20-123%20%20CHAPTER/WAC%20296%20-123%20-060.pdf