Bounce

What Should You Say When an Interviewer Asks Your Current Salary?

October 26, 2026 · Bounce

You are three questions into a phone screen, things are going well, and then it lands: "So, what are you currently making?" Your stomach drops. Answer too low and you fear the offer will match it. Refuse and you worry you will sound difficult. Neither fear is silly, and you deserve better than a vague "just be confident" pep talk.

This guide gives you word-for-word language you can actually say, explains where the question may not even be legal anymore, and keeps you on the right side of the honesty line the whole way through.

Why do interviewers ask about your current salary?

Understanding the motive helps you answer without panic. Recruiters usually ask for one of three reasons:

Only the first reason serves you at all, and you can satisfy it without revealing your history. That is the core move of this whole article: answer the real question (do we fit?) instead of the literal question (what do you earn?).

Is the current salary question even legal where you live?

In the United States, many states and cities have passed salary history bans that prohibit employers from asking candidates what they currently earn or have earned before. These laws exist because pay history questions tend to carry old underpayment forward, which hits women and minorities hardest.

Two honest cautions here:

If you are asked in a place with a ban, you do not need to lecture anyone. A simple redirect (below) works, and you can decide privately whether the company's sloppiness is a signal.

Honest scripts to deflect without lying

Deflection is not evasion or a trick. You are declining to share private information while giving the recruiter what they actually need: a way to know whether you fit the budget. Pick the script that sounds most like you.

The clean redirect:

"I'd rather not anchor this to my current pay, since the roles are different. Based on my research, I'm targeting a range of X to Y. Does that fit your budget for this position?"

The turn-the-question:

"I'm happy to talk numbers. Could you share the range budgeted for this role? That way I can tell you right away if we're aligned."

The context answer, if you want to share:

"My base is 72,000, but honestly, part of why I'm looking is that the market has moved past that for this work. For this role, I'm targeting 85 to 95."

The one for a persistent recruiter:

"I understand you need to know we're in the same ballpark. My expectation for this role is X to Y. My past compensation reflects a different company, a different scope, and a decision I made years ago, so it won't tell you much."

Every one of these is fully honest. None states a false number, and none pretends the budget question does not matter. What you must never do is inflate your current salary. Some employers verify compensation during background checks or through offer paperwork, and a caught lie can sink an accepted offer. The gap between a confident redirect and a fabricated number is the gap between negotiating and gambling with your reputation.

How to figure out the range you will name instead

Every deflection script above replaces your history with a target range, which means you need one before the call. Guessing out loud is how people lowball themselves.

There is a full walkthrough of this in how to research your market salary before you negotiate. Do it before the phone screen, not after.

What if you are currently underpaid?

This is the situation where the current salary question stings most, and where deflecting matters most. If you earn 55,000 in a role that pays 75,000 at other companies, revealing your number invites an offer of 60,000 that the recruiter sincerely believes is generous.

You do not have to explain why you are underpaid, apologize for it, or treat it as a secret shame. Underpayment usually happens for boring reasons: you were hired in a down market, you stayed loyal while raises lagged, you started in a lower cost-of-living area. Use the redirect scripts and let your research, not your history, set the anchor. If the topic comes up late in the process anyway, the context answer works: state the number, then immediately state why it is not the right reference point.

And if the roles you are landing interviews for are all anchored low, the problem may start further upstream, with how your experience reads on paper. A resume that undersells your scope attracts offers that undersell it too. That is worth fixing before your next application, and it connects directly to how you answer salary expectations on applications.

Common mistakes with the current salary question

Get your leverage in order before the call

Here is the part most negotiation advice skips: the strength of your answer on the salary question depends on the strength of everything that came before it. A candidate whose resume clearly shows scope, results, and relevant skills can name a confident range and have it taken seriously. A candidate whose resume undersells them is negotiating uphill from the first minute.

So before your next phone screen, spend five minutes checking the document that got you there. The free Beat the Bots scan at careerbounce.io shows you exactly what applicant tracking systems read from your resume: which skills come through, which accomplishments survive parsing, and where your real experience is getting lost. It runs on your device, your resume never leaves your computer, and it costs nothing. It will not promise you a job (nothing honest can), but it will make sure the person asking about your salary has already seen your best case.

See what the hiring software reads

Free, and it runs in your browser: your file never leaves your device, and your score and findings show with no name or email.

Scan my resume free

Frequently asked questions

Do I have to tell an interviewer my current salary?

In many places, no. A growing number of US states and cities have salary history bans that make it illegal for employers to ask. Even where the question is legal, you are allowed to redirect the conversation to your expectations for the new role instead of your past pay. Check the current rules where you live, because they change over time.

Is it lying to refuse to share my current salary?

No. Declining to answer is not dishonesty. Lying would be stating a false number. There is a clear line between the two: you can say 'I'd rather focus on the value of this role' all day long, but never inflate your actual pay, because offer letters and background checks sometimes surface the truth.

What if the application form requires a current salary number?

Do not enter a number you know is false. If the field accepts a range or a target, put in a researched figure for the role you are applying to, or the lowest salary you would genuinely accept. If the form truly demands a past number and will take nothing else, say so plainly in the first free-text field or to the recruiter on the phone: note that you would rather discuss expectations for this role, and give your target. A recruiter can work with that; a fabricated salary history is the kind of thing that surfaces later.

Should my resume mention salary at all?

No. Salary does not belong on a resume, and including it can anchor you low before a single conversation happens. Your resume should prove the scope and results of your work, which is what justifies the number you ask for later. A free scan at careerbounce.io shows exactly what an applicant tracking system reads from your resume, so you can make sure your accomplishments, not a number, do the talking.

What is a good answer if I genuinely want to share my current salary?

Share it with context: state the base, then immediately add the full picture (bonus, benefits, and the reason you are looking). For example: 'My base is 72,000 with a small bonus, and part of why I'm looking is that the market for this work has moved past that.' Framing it this way keeps the number from becoming your ceiling.