How to Negotiate a Raise as a Software Engineer in English

Asking for a raise as an engineer works best when framed around specific, demonstrable impact rather than effort or tenure alone — the strongest version of this conversation reads like a well-documented case, not a personal appeal.

---

Requesting the Conversation

Ask for dedicated time rather than raising it casually in passing.

• “I’d like to set up some time to talk about my compensation — is there a good time this week or next to discuss it?”
• “I want to have a focused conversation about my role and compensation, based on the impact I’ve had over the past few quarters.”
• “Before our next one-on-one, I wanted to flag that I’d like to spend part of it discussing my level and pay.”

Presenting Your Case

Lead with concrete, specific accomplishments rather than general statements.

• “Over the past two quarters, I led the migration that cut our deployment time by 40%, and I’ve taken on mentoring two junior engineers.”
• “I’ve been operating consistently at a senior level for the past six months — taking ownership of cross-team projects and making architectural decisions independently.”
• “Based on the scope of what I’m doing now compared to when my current level was set, I believe a compensation adjustment is warranted.”

Referencing Market Data Professionally

Bring external context without sounding like an ultimatum.

• “I’ve looked at market data for this role and level, and I want to make sure my compensation is aligned with that — I’m happy to share what I found.”
• “I’m not asking based on another offer, but based on comparable roles in the market, I believe there’s a gap worth discussing.”

Responding to Pushback

Stay calm and specific if the initial answer is uncertain or negative.

• “I understand budget constraints exist — could we discuss a timeline for revisiting this, even if it can’t happen immediately?”
• “I appreciate the honesty. Could you help me understand specifically what would need to be true for this to move forward next cycle?”
• “That’s helpful context. In the meantime, is there anything non-monetary — like title, scope, or professional development budget — that could be part of this conversation?”

Closing the Conversation

End with clarity on next steps, regardless of the outcome.

• “Thank you for considering this. Can we agree on a specific date to follow up, so this doesn’t just quietly drop?”
• “I appreciate you hearing me out — I’ll follow up in writing with a summary of what we discussed.”
• “I’m glad we could have this conversation directly — it means a lot that I can bring this kind of thing to you openly.”

---

Vocabulary Reference

Term	Meaning
Compensation	The full package of pay and benefits an employee receives
Level	An organization’s internal ranking of seniority, often tied to pay bands
Market data	Compensation benchmarks gathered from comparable roles across companies
Scope	The breadth and complexity of responsibility someone holds in their role
Pay band	A defined salary range associated with a specific level or role

---

Key Takeaways

• Ask for a dedicated conversation about compensation rather than raising it casually or in passing.
• Lead with specific, measurable accomplishments instead of general statements about effort or tenure.
• Reference market data professionally, as supporting context rather than as leverage or a threat.
• Stay calm and ask specific questions if the initial response is negative or uncertain.
• Close with a clear next step or follow-up date, regardless of the immediate outcome.

Expanding Your Vocabulary: Professional Phrases for Raise Negotiations

Negotiating a salary increase is rarely simple. It’s not just about stating you need more money; it’s about demonstrating your value to the company and articulating that value in a way that resonates with your manager and potentially, HR. While the core strategies outlined previously – quantifying your achievements, researching industry benchmarks, and practicing confident communication – remain vital, understanding the specific vocabulary used in these conversations can significantly improve your success, especially if you’re still developing your fluency in English. Let’s look at some phrases that go beyond the standard “I deserve a raise” and focus on building a compelling case.

One common pitfall is framing the conversation solely around personal needs. Instead of saying “I need more money to cover my bills,” which feels transactional, aim for language that highlights your contributions. Consider this Slack message you might send after successfully completing a complex feature: “Hey [Manager’s Name], just wanted to share that the integration with the new API is complete and performing smoothly – initial tests show a 15% improvement in response times. Really pleased with how this turned out!” This immediately demonstrates impact, not simply your desire for compensation. Similarly, when describing your work in a pull request description, avoid phrases like “Fixed a bug.” Instead, try “Implemented a robust error handling mechanism to prevent data corruption and improve overall system stability.” The more precise the language, the stronger the impression you make.

Another area where careful phrasing matters is during a code review. If a reviewer suggests improvements to your work, responding with something like, “That’s a valuable point regarding maintainability. I’ll certainly incorporate that into the next iteration – I appreciate the feedback on streamlining the logging system as well,” shows you’re receptive to constructive criticism and focused on continuous improvement. It’s about demonstrating professionalism and a collaborative approach. Remember, your manager is likely assessing not just what you did but how you responded to feedback.

Finally, when discussing expectations for future contributions – perhaps outlining new features or responsibilities – avoid vague statements like “I want more responsibility.” Instead, propose specific goals: “I’m confident I can lead the development of the user authentication module, which aligns with the company’s strategic focus on security and would allow me to leverage my expertise in OAuth 2.0.” This demonstrates foresight and a commitment to contributing strategically to the team’s objectives – language that will be far more persuasive than simply asking for “more work.”