How to Get Promoted from L60 to L61 at Microsoft
Building your promotion case?
Get AI coaching on what to document and how to present it.
You've been shipping features at Microsoft for over a year. Your Connects feedback is solid, your manager says good things, and yet the promotion to L61 hasn't come through. Nobody tells you this part clearly enough: doing excellent L60 work is exactly what keeps you at L60.
The L60 to L61 promotion, Software Engineer (SDE) to Senior SDE, is the first real inflection point for most Microsoft engineers. It follows the same pattern that drives promotions across big tech: you have to prove you're already operating at the next level before the system catches up. At Microsoft, that means navigating the Connects review system, expanding your scope beyond feature execution, and getting your manager to build the case. This guide covers how all of that actually works.
What Changes from L60 to L61 at Microsoft
Before building your case, understand the gap. L60 and L61 both write code and ship features, but what's expected at each level is meaningfully different.
| Dimension | L60 (SDE) | L61 (Senior SDE) |
|---|---|---|
| Scope | Owns features or modules within a component | Owns medium-to-large features or entire subsystems end-to-end |
| Autonomy | Works effectively with regular guidance from senior engineers | Works independently; self-identifies what needs doing |
| Technical decisions | Contributes to design discussions; implements designs from others | Makes and defends design decisions for their area |
| Impact on others | Helps teammates when asked | Actively mentors L59-L60 engineers; elevates team quality through reviews and knowledge sharing |
| Cross-team work | Collaborates within immediate team | Coordinates across teams when work touches shared systems |
| Planning | Executes work scoped by others | Breaks down ambiguous problems into plans; identifies risks early |
The shift isn't about tenure. It's about moving from "I execute well when given direction" to "I own outcomes and help others execute too."
"At 61, you'll be expected to be a lot more independent and work plus collaborate with just a little guidance, be better at cost estimation."
How Microsoft Promotions Actually Work
Microsoft's promotion system is manager-driven, not committee-based. Your manager nominates you, presents the case to peer managers and your skip-level, and for promotions up to L62, your direct manager approves it. No promo committee reviews packets the way Google does.
This makes your relationship with your manager the single most important variable.
The review system backing this is Connects, Microsoft's semi-annual performance review. Twice a year (roughly January and July, aligned with Microsoft's fiscal year), you write a self-assessment organized around three dimensions:
- Results is about what you shipped, built, or delivered that moved the business forward
- Growth covers how you stretched yourself, built new skills, and took on work outside your comfort zone
- Inclusion is about how you contributed to team health, collaboration, and psychological safety
Your manager reviews your Connect, combines it with peer feedback from Perspectives (Microsoft's 360-feedback tool), and creates a 1-pager for the annual talent review where managers compare reports across teams.
Promotions are lagging. You don't get promoted to start doing L61 work. You get promoted because you've been doing L61 work for long enough that it's obvious. In practice, that means showing above-target performance across at least two Connect cycles before the promotion formalizes what you're already doing.
The hidden rating system. Microsoft assigns a numeric score on a 0-200 scale that employees don't officially see. Roughly: 100-110 is Successful Impact (meeting expectations), 120+ is above expectations, and 60 or below triggers performance concerns. Your compensation is how you know where you landed. Strong rewards mean you're being recognized. Flat rewards are the system telling you something.
The Criteria That Actually Matter for L60 to L61
All three Connect dimensions carry weight, but here's what actually moves the needle:
Results needs to show ownership, not just output. At L60, delivering assigned features is expected. At L61, the bar changes: you identified the right problem, designed the solution, shipped it, and owned it in production. The work you cite in your Connect should show wider scope over time. This comes up repeatedly on Blind: the way to get promoted is to increase the scope of your contributions, because jobs are leveled based on scope requirements.
"The way to get to a higher level is to increase the scope of your contributions. You need to make sure the job you have includes the scope needed for the level you want."
Most engineers underweight Growth. If that section of your Connect is sparse, you lose ground in calibration. Strong Growth evidence looks like: taking ownership of system design for the first time, volunteering to lead incident retrospectives, or applying a new technology to a real problem your team was struggling with.
Then there's Inclusion. This isn't performative. At L61, Microsoft expects you to make the people around you better. Meaningful code reviews, unblocking junior engineers, sharing context across teams. If your Connect only talks about your own output, your manager is building the promotion case with incomplete evidence.
Step-by-Step: Building Your L60 to L61 Case
Step 1: Get clarity on the gap
Ask your manager directly: "What would L61 performance look like in my role?" If they can't answer specifically, ask for examples of what previous L61 promotions on your team looked like. Expectations vary by org. What counts as L61 scope on an Azure infrastructure team differs from a Teams feature team.
Step 2: Pick work that demonstrates L61 scope
Stop accepting every task assigned to you. Gravitate toward work that's ambiguous, cross-functional, or broader than a single feature. You need at least one project in your next Connect cycle where you owned the problem end-to-end: identifying it, designing the solution, shipping it, and measuring what changed.
Step 3: Write Connects that build the promotion narrative
Your Connect document is your promotion case at Microsoft. Treat it like one. For each accomplishment, structure it as: what you did, why it mattered, and how it went beyond L60 expectations. Name the cross-team dependencies you managed. Quantify the impact. Engineers who get promoted at Microsoft write detailed, evidence-rich Connects, not three-bullet summaries.
Step 4: Request Perspectives feedback strategically
You choose who gives you peer feedback at Microsoft. Request feedback from people who've seen your strongest L61-level work, especially cross-team collaborators and senior engineers. Skip-level managers who've observed your impact are powerful voices too. Don't pick the people who will be nice; pick the people who can speak to your scope and independence.
Step 5: Have the promotion conversation with your manager
Don't wait for your manager to raise it. Have an explicit conversation about your timeline: "I want to understand what specifically I need to demonstrate for L61, and whether we're aligned on when it could happen." Since your manager both nominates and approves this promotion, this conversation is the single most important step you can take.
"After your first proper Connect, ask your manager what they need to see from you to move to 61 and work on that."
Common Mistakes That Stall Engineers at L60
Doing more L60 work faster. The most common trap. Shipping twice as many features at the same scope doesn't signal L61 readiness. One project with broader ownership and cross-team impact outweighs five well-executed but narrowly scoped features.
Ignoring Growth and Inclusion in your Connect. Engineers who document only Results give their manager a one-dimensional case. When that case is presented in calibration alongside engineers with evidence across all three dimensions, you lose.
Writing thin Connects. Your Connect is the basis of your promotion argument. Engineers on Team Blind consistently report that taking Connects seriously correlates with promotion outcomes. If you spend 30 minutes on yours, expect 30 minutes worth of advocacy from your manager.
Waiting for the promotion to find you. Microsoft's system is manager-driven. A passive approach is the worst possible strategy here. If your manager doesn't know you want L61 and doesn't have evidence for the case, nobody else will build it.
Switching teams at the wrong time. Transferring teams resets your manager's context. Your previous Connect history loses narrative power with a new manager who hasn't observed your work firsthand. If you're close to promotion, stay and get it first. If you're genuinely stuck because the team lacks L61-scope work, then move, but expect to add 6-12 months to rebuild credibility.
Timeline and Realistic Expectations
| Scenario | Typical Duration | What drives this |
|---|---|---|
| Fast track | 6-12 months at L60 | Hired under-leveled; manager sees L61 scope quickly |
| Standard path | 12-18 months | Above-target performance across 2 Connect cycles; proactive about scope and visibility |
| Slower path | 18-24+ months | Solid performer but not demonstrating L61 scope; missing Growth or Inclusion evidence; manager not actively advocating |
The minimum time at any level before promotion eligibility is 6 months. Engineers who were brought in under-leveled sometimes get promoted in under a year. But the typical path is 12-18 months of demonstrated L61 behavior before the promotion catches up.
If you've been at L60 for two years with positive feedback but no promotion, something structural is off. Either the work doesn't have enough scope, the team has limited promotion slots, or your manager doesn't see what you're seeing. Any of those warrants a direct conversation or a team change.
Frequently Asked Questions
How long does it take to get promoted from L60 to L61 at Microsoft?
Most engineers report 12-18 months at L60 before promotion to L61. The minimum eligibility is 6 months at level. Microsoft's lagging promotion system requires demonstrating L61-level behavior across at least two Connect cycles before the promotion is formalized. Some teams enforce their own minimum tenure of 2+ years per level regardless of performance.
Is L61 the same as Senior Software Engineer at Microsoft?
Titles vary by org. In many engineering teams, L61 carries the title "Senior SDE." In others, the Senior title starts at L62 or L63, with L61 called "SDE II" instead. The level number is what matters internally for compensation, scope expectations, and career progression. Don't get stuck on the title; focus on what the level expects in terms of ownership and impact.
Can switching teams help me get promoted to L61 faster?
Switching teams resets your manager's context and delays your promotion narrative. If your current team has scope for L61 work and your manager is supportive, stay. If the team genuinely doesn't have work at the right level, moving can help. But expect to add 6-12 months to rebuild credibility with a new manager who hasn't seen your track record.
Does my skip-level manager matter for the L60 to L61 promotion?
Your skip-level doesn't formally approve L60 to L61 promotions. Your direct manager does. But skip-levels participate in talent reviews where managers present their teams. If your skip-level knows your name and your work, that strengthens the case your manager is making. If they've never heard of you, it doesn't block you, but it doesn't help either.
CareerClimb tracks your wins, maps them to your company's promotion criteria, and tells you exactly what evidence you're missing. When your next Connect review comes, your case is already built. Download CareerClimb →