How to Answer Salary Expectations: Scripts That Won't Get You Rejected (Real Recruiter Stories)

Figuring out how to answer the question about salary expectations is easily one of the riskiest times in an interview. One person recently found this out the hard way, as a single poorly-phrased response was all it took to turn off the interviewer. They shared how they turned around the recruiter's question with: "What is the budget?", and were promptly told they were being disrespectful and received a rejection email the same day. Here's exactly what went wrong, what the statistics say, and what you can say instead for every kind of salary question.

The Reddit story that got a candidate instantly rejected

The original poster was interviewing with internal talent acquisition at a 100-person drone startup. The recruiter opened warmly — acknowledging "how stressful job interviews can be" — and moved through a few technical questions about flight control systems. Then, about ten minutes into a scheduled 25-minute call, she asked about salary expectations.

His reply: "What is the budget?"

She thought he was being disrespectful so she cut the interview off early. She sent him a quick rejection email with no greeting. (Edit to clarify that the poster also mentioned that he already has a signed offer from somewhere else and that this company was just a backup interview, thus he didn’t feel they had leverage over him).

That context matters, but it doesn't change the core lesson. The tactic — asking for the range — is fine. The delivery is what blew up.

Why "what is the budget?" backfires (and when it works)

But the thread broke apart quickly, with the most upvoted comment pointing out that "It's kind of sassy answer to the salary question, but you could ask it in a more professional manner, and people wouldn't feel as offended by it." One user summed it up bluntly, noting that the exchange reads like, "How tall are you? How much do you weigh?" and ultimately it was rude.

One reader said the two-word answer basically means: "What you are basically doing is answering her question with: I'm worth every penny that I can get from you." Another reader said a "senior engineer" who posted a comment noted: "In this market, if you are in it, then you should come prepared knowing what the market range is for your skill set CURRENTLY, not what you want to be paid. Those are two different things."

Still, the move was praised by many. A recruiter at a staffing agency said: "I LOVE getting asked what the budget is when I ask for salary expectations. This tells me that this person actually knows how to interview, has ambition and is not afraid of a power struggle." Some on Reddit called the company's response a red flag (and a bullet dodged) and said that it's time for all jobs to be transparent about their salary range. "No more bidding war."

It’s not either camp that’s right, both of them are. Requesting the range is a perfectly good (and common) move to make. This case wasn’t a bad strategy, just a bad tone.

The core move: deflect, anchor, or answer

Each of the three plays is a good response to the salary question. Decide which to use based on how advanced in the process you are, and what kind of escape you have.

1. Deflect (gather info first)

You can flip the question back on the interviewer or politely pass on answering. Coursera's job-seekers guide, for instance, advises turning the recruiter or hiring manager's question around by inquiring how much budget the company has for the role. And Robert Half suggests to "hold your cards fairly close" or better yet, "get the employer to put out a number first" if they can. This isn't rude; it was the way you delivered it to a startup that wasn't doing so well.

2. Anchor (state a researched range)

You should try to give them a range (and make sure to back it up with market research), not a singular number, and certainly don't mention what you want. As the Reddit Engineer put it, give your market value, not your desires. If you give them a lower than expected amount that might anchor you lower than the amount they're willing to spend.

3. Answer (give a number when required)

Sometimes a job application requires that you give your number. Give a range with the bottom number as the absolute lowest figure you would be okay with. Companies like the lowest number in the range so don't say any amount of salary that you would feel underpaid for.

Research shows that deferring is the way to go. LinkedIn career coach Margaret Buj said to put it this way, "Ideally, you want to defer this conversation until the offer stage when the company has decided they want you. And the longer you delay giving the interviewer your number, the more power you are holding on to."

Copy-paste scripts for every salary scenario

See here for what to say regarding salary expectations that sounds helpful and doesn’t get you turned down. Feel free to customize as needed to match your voice.

Polite deflect + reflect the range back (the upvoted rewrite of the viral flop):

"My salary expectations may change as I learn more about the role. Is there a salary range you're targeting?"

Fit-first defer (for early-stage screens):

"Salary matters to me, but finding the right fit matters more. I'd love to understand the scope and expectations first — can we come back to compensation a bit later?"

Market-range anchor (when they insist on a number):

"Based on my research for similar roles in this market, competitive comp seems to fall in the $X–$Y range, depending on the full scope and benefits. I'm flexible on the details."

When they still won't budge and demand your figure:

"I'm looking for something in the neighborhood of $X, with the understanding that final compensation depends on the role, benefits, and overall package."

