How to Get Promoted from L61 to L62 at Microsoft
Building your promotion case?
Get AI coaching on what to document and how to present it.
You've been at L61 for a while now. You own your subsystem, mentor junior engineers, coordinate across teams when projects demand it. Your Connects feedback is positive. But the promotion to L62 hasn't materialized.
This is where many Microsoft engineers hit their first real wall. The L60 to L61 promotion rewarded you for becoming an independent owner. The L61 to L62 promotion, SDE II to Senior SDE, asks something different: stop executing at high scope and start setting the technical direction that determines what gets built. That shift is less obvious than it sounds, and it trips up a lot of strong engineers.
What Changes from L61 to L62 at Microsoft
The gap between L61 and L62 isn't about writing better code or shipping more features. It's about influence.
| Dimension | L61 (SDE II) | L62 (Senior SDE) |
|---|---|---|
| Scope | Owns medium-to-large features or subsystems end-to-end | Owns the technical direction of a system or product area |
| Problem selection | Takes ownership of problems identified by the team | Identifies the right problems to solve before anyone asks |
| Cross-team work | Coordinates across teams when a project requires it | Drives cross-team technical decisions as a recognized go-to person |
| Mentorship | Mentors junior engineers and interns when opportunities arise | Grows engineers around them systematically; raises the quality bar for the whole team |
| Technical influence | Makes and defends design decisions within their area | Designs systems that other engineers build; shapes architecture beyond their immediate team |
| Production ownership | Ensures reliability of features they shipped | Owns production health for broader systems; anticipates failure modes before they surface |
L61 executes with independence and owns outcomes. L62 sets the direction that determines which outcomes matter.
"The main difference between senior levels and junior levels is the degree of self-direction expected. Juniors get well-defined tasks while seniors are given goals to work towards."
How Microsoft Promotions Work at L61 to L62
This promotion is still manager-driven. Your direct manager nominates you and approves it. L62 is the last level where that's true. Starting at L63, your skip-level manager (typically an L67 Group Engineering Manager) has to sign off.
That makes your manager relationship the most critical variable, the same way it was for L60 to L61. But at L62, the evidence bar is higher. Your manager needs to present a case in calibration that shows sustained L62-level scope across multiple review cycles, not just a strong quarter.
The review system is Connects, Microsoft's semi-annual performance review. Twice a year you write a self-assessment organized around three dimensions: Results, Growth, and Inclusion. Your manager combines that with peer feedback from Perspectives, assigns an impact rating on the confidential 0-200 scale, and presents your case in talent calibration alongside other managers' reports.
Promotion to L62 typically requires consistent Successful Impact (SI) or Exceptional Impact (EI) ratings across at least two Connect cycles. Most engineers who get promoted have been performing at L62 scope for over a year before the title catches up.
The Criteria That Actually Matter for L61 to L62
Results needs to show direction-setting, not just delivery. At L61, owning a feature end-to-end and shipping it reliably is the expectation. At L62, your Results section should show that you shaped what got built, not just that you built it well. If you identified a problem nobody else saw and designed the solution the team implemented, that's L62 evidence. If you executed a plan someone else wrote, that's L61 evidence regardless of how well you shipped it.
"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."
Growth is where most L61 engineers leave points on the table. Taking a dependency on a new technology stack, leading your first cross-team design review, volunteering for an on-call rotation you haven't owned before. If your Growth section is two sentences long, you lose ground in calibration to engineers who documented evidence across all three dimensions.
Inclusion at L62 goes beyond answering questions when somebody asks. Microsoft expects you to make the people around you measurably better. Code reviews that teach, not just approve. Knowledge sharing that prevents problems before they happen. Documentation or tooling that makes the whole team faster. If your Connect only talks about your own output, you're presenting an L61 case with L62 formatting.
Step-by-Step: Building Your L61 to L62 Case
Step 1: Get explicit about what L62 means on your team
Ask your manager: "What would L62-level contributions look like for someone in my role?" Expectations vary by org. What counts as L62 scope on an Azure infrastructure team differs from a Teams feature team. Your manager should be able to reference past L62 promotions on your team. If they can't give specifics, that's a signal worth paying attention to.
Step 2: Pick work that shows direction-setting, not just ownership
Stop picking up every task that comes your way. Gravitate toward projects where the problem is ambiguous, the solution isn't obvious, and the impact stretches past your immediate team. You need at least one project in your next Connect cycle where you didn't just own the execution. You identified the opportunity, designed the approach, brought others along, and delivered results that the team couldn't have reached without your direction.
Step 3: Own production health for your area
At L62, production ownership is no longer someone else's job. Volunteer to own livesite health for your subsystem. Set up monitoring, build runbooks, lead incident retrospectives. Engineers who take ownership of reliability and operational health demonstrate the proactive thinking that separates L62 from L61. It also makes you the person others come to when things break, which is L62-level influence in action.
Step 4: Write Connects that tell the L62 story
Your Connect document is your promotion case. Treat it like one. For each accomplishment, show what you did, why it mattered at L62 scope, and how it went beyond what's expected at L61. Name the cross-team dependencies you navigated. Quantify the outcomes. Engineers who get promoted at Microsoft write evidence-rich Connects, not three-bullet summaries dashed off the week before the deadline.
Step 5: Have the promotion conversation early
Don't wait for your manager to bring it up. Be direct: "I want to understand what specifically I need to demonstrate for L62, and whether we're aligned on when that could happen." Since your manager controls both the nomination and the approval at this level, this conversation is the single most important step in the entire process.
Common Mistakes That Stall Engineers at L61
Shipping more features at L61 scope. Delivering three projects that each show L61-level ownership doesn't add up to L62. One project where you set the direction, designed the system, and influenced engineers across teams is worth more than five well-executed features with narrow scope.
Staying inside your team's boundaries. L62 requires cross-team influence. If all your work, code reviews, and Perspectives feedback come from within your immediate team, your manager will struggle to argue that you operate at Senior scope. Find ways to drive technical decisions that touch adjacent teams. Join cross-team design reviews. Offer to own a shared dependency.
Ignoring production health. L62 engineers own their systems in production, not just in development. If you ship features but someone else handles monitoring, on-call, and incident response for your area, you're leaving a significant part of the L62 case unbuilt.
Writing thin Connects and hoping your work speaks for itself. It doesn't. Calibration runs on documents, not reputation. Engineers on Team Blind consistently report that the engineers who get promoted invest real time in their Connect documents. If you spend 30 minutes on yours, expect 30 minutes worth of advocacy from your manager.
Not having the promotion conversation. Microsoft's system is manager-driven. Your manager won't build a case they don't know you want built. If you haven't explicitly discussed L62 with your manager, start there before doing anything else.
Timeline and Realistic Expectations
| Scenario | Typical Duration | What drives this |
|---|---|---|
| Fast track | ~1 year at L61 | Hired under-leveled; manager recognizes L62 scope quickly |
| Standard path | 1.5-2 years | Above-target performance across 2+ Connect cycles; proactive about scope expansion |
| Slower path | 2.5-3+ years | Solid performer but not demonstrating L62-level direction-setting; team has limited promotion budget; missing Growth or Inclusion evidence |
The typical L61 to L62 promotion takes 1-2 years, though engineers on teams with many strong performers and limited promotion slots report waiting longer. Some teams enforce 2+ year minimums per level regardless of individual performance.
If you've been at L61 for over two years with strong feedback but no promotion, something structural needs to change. Either the work available doesn't have L62 scope, the team has too many people competing for too few promotion slots, or your manager isn't actively building the case. Any of those warrants a direct conversation. If the first two can't be fixed, a team change might be the fastest path forward.
Frequently Asked Questions
How long does it take to get promoted from L61 to L62 at Microsoft?
Most engineers report 1-2 years at L61 before promotion to L62. Microsoft's lagging promotion model requires demonstrating L62-level work across at least two Connect cycles before the promotion formalizes what you're already doing. Some teams enforce their own minimum tenure policies, and competitive teams with limited promotion budget may extend the timeline further.
Is L62 a terminal level at Microsoft?
L62 is not officially a terminal level, but many engineers stay there for years or for their entire Microsoft career. The jump from L62 to L63 (Principal SDE) requires skip-level approval and significantly broader scope. Most L63 engineers influence technical direction across entire product areas, not just their team's systems. For engineers who want deep technical work without the organizational complexity of Principal-level visibility, L62 is a well-compensated place to stay. Median total compensation at L62 is roughly $206K.
Does switching teams help get promoted to L62 faster?
Only if your current team genuinely lacks L62-scope work. Switching teams resets your manager's context and weakens the promotion narrative that's been building through your Connect history. A new manager who hasn't observed your work firsthand will need time to build confidence. If you're close to promotion, stay and get it. If the team's work is genuinely capped at L61 scope or the promotion budget is perpetually exhausted, moving is the right call. Expect to add 6-12 months to rebuild credibility.
Does my skip-level manager matter for the L61 to L62 promotion?
Your skip-level doesn't formally approve L61 to L62 promotions. Your direct manager does. But skip-levels participate in talent reviews where managers present their cases. If your skip-level knows your name and has seen your impact firsthand, it strengthens the story your manager tells. L62 is the last level where your skip isn't a required approver, so building that relationship now pays off when you're aiming at L63 later.
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 →