Internal Rotation - Changing Jobs Without Changing Companies
Switching Jobs Without Changing Companies
You're tired of your current team or you want to move into a new area in your career. The first thing that comes to mind is looking outside, but there's another option inside the company: rotation. Switching to a different team, a different product, or a different tech stack within the same company is an option most engineers don't consider seriously enough.
Rotation carries less risk than searching outside. You keep your current salary and seniority, you skip the stress of the first six months at a new company, and you already know the culture. But the process isn't free. If you handle the relationship with your manager, the career timeline, and the salary adjustment poorly, rotation can become more exhausting than just leaving.
This piece covers how internal rotation works in Türkiye's software sector, when it makes sense, and what traps to avoid.
When Does Rotation Make Sense?
Two healthy reasons drive rotation. The first: your current work is done or your interest has shifted. Writing the same CRUD screen for three years, finishing a project, or wanting to move into a new area like ML, platform, or mobile fits this category. The second: there's no growth left in your current team. You're waiting for a senior promotion but the role is filled, or the team itself is shrinking.
In both cases, rotation benefits both you and the company. The company doesn't lose an experienced engineer; you open up a new career path without starting from scratch.
But there are also bad reasons. The most important: escaping your current manager. Asking for rotation because of a conflict with your manager usually doesn't work, because that manager will be involved in the rotation decision. A transfer they block either never happens or wears you out badly. If your goal is to move away from your manager, looking outside is usually faster.
Another wrong reason: chasing a raise. Rotation doesn't bring an automatic salary bump. If the new team is explicitly asking for a higher seniority, that's different, but switching to another team at the same level is salary-neutral on its own.
How Does the Process Work?
Rotation procedures vary by company. Larger companies (Trendyol, Getir, Hepsiburada, Türk Telekom) have open internal application systems; smaller companies run the process semi-formally.
Typical steps look like this:
Identify the target team. Look at internal job listings, and if possible, have an informal conversation with the target team's manager. Don't skip this step; applying through formality alone increases the chance of rejection.
Tell your current manager. This is the sensitive part. Hearing about your rotation request through another channel is something a manager takes personally. If you don't tell them yourself, the relationship breaks.
Formal application. Through HR or the internal mobility platform. The target team needs an open position or one needs to be created.
Interview. Most companies treat internal rotation as a kind of interview process too. It's not a from-scratch external interview, but the target manager needs to say yes.
Transition date negotiation. Handover time at the current team, start date at the new team. Usually a 4-8 week transition window.
Practical advice: don't skip the order between steps 1 and 2. Talking to the target team without telling your current manager usually backfires; information spreads quickly inside a company.
Manager Relationship - The Riskiest Part
The hardest part of rotation is moving to another team without breaking your current manager. Most managers are professional about this, but individual reactions vary.
A manager typically reacts in one of two ways. First: approves and smooths the transition. This depends partly on your value, partly on the current team's workload. Second: blocks. A "we have things to ship now, let's revisit in 6 months" type response. The block is sometimes legitimate (a critical release is in progress, the team has already shrunk) and sometimes personal (the manager doesn't want to lose you).
It matters whether the block is legitimate. If the manager keeps the door open for 6 months later and the reason is concrete (let's finish project X first), respecting that makes sense. But if the reason is vague or the timeline is undefined ("let conditions change first"), understand that the manager will never approve. At that point, talking to HR or escalating through the target team's manager becomes necessary.
In another scenario, the manager may make a counter-offer to keep you. New responsibilities, a promise of promotion, more control over a project. These promises don't mean much if they're not tied to specific dates or aren't in writing; no matter how senior you are on the current team, verbal commitments aren't guaranteed. Evaluating a counter-offer is its own topic - the counter-offer guide walks through this in detail.
Will the Salary Be Adjusted?
Rotation doesn't bring an automatic raise. Moving to another team at the same seniority means the same salary. If the move also includes a level promotion (Mid to Senior, Senior to Staff), there can be a salary adjustment, but unless that's written into the rotation decision, it doesn't happen automatically.
A practical tip: ask for your salary to be reviewed during the rotation conversation. "Which seniority band do I land in on the new team, and where does my current salary sit in that range?" Ask this directly. If your salary is below the new team's seniority band, ask for an adjustment along with the rotation. Take the rotation advantage now; if you're told "we'll do the raise after rotation," you may end up waiting 12 months.
Some companies handle the rotation raise inside the formal annual review process. Then you get the raise later but more systematically. Ask HR about company policy.
Which Roles Are Easier to Rotate Into?
Rotation flows more easily for some role types. Backend to frontend, mobile to web, application to platform/infra are typical rotation patterns. Most existing skills transfer; the from-scratch learning takes 3-6 months.
Harder rotations: backend to ML, application to security, classic web to game development. These require additional technical preparation; sometimes the company supports this with a training budget, sometimes you're expected to do it on your own time.
Going from a manager/lead role back to IC is also a kind of rotation but especially sensitive. In most companies, once you give up a lead position, getting it back isn't easy; that's why this should be approached as a permanent choice rather than a temporary detour.
Most Common Mistakes
1. Surprise channel. Flirting with the target team without telling your current manager. Information spreads inside a company in minutes; if they hear about it, rotation becomes impossible.
2. Rushing. Pushing for "let's decide this week." Rotation decisions usually take weeks; pressure pushes both your manager and the target team away.
3. Slacking on current work. You need to keep doing your job until the rotation decision lands. Leaving half-finished work in the handover both wrecks your professional reputation and turns the manager's exit review negative.
4. Not keeping a paper trail. Verbal offers and processes are unreliable. The rotation decision, the start date, and any salary adjustment should be confirmed in writing through some channel (email, HR platform).
5. Slamming the door on the current team. Making a critical exit (especially mentioning negative reasons about the team or manager) does serious damage. You're staying in the same company; these people will show up on another project next week.
Rotation or Resignation?
A few criteria mark the line between rotation and resignation. Rotation makes more sense when:
- You're broadly satisfied with the company but not the current team
- Your current salary is good and above the market average
- You want a tech change but not a whole new company environment
- The company's stock options or ESOP haven't vested yet
Resignation makes more sense when:
- You want to change company culture (not just the team)
- Your current salary is clearly below market
- Your manager or seniors are professionally toxic
- You're no longer aligned with the company's long-term vision
Rotation is a small reset. Resignation is a big reset. Knowing which one you want up front keeps the process running through the right channel from the start.
What's Next
If you're tired of your current team, scanning internal options before looking outside is worth doing. Grabbing a coffee with HR, checking open internal positions, having an informal chat with a senior on the target team - these are low-cost, high-information moves.
The first salary negotiation guide covers how a new-position salary negotiation is set up; the same principles apply in rotation conversations. The annual raise negotiation guide covers raise negotiation if you're staying put.
Rotation done right is a career move equivalent to leaving and switching jobs but with less risk. Done wrong, you neither make it into the new team nor keep your standing on the old one.