Junior to Mid Developer - How to Ask for the Promotion
The "Just Do Good Work and They'll Notice" Myth
Most Junior developers in Türkiye's software sector wait for the Mid title the same way: write code, close tickets, finish sprints, and eventually the manager will notice. This strategy rarely works.
The Mid title doesn't come from waiting - it comes from asking. But asking isn't a random "when can I get promoted?" question. It's a prepared, well-timed, evidence-based conversation. This post shows you how to have that conversation.
Who Is a Mid Developer?
First, let's clarify the definition. There's significant inconsistency across companies: some promote at 2 years, others still have "near-senior expectations" at 5 years.
But beneath the title chaos, a few core criteria remain consistent:
Independent execution: A Junior takes a ticket and asks questions when stuck. A Mid takes a ticket, researches first, and comes back with proposed solutions - or asks questions only then. This difference seems small but accounts for much of a manager's daily stress.
Sphere of influence: A Junior writes their own code. A Mid writes their own code and affects others' - giving meaningful code review feedback, shaping technical decisions, guiding newer team members.
Problem definition: A Junior solves what's in the ticket. A Mid notices when the ticket is wrong and fixes that first.
Look honestly at yourself against these three criteria. If you're meeting all three, you're already working as a Mid - the title is just missing from your contract.
See It Through Your Manager's Eyes
To frame the promotion request correctly, you need to understand what's going on in your manager's head.
Most managers don't make promotion decisions alone. They have to explain them to leadership, HR, or a team lead. "Kadir is a good developer" isn't enough - "Kadir met these specific criteria" requires a concrete justification.
So your job is to make your manager's job easier: you prepare the argument, they carry it upward.
From this angle, the promotion conversation isn't a "please promote me" request - it becomes a business case. You're telling your manager: "Here's what I've delivered, here's what I'm looking for - what do you think?"
When Is the Right Time to Talk?
Timing matters. A poorly timed conversation can waste even the best preparation.
Moments to avoid:
- Mid-sprint - everyone is in delivery mode
- Right after a major incident - the atmosphere is tense
- Budget freeze periods - promotion decisions are already deferred
- Company restructuring - high uncertainty, decisions are on hold
Good windows:
- 4-6 weeks before performance review season - decisions are still being shaped
- Right after successfully delivering a major project - you're in active memory
- When your manager opens a door with "what are you looking for?" in a 1:1
In Türkiye, most companies run performance reviews in January-February or July-August. If you know this cycle, planning the conversation in December or early June is smart.
If you don't know - just ask: "When are promotion decisions typically made?" It's a legitimate question, and very few managers don't have an answer.
Preparation: What Do You Bring to the Table?
The promotion conversation requires preparation. "I've been here 18 months and I do good work" isn't enough.
Your impact record
Document what you've done in the last 6-12 months with concrete examples. Not a dry list - each item needs a result:
- "Reduced API response time by 40%" - what you did and its impact
- "Improved new developer onboarding, first-week questions dropped by half" - measurable outcome
- "Led an auth refactor affecting three teams, zero incidents" - scope breadth
Write this list for yourself first. Then imagine your manager presenting it upward and trim to the strongest 5-6 points.
Your manager's feedback
What was said in your last performance review? If "you need to develop in this area" came up, show concretely what you've done about it. Your manager should be able to say "I told them X, they did X."
If you haven't received clear feedback - which is common - you can request an "alignment conversation" before the promotion talk: "I want to understand what the Mid criteria look like and where I stand right now."
Your salary expectation
Most Juniors come unprepared on this part. Bring a salary expectation alongside the title change, but keep the numbers realistic. Use the Salary Calculator to see Mid medians in Türkiye's software sector by industry, experience, and city.
Don't say "whatever you offer." The party that enters without a number almost always leaves at a disadvantage.
How Do You Open the Conversation?
Direct, but not aggressive:
"I'd like to talk with you about my career development. In the last 6 months I've taken on responsibilities like [major project/achievement]. I believe I'm meeting the criteria for Mid-level evaluation - what's your read on that?"
This framing does several things at once. The agenda is clear (career development), there's a concrete reference (major project), you're asking for an opinion rather than approval (not putting your manager on the defensive), and the conversation returns to you (you'll listen to the response).
Your manager saying "you're not ready yet" is also valuable information. The question to ask then: "What would you need to see to say I'm ready?"
After "Not Yet"
Promotion decisions don't always come immediately. When you hear "not yet," there are two scenarios:
Legitimate "not yet": The manager names clear criteria (finish this project, demonstrate this skill). That's a roadmap you can track, document, and update every 3 months.
Vague "not yet": "Wait a bit longer" or "budget isn't there but we definitely see you." This ambiguity signals one of two things: either the manager is genuinely budget-constrained (worth verifying) or the promotion isn't coming.
If you're getting clear criteria, meeting them, and the promotion still isn't materializing, it may be time to look outside. Check the salary impact of changing companies - in Türkiye, a job change typically brings 30-50% increase, which often exceeds what internal promotion delivers.
Title vs. Responsibility Gap
One practical note: at some companies, you're doing Mid-level work while being paid at a Junior title. This is more common than it should be.
If you're already operating at Mid level (independent tickets, code review responsibilities, guiding newer teammates), the title conversation shifts from "am I ready?" to "how do I document what I deserve?"
Say this plainly to your manager: "I've noticed I've been taking on Mid-level responsibilities for the past 6 months. What would it take to formalize that?"
The promotion process asks for patience but not passivity, preparation but not aggression. Go to the Dashboard to see the Mid salary range in your sector and walk into the conversation with real numbers.