Annual Raise Negotiation - Bargaining to Stay Is Harder Than Bargaining to Leave
Staying Is a Negotiation Position
Job hoppers and stayers are not getting the same raise. This has become one of the most-cited statistics in Türkiye's software sector over the past few years: developers who rotate jobs capture 40-60% nominal jumps, while those who stay at the same company average a raise close to or below inflation. The visible result: as experience grows, salary growth slows, and loyalty gets penalized.
But not every developer wants to switch companies every six months. You like the team you're on, the problem domain interests you, you don't want to relocate, or you're simply tired. The catch: staying is also a negotiation position - if you don't bargain for yourself, no one bargains in your place.
This article is about how to structure annual raise negotiation when you've decided to stay. What to do when a counter-offer arrives and the salary impact of job hopping are separate articles. Here we answer a different question: how do you stay in real-terms gain by remaining in the same place?
An Inflation-Indexed Raise Is Not a Real Raise
This distinction has to come first. "I got a raise equal to inflation, that's fine" is a trap. A raise equal to CPI is in fact zero real growth - you are running in place. Your career experience curve should advance every year, but if you are running in place, your seniority is not translating to your salary.
According to getSalary 2026 data, the median developer salary in Türkiye is 132,500 TL, with a 35.9% nominal annual raise against 29.53% CPI - which means a sector average of roughly 5% real gain. So the first 29.53% of your raise is "running in place", and the 5% on top is the real gain. Your goal in negotiation is to push that 5% to 10-15%.
Two rough categories:
Reasonable raise (the stayer's real target):
- CPI + 8-12 percentage points real gain
- Recognition of earned tenure (e.g., second year as a mid)
- Compensation for performance and scope expansion
Insufficient raise (accept it and you'll rotate within 12 months):
- Below-CPI "tight budget this year" raise
- A raise equal to CPI marketed as "inflation-indexed"
- 1-3 points above CPI as "goodwill"
Where your position sits on this spectrum determines the tone of the negotiation.
Timing the Ask - Move Before Year-End
In Türkiye's software sector, raises are mostly given at the start of the calendar year or fiscal year. This means the negotiation needs to start in the September-November window. By the time you learn about the raise in December, it is too late to change anything.
Timing table:
| Period | Action | Reason |
|---|---|---|
| Early September | Start gathering data | The budget is not yet locked |
| September - October | Open the first conversation | Your manager begins forming a position |
| Late October | Make the formal ask | Manager has time to escalate to leadership |
| November | Negotiation and revision | Budget decisions are taking shape |
| December | Awaiting decision | Most companies have approved raises |
| January | Raise announcement | Negotiation window has closed |
If you open the negotiation in December, your manager saying "I submitted our budget last month, there's nothing I can do now" is fair. If you open it in September-October, they have to say "let me think about it, let's work something out".
One more note: a raise negotiation is not a single meeting but a process of three or four conversations. The first is "I want to flag in advance that I'm expecting a raise this year" - a heads-up. The second is the figure with reasoning. The third is revision or counter-proposal. Trying to compress this into a single sitting is a weak position.
A Demand Without Evidence Is an Insufficient Demand
A developer switching jobs comes to the table with a new offer - a concrete alternative. A staying developer has no such card and must instead bring accumulated evidence.
What evidence?
- Scope expansion across the year: What new area of responsibility did you take on? What things do you now do that you didn't before?
- Measurable impact: A process you sped up, an incident you resolved, money brought in or cost saved
- Mentorship or leadership: Onboarding juniors, code review load, RFC ownership
- Market data: What is the market median for the same role? What does getSalary data say for a profile like yours?
- Performance review notes: Positive feedback in past 1:1s, calibration notes
This evidence has to be accumulated across the year, not gathered in the negotiation week. In our performance review article, under the heading "brag document", we explain how to keep this - the same file works for raise negotiation.
A demand without evidence sounds like this: "I've worked hard this year, I want a raise." The manager has nothing to take to leadership. A demand with evidence sounds like this: "This year I owned project X, process Y got faster, my second year as a mid is wrapping up, market median for my profile shows 165k - I'm thinking 35%." Now the manager has a case to escalate.
How to Respond to "No Budget This Year"
This sentence is one of the most common roadblocks in negotiation. What matters is understanding what it actually means. Three possible reasons:
- There genuinely is a budget squeeze - the company is contracting, runway is short, there were layoffs in the past six months.
- There is a budget, just not allocated to you - a general budget exists but your share is narrow.
- "No budget" is just a formula sentence - it's actually the opening of negotiation, asking "what will you do?"
In the first case there is a real constraint, but the path forward is not closed. In place of base salary: a one-time bonus, extra leave days, learning budget, title change (promotion), role change. These hit a different budget line and are sometimes easier to approve.
In the second and third cases, the underlying message is: if you accept this, the manager doesn't have to come back. "Understood, no budget right now. When does the mid-year review window open? Let's talk again then; in the meantime, what specifically should I deliver against [X, Y, Z]?" This is a moment where the manager both gives you a commitment and notes "I have to solve this".
The wrong response: "Okay, agreed, I accept." That's a verbalized acceptance, the moment the negotiation ends. Next year the same sentence comes back.
Three Scenarios - Where Do You Stand?
Before walking into the negotiation, you have to categorize your position. Three typical scenarios:
Scenario A - Strong position: You owned a critical project in the past six months, you hold indispensable knowledge for the team, you also got an external offer (which you turned down). Your hand is full, so the ask can be high - 35-40% nominal, 8-12 points real gain over CPI.
Scenario B - Middle position: Work is being done well, performance is steady, scope is the same as last year, no external offer. A reasonable ask is CPI + 5-7 points real gain - above the sector average but not aggressive.
Scenario C - Weak position: Last year's review note was average, no scope expansion, you reacted poorly to a critical incident in the past six months, no knowledge monopoly on the team. Before asking for a raise you need to strengthen your position; if you ask today, the risk of receiving a below-CPI raise is high.
Don't blur the scenarios. Pushing Scenario A's ask while in Scenario C triggers a "reality test" from the manager and damages both the negotiation and your reputation.
The Other Side's Mind - Constraints in the Manager's Pocket
It helps to understand the constraints sitting on your manager's side of the table. Your manager wants you to get the raise - if you leave the team, their workload also goes up - but they don't have unlimited authority.
Typical constraints:
- Budget windows: Two budget revisions per year (typically January and July). Granting a raise outside of these windows requires leadership approval.
- Internal equity (calibration): Your salary has to be balanced with other mids on the team. Giving you 35% while your peer gets 15% creates a problem.
- Annual raise percentage cap: The total company budget is X percent, distributed across the team.
- Leadership approval: Raises above a certain threshold (e.g. 30%+) require HR and CFO sign-off.
These constraints limit how effective the negotiation can be, but they also reveal what your manager can do to help. The developer who says "what do you need from me to get leadership approval, let me help you build the case" is in a different position from the one who only says "I want a raise".
Quick Recap
- A raise equal to inflation is not real growth, it is running in place. Target: CPI + 8-12 points.
- Open the negotiation in September-October, not December - budget decisions are taking shape in that window.
- A demand without evidence is insufficient - scope, measurable impact, mentorship, market data accumulate across the year.
- "No budget" is not the final word, it is the opening of negotiation. Ask about non-salary items, a date commitment, a list of criteria.
- Categorize your position as A/B/C and calibrate your ask accordingly.
Staying Is Not a Passive Decision
Staying is not a passive decision but an active choice. When passive - "whatever they give, they give" - 12 months later you face a salary that has shrunk in real terms. When active - gathering data, planning timing, coming with evidence, expanding the table with alternative items - staying can be as valuable as rotating.
The data shows it: against a 40% average raise for those who switch, those who stay get 35%. The gap is smaller than it looks - add adaptation time at a new company, the new learning curve, and the cost of rebuilding a team, and a one-year net difference closes substantially. With the right negotiation, "staying" closes the financial gap by half; once you factor in job satisfaction and continuity, it can pull ahead.
In the end, raise negotiation is not a personality test but a year's worth of accumulated evidence turning into a formal conversation. For the developer who comes with a data-driven ask, staying is also a negotiable position.