Internal Transfer Negotiation - The Strategy of Changing Teams or Products
You have been on the same team for two years. The product has matured, sprints are predictable, and the codebase feels too small for you. You think about leaving the company, but you like the team, the package is decent, and you do not want your tenure clock to reset to zero. The team next door is spinning up a new product. Different stack, different problem, different velocity. Telling your manager "I want to move there" is not enough, because an internal transfer is really changing jobs without resigning. You get a new role, a new manager, new objectives. In other words, a new offer. And like every offer, it has a negotiation attached.
Internal transfers in the Turkish software industry are often assumed to be "settled with a friendly chat." They are not. If you skip the negotiation, six months later you find yourself with a damaged relationship to your former manager, a salary lower than your old one, and a tenure clock that quietly reset. This piece covers which axes you should negotiate on, which traps to avoid, and how to build leverage without putting the resignation card on the table.
Is an Internal Transfer Actually a Negotiation?
Most engineers treat an internal transfer as a "request." A request is a polite ask; a negotiation is a two-sided exchange. If you miss this distinction, you end up saying: "I would like to move to team Y, is that possible?" When the answer is "not right now," you have nothing left to work with.
Frame the negotiation like this. By leaving your current team, you impose a cost on the company: a backfill hire, handover overhead, short-term velocity loss. In exchange, you bring value: an immediately productive engineer on the target team, with no recruiter spend. The balance between these two scales is the negotiation table.
There are three axes within that frame:
- Team axis: which team, which role, which manager
- Product axis: which product or project, which stack, what level of ownership
- Compensation axis: salary, title, tenure clock, performance cycle
If you only put one axis on the table, the conversation collapses onto a single dimension and the compensation axis usually gets crushed. The "the transfer itself is already a favor, do not bring up money" mindset takes over. The moment you accept that mindset, you have lost the negotiation.
Questions to Answer Before Walking Into the Conversation
Before you sit down with your manager, you need clear answers for yourself. Otherwise the other side starts asking their questions and catches you off guard.
Why are you leaving? Is it escape from the current team, or pull toward the target team? This distinction matters because if your reason sounds like "escape," your manager will pull you into the "let us fix the problem, stay on the team" game. A "pull" framing gives you a stronger posture.
Which team are you going to? Name it. "Some other team" is too vague. If you have already had an informal conversation with the target manager, keep that name within reach. The point is not to say "I will be doing this job," but to say "there is a gap, I am filling it."
When are you moving? End of sprint, end of quarter, end of year? How long do you need for handover? How long can the target team wait for you? The intersection of those three time windows is your negotiation range.
What is your fallback if the transfer is denied? This answer is your BATNA - your best alternative to a negotiated agreement. If your honest answer is "I will stay and swallow it," your leverage is zero. If it is "I will give it two more months and start preparing to look outside," your leverage is moderate. If it is "I will have an outside offer within three months," your leverage is high. Do not sit at the table without being honest with yourself.
The First Conversation With Your Manager - How to Open
The most common mistake is opening the transfer conversation incorrectly. "I am thinking about leaving" is a threat, and you do not actually want to threaten. "I am interested in the new project on the other team, can we talk?" is too vague - the kind of opener that lets your manager push the meeting six weeks down the calendar.
The right opening is three parts:
"I would like to talk about a career topic with you, and I want to solve it inside the company. I have been in my current role for X time and my growth curve has slowed down. Team Y's new Z product overlaps with where I want to go. I would like to discuss how we can plan this transfer."
Let us unpack what that does. Sentence one signals rotation, not departure, so it does not push your manager into defensive mode. Sentence two gives a concrete reason - stronger than "I am bored." Sentence three names the target, removing ambiguity. Sentence four puts the ball in your manager's court but frames the question as "how do we plan this," not "is it possible" - the assumption is positive.
Your manager will typically respond in one of three ways.
Type one - "Not right now, we have a project on." This is usually not a bluff; your manager's KPI partly depends on your output, after all. But focus on the words "right now." Ask: "Understood. After when would it be possible?" If they say three months, the window is open. If they say six months, push back that the target team cannot wait that long. Managers often try to say "not now" hoping you forget about it over time; putting a date on the calendar prevents that.
Type two - "You are valuable, why would you leave, let us fix it." This is the classic retention move. The dangerous part: it pretends to fix things that are not fixable. Boredom does not get fixed; "wanting to learn new technology" can be partly fixed inside your current team but is not the same as actual experience on the target team. Be polite but firm here: "This is not a leaving conversation, it is a transfer conversation. Is there a reason we cannot move forward with the transfer?"
Type three - "Sure, let us start the process." This looks like the best case but has its own traps. Your manager will assume the process is fast and will skip details. You should not skip them. Title, package, tenure clock, performance cycle, handover duration - all of it should be in writing. Do not trust "I will handle it, do not worry"; you should know exactly what HR has on file.
Negotiating on Three Axes - Team, Product, Package
Once you get the green light, the real negotiation begins. Do not think one-dimensionally. All three axes belong on the table.
Team Axis
Knowing which team you are joining is not enough on its own. What role you take is decisive. Same title, promotion, lateral move? "Same title" is a default assumption that should be questioned. If the work the target team needs from you is one level above your current title - say, technical lead on a new product - you should negotiate a promotion. The "I am moving as a Senior but doing Lead work" arrangement comes back as "we expected Senior performance, you are still a Senior" in the next review cycle.
Get to know the target manager beforehand. Have coffee if possible. Read their style: micromanager or autonomy-friendly, harsh or fair on performance reviews, how many people have left the team in the past year. Get this from an engineer on the target team, not from HR.
Product Axis
"A new product" is not enough description. What maturity stage? Greenfield, MVP, or scaling? Greenfield looks attractive but carries risk - if the budget is cut 18 months in, the product shuts down and you are looking for another transfer. A mature product is safer but less exciting. Decide where you are between those two before agreeing to move.
Stack alignment matters too. If the new stack overlaps with your existing experience, you become productive quickly. If it is fully different - .NET to Go, or Java to TypeScript - there is a learning curve, and that curve can show up as "not yet productive enough" in the first review. Negotiate that upfront: "I am learning a new stack, what is the productivity expectation for the first three months?"
Compensation Axis
The most ignored axis and the most expensive one. There are three compensation risks in Turkish software companies during internal transfers.
Salary risk: the target team has a different budget. Sometimes higher (new product premium), sometimes lower (cost center). The "my current salary is preserved" assumption is usually correct but unreliable unless written. Frame the agreement as: "Current package is preserved, and we move my annual review forward to coincide with the transfer."
Tenure clock: in Türkiye, severance is tied to total time at the company, not to a specific team. So an internal transfer does not reset the tenure clock. But some companies have hidden rules like "the bonus or stock vesting clock resets at the start of the new role." Talk to HR about it openly: "Annual bonus, stock vesting, performance review clock - which carry over and which reset?"
Performance cycle: if you transfer mid-year, who reviews you? Does the old manager rate the first half and the new manager the second? Or does the new manager say "I do not know you, this cycle is N/A"? An "N/A" outcome means you lose the raise and bonus tied to that cycle. Settle this before the move.
If there is a vesting schedule - especially at companies with stock options - ask whether the transfer affects the schedule. Usually it does not (same company), but stay alert for surprises like "the new role is subject to a fresh cliff."
Severance and the Legal Frame
This part is critical because many engineers get it wrong. In an internal transfer, your employment contract does not change; only your job description is updated. Your severance does not reset, your accrued vacation is preserved, your social security premiums continue without interruption. This is the explicit position under Turkish labor law.
But some companies push to have you sign a "new employment contract." Watch for this. If HR brings you a new contract:
- The start date and the company entity must remain the same (only the position changes)
- There must be no language like "the previous contract is terminated"
- It should ideally be an "addendum" rather than a new contract
- If you have a lawyer friend, show it to them before signing
If the company insists on a "new contract," ask why explicitly. "It is our HR process" is not enough; ask the concrete question: "How does this affect my severance?" Get the HR answer in writing. Verbal guarantees get forgotten in a few years.
You can find the details of severance and resignation processes here.
The Resignation Card and Leverage
There are two ways to bring the resignation card into a transfer negotiation: implication and explicit threat. They are different things.
Implication sounds like: "If this transfer does not happen, I might have to continue my career somewhere else." This sentence is polite, professional, and clear. It does not panic your manager but the message lands.
Explicit threat sounds like: "If the transfer does not happen I will resign, I have an outside offer." This sentence burns the relationship. If your manager says "go ahead, resign," there is no way back. If they say "what would it take to keep you," the conversation has shifted into a retention play - a different dynamic, covered in the counter-offer post.
To stay at the implication level, know the difference between actually looking outside and telling your manager you are looking outside. Do the first; do not announce the second. If your manager asks "do you have any offers," a clean answer is: "I am not actively interviewing, but if this is not resolved I will start."
The foundation of the negotiation: be ready to leave, but do not need to leave. As long as you hold that balance, both sides act fairly. The moment the balance breaks - either you need it too much or you have grown bitter - you lose the negotiation.
Preserving the Relationship With the Old Team
Suppose the negotiation succeeds and the transfer goes through. The relationship with your old team is the part that gets ignored, and it bites back a year later when you switch elsewhere. The industry is small; your former manager can be called as a reference at another company.
Three practical rules:
Do the handover properly. Handover should be at least four weeks, ideally six. Use that duration as a negotiating chip in the package conversation: "I am leaving, but I am leaving cleanly." The "this person is professional" feeling your old manager carries away is your long-term credit.
Once on the new team, stop talking about the old team. Sentences that begin with "back on my old team we used to..." are not welcome on the new team. Listen, observe, learn the new team's dynamics. The first three months are observation mode.
Schedule monthly coffees with your old manager. For three months. Then quarterly. The relationship stays alive without effort, and when a future reference call lands, the answer is a guaranteed "yes, same engineer, very good."
The First 90 Days After the Transfer
Pre-transfer negotiation matters, but the 90 days after the transfer matter just as much. The first three months on a new team are your unofficial "probation period." If you are not productive quickly during those three months, the "we should not have brought this person over" narrative starts, and recovering from it is hard.
First 30 days: listening. Speak less in stand-ups, read the codebase, learn how the team operates. Land a quick win - a small bug fix or cleanup PR - as a symbolic "I am here and I am shipping" signal.
Days 30-60: small feature ownership. Take one feature end to end, write the design doc, request code reviews, ship it. Closing that small loop is your competence proof.
Days 60-90: contributing to team dynamics. Not just code: bringing a useful idea in retrospectives, doing meaningful PR reviews for others, improving documentation. These are the inputs to the "good team member" rating in your performance review.
You can find a detailed 90-day playbook here.
The Most Common Mistakes
Mistake 1: Approving the transfer before negotiating the package. Once you have said "yes," your room to negotiate compensation collapses.
Mistake 2: Trusting the new manager's verbal promises. "I will open a Lead position for you in six months" disappears in six months unless it is in writing.
Mistake 3: Saving the conversation with the old manager for last. By the time they hear the transfer is in motion, the old manager goes reactive. Talk to them first, then the target manager and HR.
Mistake 4: Transferring in the middle of a performance cycle. Mid-cycle moves are a grey area for ratings. If you can, time the transfer to land at the end of a cycle.
Mistake 5: Two consecutive internal transfers in the same company. If you have changed teams twice in two years, your third move gets you tagged as "indecisive." After a transfer, stay on the new team for at least 18 months.
What Should Be in Writing After the Negotiation
After the conversation closes, HR will share an email or document about the new role. The non-negotiables in that document:
- New position title and job description
- New manager's name
- Transfer date
- Salary information (if preserved, the explicit phrase "current package is preserved")
- Confirmation that the tenure clock continues without interruption
- The next performance review cycle and method
- Transfer of the accrued vacation balance (automatic, but written confirmation is a good idea)
- If salary or bonus clocks change, the effective date
If the document is missing any of these, go back to HR and ask. "We agreed verbally" is not enough. Six months later, different people sit in HR and they do not remember the verbal agreement.
A Note From getSalary Data
In the getSalary 2026 dataset, engineers who did internal transfers had an average raise that was about 18 percent lower than engineers who left the company entirely. That gap is the structural negotiation ceiling between "moving inside" and "moving outside." The advantage of an internal transfer is not the raise; it is the preserved tenure clock and ecosystem. Sit at the table accepting that.
If you get a 5-10 percent raise on an internal transfer, you did well. Above 15 percent is exceptional. A flat 0 percent means you skipped the negotiation. If that happened, start looking outside three months later, because if the transfer is "good but not enough," staying becomes the second loss.
Closing
An internal transfer is changing jobs without resigning. That sentence is both an opportunity and a trap. Opportunity, because tenure, ecosystem, and relationships are preserved. Trap, because the comfort of "I am already inside" makes you skip the negotiation, and you pay for the skipped negotiation a year later.
Three axes: team, product, package. Put all three on the table. Open the first conversation correctly, hold leverage at the implication level, avoid explicit threats. Do the handover cleanly, keep the old manager warm. Be quiet but productive in your first 90 days on the new team. Always ask for the document.
If you want a quick view of the salary trends in the industry and how different roles are paid before walking into a team negotiation, take a look at the Dashboard. Learn what the market pays for the target team's stack, then sit at the table.