How to Get Promoted from L59 to L60 at Microsoft

You just started at Microsoft as an L59. Your offer letter said "Software Engineer," and your first month is a blur of onboarding sessions, codebase walkthroughs, and figuring out how to navigate the internal tooling. Nobody sat you down and explained the leveling system, but you've picked up enough from Blind and hallway conversations to know: L59 is the entry rung, and L60 is where you stop being treated like a new grad.

The L59 to L60 promotion is the easiest level bump at Microsoft. Most engineers who do competent work and have a half-decent manager get it within 12 to 18 months. But "easiest" doesn't mean automatic. Engineers do get stuck here, and the reasons are almost always avoidable. This guide covers what L60 actually means, how your manager decides when you're ready, and the specific moves that separate engineers who advance in under a year from those who spend two years wondering what went wrong.

What Changes from L59 to L60

Both levels sit within the SDE 1 band. Microsoft doesn't draw a hard title distinction between them. But the expectations are real, and your manager is evaluating you against them whether you know it or not.

Dimension	L59 (New Grad)	L60 (Established SDE 1)
Independence	Needs regular guidance; works under direct supervision	Progressing toward self-direction; handles tasks with minimal hand-holding
Scope	Small, well-defined tasks and bug fixes	Broader problems that affect the group's work
Technical depth	Learning the codebase, tools, and engineering patterns	Becoming the person others ask about a specific area
Problem ownership	Executes what's assigned	Takes problems and drives them to resolution without being chased
Proactivity	Does what is asked	Identifies work that needs doing before someone points it out
Code quality	Code works and doesn't break things	Code follows team patterns, gets clean reviews, and earns trust from senior engineers

The gap boils down to one shift: supervised learner to self-directed contributor. You don't need to be fully independent. That's L61. You need to show that you're moving in that direction.

"L59s get promoted to 60 after 9 months to a year and the bar for that is not too high."

— Microsoft engineer, Quora

How Microsoft Decides When You're Ready

Microsoft promotions below L62 are manager-driven. Your direct manager decides when to put you forward. There's no promotion committee, no promo doc that gets reviewed by strangers. Your relationship with your manager matters more than anything else in how quickly you advance.

The review system behind this is Connects, Microsoft's semi-annual performance check-in. Twice a year, roughly in January and July, you write a self-assessment covering three dimensions:

• Results covers what you shipped, built, or delivered that had measurable impact
• Growth covers how you stretched yourself: new technical skills, ownership of unfamiliar problems, initiative outside your comfort zone
• Inclusion covers how you contributed to team health: quality code reviews, unblocking teammates, sharing context