Salary on an application form (where you can't have a conversation): enter a researched range like "$62,000–$72,000" rather than a single number, or "Negotiable / open based on total compensation" if the field allows text.

Email reply to a recruiter:

"Thanks for reaching out. Before we schedule time, could you share the job description, the salary range, and the work model (remote/hybrid/on-site)? That'll help me confirm we're aligned before we both invest time."

See, each of those scripts asks for their number, but doesn’t force them to give it. That small change is what separates the recruiters who get “I love it when you do that” on the other end of the phone from “Call me when you know what you’re doing!”

How to spot and handle lowball recruiter offers (50–80% of your pay)

The other side of the salary question is filtering out offers that waste your time. In a separate r/cscareerquestions thread, an engineer described recruiters pitching contract roles at "50-80% of what I'm currently making as a FTE" — no benefits, and in-office five days a week. Some recruiters even admitted the lowball on the call: "Oh yeah I noticed you were from x company so I figured it'd be too low."

Those leaving comments on the LinkedIn post immediately pointed out that their experience lined up exactly with what was on display in the viral screenshots. "I have 18 years of experience and I get constantly spammed with things I'm grossly overqualified for... A huge part of it is that AI makes it easier for them to spam people," said the first commenter. As for a workaround, the second commenter suggested, "Be very upfront and frank... Make a copy-paste template for your reply with your reqs."

Before you proceed, screen the opportunity first. Obtain the job description, the compensation band, and the remote-work arrangement in writing before moving forward, as that’s the approach a senior commenter described: "I don't take calls without job description, salary range, and company." And bear in mind the reality check another commenter provided: outside boom conditions, you'll often earn more at your current place of work, because "replacing you costs them more and you've got the particular experience that they require". You don't necessarily have to be insulted by accepting a pay cut in exchange for a new job. You should, however, be aware of it in advance.

Do your homework: anchoring with real market data

Every credible source agrees on the first step: research the current market rate before you open your mouth. The U.S. Department of Labor's 2026 salary negotiation guide tells candidates to pull data from the Bureau of Labor Statistics, then set a target, a midpoint, and a walk-away minimum — and to "aim high when stating your desired salary range."

The data also says negotiating is expected, not risky. One 2026 compilation found 73% of employers anticipate salary negotiation from applicants, yet fewer than half of candidates actually negotiate. The Labor Department guide is blunt: "Most employers leave room to negotiate," so don't accept the first offer by reflex.

Transparency helps everyone. A PayScale study cited by Buj found that job postings with salary ranges get up to 30% more applicants — which is why so many commenters saw the secretive startup as the real red flag. For entry-level roles, the same research approach applies: check BLS, Glassdoor, and Levels.fyi for your title and location so a "$45,000–$55,000" answer is defensible, not a guess.

One more counterintuitive point: justify your number with market data and your value, never your rent or debt. Personal need weakens your case; comparable-pay data strengthens it. If you're still building your interview fundamentals, our guide on answering "tell me about yourself" pairs well with this — both questions reward preparation over improvisation.

Using MeetAssist to stay sharp on live salary questions

The salary question almost always ambushes you mid-call, and freezing is what turns a good candidate into the r/recruitinghell story. MeetAssist listens to your live interview on Zoom, Google Meet, or Microsoft Teams and surfaces real-time answer suggestions on your screen — staying invisible during screen sharing — so when "What are your salary expectations?" lands, you have a composed range-and-defer line in front of you instead of a blank mind. It works during live calls only, so pair it with the scripts above rehearsed in advance. For the setup details, see our walkthrough on using an AI assistant for interviews on Google Meet.

Frequently asked questions

What is the best answer for salary expectations?

The optimal approach is to give a researched range, and not a number, anchored to the market rate for the job. You might say, "According to my market research on similar positions, a competitive salary would be somewhere in the $X to $Y range depending on the total benefits package." You should set the bottom end of the range at a number you would be happy with, since companies will often start by offering you something closer to that.

How do you answer salary expectations without giving a number?

Politely defer the question and ask for a range: "My expectations may change with more knowledge about the role. Is there a range that you're thinking of for the position?" You're turning it back to them without being dismissive. If they refuse to give a range and continue pressing you, try to give a range backed by your research instead of outright refusal.

Is it okay to ask the recruiter what the budget is?

Yes, it is an "acceptable," expert- endorsed approach to ask for the range, which may even suggest a certain degree of expertise to some hiring managers. What will cause you to be turned off from a potential interview with that organization is the way it is worded. "What is the salary budget?" seems hostile. But ask in a complete sentence ("What is the salary budget for this job?") and provide your willingness to negotiate based on the range.

How do you answer salary expectations when you know the range?

Anchor near the top of the posted range and say something along the lines of, "I see the range is $X to $Y. My expectation is to target the upper end. But, I'm open to discussion as well." Many employers have some room to negotiate, and anchoring high gives you more room to settle at a fair midpoint.

What should I write for salary expectations on an application?

Provide a range of numbers, for example, $62,000 to $72,000, to avoid putting yourself in a corner. If the field permits writing, write something like, "Negotiable depending on total compensation package" or "Open, happy to talk." Do not leave it blank if it is a required field; having a well-considered range of numbers is better than just writing down the first number that came to mind.