English for Salary Negotiation in Tech
Practical English phrases and strategies for negotiating your salary as a software engineer — from the initial offer to the final agreement.
Salary negotiation is one of the most financially impactful conversations you will have in your career — and for non-native English speakers, it can feel especially high-stakes. This guide gives you the exact phrases to use at every stage of a salary negotiation, from receiving the initial offer to reaching a final agreement.
Why Negotiation Is Expected
In the tech industry, almost every employer expects candidates to negotiate. Accepting the first offer without discussion often leaves money on the table. Negotiating professionally signals confidence and self-awareness — not greed.
A key mindset shift: you are not asking for a favour. You are completing a business negotiation between two parties who both want to reach an agreement.
Responding to the Initial Offer
Never accept or reject on the spot. Buy time to evaluate:
“Thank you — I’m genuinely excited about this opportunity. I’d like to take a day or two to review the full package. Is that okay?”
“I appreciate the offer. Before I respond formally, could you send me the full compensation details in writing?”
“This is encouraging. I’d like to take 24 hours to review it carefully. I’ll come back to you by [date].”
This is not stalling — it is standard professional practice. Any employer who pressures you to decide immediately is a red flag.
Researching Your Number
Before the negotiation call, research the market rate for your role, location, and experience level. Common resources include Glassdoor, Levels.fyi (for US tech companies), LinkedIn Salary, and industry surveys.
Useful framing for your research:
“Based on my research into the market rate for this role in [city/country], and given my [X years] of experience, I was expecting something in the range of [number].”
Making the Counter-Offer
Be specific. A specific number is taken more seriously than a range:
“Thank you for the offer of £70,000. Based on my experience and the market rate for this level in London, I was hoping for something closer to £78,000. Is there flexibility there?”
“I’m very interested in the role and want to make this work. The base salary is a little below what I was targeting — I was looking for £85,000. Is that achievable?”
“I appreciate the offer. My current compensation package is [amount], and given the move I’m making, I was aiming for [number] as a base. Can we explore that?”
Important: State your number, then stop talking. Do not fill the silence.
When They Can’t Move on Base Salary
Sometimes the base salary is fixed. In that case, negotiate other components:
“If the base is fixed, would there be flexibility on the signing bonus?”
“Could we look at an earlier performance review — say, after six months instead of twelve — with a salary adjustment at that point?”
“What about additional equity? Would there be room to increase the stock options component?”
“I understand the base is set. Could we discuss remote work flexibility / additional annual leave / a training budget?”
Total compensation includes: base salary, bonus, equity (shares/options), signing bonus, pension contributions, and benefits. Consider all of these in your negotiation.
Handling Pushback
When they ask what you currently earn:
In many countries (UK, parts of the EU, US), you are not required to disclose your current salary. You can deflect:
“I’d prefer to focus on the value I’d bring to this role and the market rate, rather than my current salary. My target for this role is [number].”
When they say the offer is their best:
“I understand. I want to be transparent: this is important for me to get right, as I’m evaluating a couple of options. If there’s any room to move, even modestly, it would make it easier for me to commit.”
When they ask why you deserve more:
“In my current role, I [specific achievement — delivered X, reduced Y, led Z]. I believe that level of impact is reflected in the range I mentioned.”
Accepting the Offer
“I’m delighted to accept. Thank you for working with me on this — I’m looking forward to joining the team.”
“I’m happy to accept on those terms. Could you send through the updated offer letter so I can sign?”
Key Vocabulary
| Term | Meaning |
|---|---|
| base salary | Fixed annual pay before bonuses or equity |
| total compensation | All elements combined: salary + bonus + equity + benefits |
| signing bonus | One-time payment when you join |
| vesting schedule | Timeline for when equity becomes yours |
| cliff | Minimum time before any equity vests (typically 1 year) |
| counter-offer | Your response proposing different terms |
| leverage | Your negotiating strength (competing offers, unique skills) |
Negotiating in a second language is genuinely difficult — but the stakes make it worth practising. Read your phrases aloud before the call. Confidence in delivery matters almost as much as the words themselves.
Expanding Your Vocabulary: Phrases for Non-Native Speakers
Negotiating a salary in tech, regardless of your native language, hinges on more than just stating a number. It’s about demonstrating value, understanding market rates, and confidently articulating your expectations. For developers who are still building their professional English vocabulary, this can feel particularly daunting. The subtle nuances of phrasing – the difference between “I’m looking for” and “I need,” or “That’s a bit low” versus “I was hoping for something closer to…” – can significantly impact how your offer is received. Don’t be afraid to ask clarifying questions; it demonstrates engagement and a desire to fully understand the situation. Remember, active listening is just as crucial as effective speaking.
A common hurdle for non-native speakers is framing feedback constructively. During a code review, for example, simply saying “This isn’t good” won’t achieve much. Instead, focus on specific areas for improvement. “I noticed some complexity in this section; perhaps we could refactor it to improve readability and maintainability?” or “Could we explore alternative approaches to this algorithm? I was wondering if a simpler solution might be more efficient.” These phrases demonstrate technical understanding while offering suggestions – key elements of professional communication. Similarly, when discussing a pull request description, avoid overly literal translations. Instead of “This change fixes the bug,” try “I’ve addressed the reported issue with this update, ensuring stability and preventing future occurrences.”
Another area to focus on is expressing your value proposition. Rather than simply stating your years of experience (“I have five years of experience”), which can feel vague, consider framing it around accomplishments and impact. “In my previous role, I led the development of [project], resulting in a 20% increase in user engagement” or “My expertise in [specific technology] allowed me to streamline our workflow and reduce operational costs.” These statements quantify your contributions and highlight your value to the company. Practicing these phrases out loud – even with a friend or colleague – can dramatically improve your confidence and fluency during salary discussions.
Finally, be mindful of common idioms and expressions. Phrases like “thinking outside the box” or “low-hanging fruit” are frequently used in tech conversations but might not translate directly into your native language. Don’t hesitate to politely ask for an explanation if you encounter one you don’t understand. Showing a willingness to learn and adapt is highly valued, and often leads to positive interactions. Remember, the goal isn’t just to negotiate a salary; it’s to build a strong professional relationship based on clear communication and mutual respect.