Your manager takes your Connect, combines it with peer feedback from Perspectives (Microsoft's 360 tool), and builds a picture of where you stand relative to level expectations.

For L59 to L60, the bar is straightforward. Your manager needs to see that you've moved past the learning phase and are reliably contributing without constant oversight. In some orgs, L59 and L60 are evaluated together with no functional difference between them. In those teams, the promotion is largely administrative. In others, there's a genuine step up in expectations.

Promotions are lagging. You don't get promoted to start doing L60 work. You get promoted because you've already been doing it. The promotion recognizes what's already happening, not what you promise to do next. In practice, this means showing above-target performance across at least two Connect cycles.

What Actually Gets You Promoted

Stop waiting to be told what to do

The clearest signal that you've outgrown L59 is proactivity. L59 engineers wait for tasks. L60 engineers spot problems and propose solutions. You don't need to redesign the architecture. Start small: notice a flaky test that keeps failing in CI and fix it. Find a gap in the team's documentation and fill it before anyone asks.

What matters isn't the size of the contribution. It's that nobody assigned it to you.

Become the person who knows something deeply

Every team has areas that are under-documented and poorly understood. Pick one. Read the code, understand the history, and become the person teammates come to with questions. This is what Microsoft's internal framework calls "subject matter expertise," and it's one of the clearest markers of L60 readiness.

This doesn't mean learning everything. It means learning one thing well enough that your team depends on your knowledge of it.

Own problems end-to-end

L59 engineers get assigned a task, do the task, and hand it back. L60 engineers take a problem, figure out the approach, do the work, get it reviewed, ship it, and follow up on whether it actually solved the issue. The difference is ownership through the full lifecycle.

When you pick up a bug, don't just fix the immediate symptom. Investigate the root cause. If the fix is bigger than expected, communicate that to your manager with a plan. If you can't fix it alone, bring in the right people and coordinate. This is L60 behavior.

Write Connects that prove the shift

Your Connect document is what your manager uses to advocate for you. If you spend 30 minutes on it, expect 30 minutes worth of advocacy. Write specific, dated, evidence-rich entries.

For each accomplishment, cover three things:

1. What you did
2. Why it mattered to the team or the product
3. How it went beyond "I was told to do this and I did it"

Don't leave Growth and Inclusion empty. Document the time you helped a teammate debug a tricky issue, or your first code review for an intern. These feel small but they add up in calibration.

Have the conversation with your manager

Don't assume your manager knows you want L60, or that they know what it takes. After your first Connect cycle, ask directly: "What would you need to see from me to recommend L60?" If they give a vague answer, push for specifics. "Can you give me an example of what a recent L60 promotion on this team looked like?"

This conversation does two things. First, it gives you a clear target. Second, it tells your manager you're thinking about growth, which matters more than most engineers realize.

Why Some Engineers Get Stuck at L59

The L59 to L60 transition should be simple. When it isn't, the reason is almost always one of these.

The most common: your manager isn't paying attention. Some managers treat L59 to L60 as something that happens automatically "when it's time." If your manager hasn't brought up your development trajectory after your first Connect, initiate the conversation yourself. Waiting for them to notice is the number one reason new grads stall.

Scope is the second culprit. If you're assigned only bug fixes and small tasks, you can't demonstrate L60-level ownership. Talk to your manager about getting work that stretches you. If the team doesn't have it, consider an internal transfer.

Then there's the complaint trap. One pattern that comes up repeatedly in advice threads: bringing problems to your manager without proposed solutions reads as junior behavior. When you flag an issue, include what you think the team should do about it.

Promotion velocity also works against you. The longer you stay at a level, the harder the next promotion becomes. This isn't official policy, but engineers across Microsoft report it consistently. If you've been at L59 for more than 18 months without a clear signal from your manager, something is off. Address it directly.

And if you joined mid-cycle, the math is just slow. Start in February, your first full Connect cycle doesn't close until July. You're not eligible for promotion until you've had at least two Connect data points. There's no shortcut here, only using the time to build the strongest possible case for the next window.

Timeline and What to Expect

Scenario	Typical Duration	What drives this
Fast track	9-12 months	Returning intern or strong new grad; manager sees L60 behavior early; high-scope work available
Standard path	12-18 months	Consistent above-target Connects; proactive about ownership and visibility
Slow path	18-24 months	Solid work but narrow scope; thin Connects; manager not actively engaged in your development

Compensation at L60 shifts modestly. Base typically increases 5–8%, and you'll start receiving annual stock grants (~$9K/year at target). On Levels.fyi, median total comp at L60 is around $178K compared to roughly $156K at L59. The bump matters, but the real value is momentum. L60 puts you on the path toward L61 (SDE II), which is where the title change and more significant comp increase happen.

If you've been at L59 for two years with decent feedback but no promotion, treat it as a signal. Either the team doesn't have L60-scope work, your manager doesn't think you're there yet (and hasn't told you), or there's a structural issue with promotion budget. All three are worth a direct conversation. If that conversation doesn't produce a clear plan, it might be time to look at other teams internally.

Frequently Asked Questions

How long does it take to get promoted from L59 to L60 at Microsoft?

Most engineers make the jump in 12 to 18 months. Strong performers, especially returning interns who already know the codebase, can do it in under a year. The minimum eligibility is 6 months at level. Getting stuck at L59 for more than two years is a red flag worth investigating with your manager.

Is the L59 to L60 promotion automatic?

Not technically, but it's the lowest bar of any promotion at Microsoft. You need above-target Connect ratings and your manager's recommendation. In some orgs, L59 and L60 are treated as the same band with no functional distinction. In others, there's a genuine evaluation. Either way, competent work plus a supportive manager gets it done.

What's the pay difference between L59 and L60 at Microsoft?

Median total compensation jumps from roughly $156K at L59 to $178K at L60, according to Levels.fyi. The base increase is typically 5–8%, and L60 starts receiving meaningful annual stock grants. Location matters too. Seattle-area L60 engineers average around $176K total while Bay Area roles push closer to $200K.

Should I switch teams if I'm stuck at L59?

Only if the problem is the team itself: no projects with real scope, or a manager who isn't investing in your growth. Transferring resets your context with a new manager and can add months to your timeline. If you're going to switch, do it early in your L59 tenure rather than after 18 months of building history your new manager won't see.

---

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 →