From Mid to Senior - The Promotion You Can't Get by Waiting
"I Waited, Didn't Get It Last Year Either"
Most Mid developers in mid-career follow this path to the Senior title: keep working, do good work, and eventually the manager will notice. This rarely works.
The Senior title is earned through documentation, not seniority. The difference between a Mid waiting for their seventh year and a Mid promoted in seven months is usually not talent but the ability to present concrete evidence to the manager at decision time.
This article covers concrete steps that accelerate the Mid-to-Senior transition in Türkiye's software sector. Not romantic career advice, but what should be on the table during performance review.
According to getSalary 2026 data, the Mid median salary is 110,000 TL and the Senior median is around 165,000 TL - a 50% gap. The income loss between earning that gap after a year of waiting versus six months of earning it is larger than most developers roughly estimate.
What Is Senior, How Does It Differ From Mid?
Companies usually don't publish a standard definition; they bury it in their promotion rubric. But three criteria stay consistent across the sector:
1. Scope of ownership. A Mid finishes a feature; a Senior can hand off internal design to others, take on its code review, and plan deploy/rollout. If the time from feature kickoff to production doesn't require the manager asking "what's the status?," you're on the Senior side.
2. Working with ambiguity. Mids receive tickets; Seniors write their own. An empty Figma, an ambiguous product hypothesis, or a missing requirement - if you can pull together a question list and gather stakeholders instead of bouncing it back as "insufficient brief," you're on the Senior side.
3. Impact multiplier. Mids do work with their own code; Seniors do work with others' code. Raising the quality bar via PR review, giving technical direction to juniors in 1:1s, and ending a contested decision via RFC all create impact multipliers.
Most companies want all three criteria present. Excellent at one and zero at the other two means no promotion.
Brag Document: Performance Review Is a Process, Not a Year-End Task
This single practice accelerates a Mid's transition to Senior by at least 6-12 months.
Open a notes file (Notion, Obsidian, README.md - doesn't matter), spend 5 minutes every weekend, and write the evidence of what you did that week:
- Which PR did you merge, how many lines, what type of work?
- What review did you do, what bug did you prevent?
- Whom did you ask for help, whom did you help?
- What technical discussion did you join, what decision changed?
- Which metric in production was impacted, how?
When the year-end performance review asks "what did you do last year?", most developers remember the last three months. A developer with a brag document remembers the entire 12 months - and the same applies to the manager's memory.
For the manager to approve your promotion, they need to defend it in calibration. If you don't give them the ammunition they need to defend it, they won't have it. The brag document is ammunition.
Performance Review: How to Prepare?
Companies in Türkiye typically run a 6-12 month performance cycle. Most follow "self-review" → "manager review" → "calibration".
Self-Review
If you have a brag document, self-review takes 30 minutes. You're typically expected to answer three questions:
What did you do this period? - Pick 5-7 standout achievements from your brag document. For each: context (situation), action (what you did), result (impact). Not "I did frontend optimization," but "I reduced homepage first render time from 3.4s to 1.6s, bounce rate dropped 12%."
What did you learn? - Write at least two technical developments: a new technology, an area you deepened, a design problem you solved.
What are your goals for next period? - If you're requesting Senior, this is where it goes. Scope/authority increase requests like "I want to own the design of project X, I want to mentor junior Y" appear here.
If you're requesting Senior, write it openly in self-review: "This period I owned the payment flow rewrite, demonstrated evidence for the scope of ownership criterion, and performance improved by 30%. I want to start the conversation about promotion to the next level."
Managers can pretend they didn't read it if they don't see this line. One sentence, clear request.
Manager 1:1s
Performance review isn't a year-end thing; it's accumulation built in every 1:1. Bring up Senior promotion signals at least once a month:
- "Last sprint I led the design of feature X and explained it to junior Y. Does that count toward [scope of ownership] in our Senior rubric?"
- "What is the promotion committee currently looking at? What evidence should I be building?"
- "Can we open a Senior conversation in the next performance period? I'd come prepared."
These questions aren't embarrassing; they're professional. Thinking about your career is your manager's job, but you initiate that thinking.
Typical Promotion Obstacles in Companies in Türkiye
Obstacle 1: Vague rubric
Some companies don't have a "Senior rubric" written as a document. When you ask the manager, you might hear "we don't think in stages like that." Two options:
- Ask the manager: "What do people called Senior here do that separates them from Mid? Three examples would be ideal." The answer provides calibration.
- If the company is 50+ people, there's likely a Notion document someone wrote. Ask, find it.
If there's no written rubric and the manager doesn't have a clear answer either, the promotion policy is effectively "manager discretion." Bad news: even accumulating evidence may not be enough because there's no shared decision framework.
Obstacle 2: "No open position"
A common answer in Türkiye: "We want a Senior, but there's no budget for the Senior title this year." This is often a polite no.
How to test: ask directly. "This year or next year? Under what conditions does it open?" If the answer is vague or recurring stalling, that's enough signal to start looking externally. The job hopping article's data is meaningful here: a 40-60% salary increase comes with the Senior title at the new company.
Obstacle 3: "You haven't mentored a junior"
Mentorship evidence is the silent requirement of seniority promotion. If you've been at the same company for 3+ years and never sat next to a junior, the gap will be felt in the Senior conversation. Quick way to close it: in the next period, say to a junior (even informally) "I can support you on this task" and reserve a 1:1. Write educational comments in PR reviews and add this to the brag document too.
Senior Salary Negotiation
After the promotion is approved, the salary increase usually doesn't come automatically. Typical Mid → Senior promotion raises in companies in Türkiye are 15-25%, but Senior median is 50% higher than Mid median (132,500 TL → 165,000 TL band). The gap is found by positioning yourself in the external market as a Senior.
What to do: in the promotion conversation, treat salary as a separate topic. "Thank you for the Senior title. I want to benchmark on the salary side - getSalary's median is in the 165,000 TL band; where can our offer move?" This sentence isn't aggressive, it's data-driven.
When the manager responds with "this much budget exists," you have no obligation to accept without an outside offer. Step one is getting the promotion; step two is testing the market; step three is either staying or leaving.
If the Person Waiting Is You
Some Mids think the manager is waiting, but actually the manager is waiting for them to ask. From the manager's perspective, there's a truth here: a passive Senior candidate already doesn't fit "scope of ownership." Saying clearly that you want to be Senior is itself part of that criterion.
A table for the next three months:
- This week: Open the brag document, backfill the last three months.
- This month: Tell your 1:1 you want to discuss the promotion path.
- Three months from now: Write the explicit request in self-review, enter the performance period with evidence.
The Senior title isn't a gift, it's a thesis to be defended. If you don't prepare your thesis, no one will prepare it for you.