How to talk about salary in English when it is not your first language

Negotiating pay is uncomfortable for almost everyone. In a second language there is an extra cost: when the right words do not come quickly, people tend to accept the first number to end the awkward moment. Nobody loses money because of their grammar. They lose it because they ran out of sentences.

This guide collects the sentences. It also covers a problem native speakers rarely think about: the same number can mean very different things depending on where you and the recruiter are from.

The misunderstanding that costs the most

In the US and the UK salaries are usually discussed per year, before tax. In much of Central and Eastern Europe people think per month, and sometimes after tax. Contractors often think in day rates. If a recruiter in London hears "fifteen thousand" and you meant per month, before tax, you have just underpriced yourself by a lot, or confused the conversation.

Always say the unit out loud:

That's per year, before tax.Annual gross: the default in the US and UK. To be clear, I mean per month, net, on a contractor basis.Monthly net on a B2B or contractor agreement. Just so we're comparing the same thing, is your range annual or monthly?When the recruiter's number seems strangely low or high.

When they ask for your expectations

You can answer with a range, or ask for theirs first. Both are normal.

I'm looking for something in the range of … to … per year, depending on the full package.A range, a unit and room for benefits. Before I give you a number, could you share the range you have in mind for this role?Polite and very common. Based on my research and my experience with…, I'd expect something around…Shows the number is not random.

Choose the bottom of your range carefully. Many recruiters will treat it as your real number.

When the offer is lower than you hoped

You do not need to accept or refuse on the spot. These sentences keep the conversation open:

Thank you, I appreciate the offer. It's a bit lower than I expected.Direct, no apology. Is there room to move on the base salary?The simplest negotiation question there is. If the base is fixed, could we look at a sign-on bonus, extra days off or a review after six months?Other parts of the package. Can I come back to you by Friday?Asking for time is standard, not weak.

Asking for a raise with a manager who speaks English

A raise conversation is different from a job offer: you are talking to someone you work with every day. Three steps work well: book the meeting, bring evidence, make a clear request.

Could we schedule some time next week to talk about my compensation?Nobody likes salary surprises in a regular one-to-one. Since my last review, I've taken on… and delivered…Specific results, ideally with numbers. I'd like to discuss bringing my salary in line with that. I was thinking of…A clear request with a number. If that's not possible now, what would I need to show to get there by the next review?Turns a 'not now' into a plan.

A short example

Recruiter: So what are you looking for, salary-wise?

You: I'm looking for something between … and … per year, before tax. Is that in line with your budget?

Recruiter: It's at the top end of what we had planned.

You: I understand. Since the role includes mentoring two junior developers, which I've been doing for the past year, I think the upper part of the range is fair. Is there any flexibility there?

Notice what is not in this dialogue: no apologies, no long explanations and no immediate agreement. That is less about English and more about confidence. But having the sentences ready removes a big part of the stress.

Practise the uncomfortable part

Reading phrases is easy. Saying "that's a bit lower than I expected" out loud, to a person, is the hard part, and it gets easier only by doing it a few times before it matters.

Preparing for the rest of the interview? Start with Tell me about yourself: answers for developers who are not native speakers.