The three levels most engineers live in

Microsoft L62 vs L63 vs L64: The Step Into Senior, and What Comes After

These three levels cover the top of Software Engineer II and the whole of the Senior band, which is where the majority of Microsoft engineers sit and where most offers and promotions actually happen. None of them is a Principal Engineer level, despite a widely repeated claim that L63 is one. This guide covers what genuinely changes between them, why the L62 to L63 promotion is the first contested one, and the decision that arrives when you reach L64.

Compare the Three The L62 to L63 Promotion

Last reviewed: August 2026
L62 median: $215k, SDE II
L63 median: $242k, Senior
L64 median: $265k, Senior

First, the correction

What these three levels actually are

L62 is the upper level of the Software Engineer II band. L63 and L64 are both Senior Software Engineer, sharing one title across two levels. None of the three is Principal, which does not begin until L65.

This needs stating because a different mapping circulates widely, one that promotes L63 to Principal and L64 to Senior Principal. It is wrong, and it matters for a practical reason rather than a pedantic one.

The confusion is understandable. Microsoft uses numbers internally and publishes no official map to titles, so there is no authoritative document to check a claim against. The mapping used here follows levels.fyi, which states directly that a Senior Software Engineer at Microsoft is level 63.

The full ladder from L59 to L70 is set out in the Microsoft engineering levels and salary guide. This page stays with the three levels where most engineers actually spend their careers.

Side by side

Side by side comparison

The row worth dwelling on is the last one. The value of each step is not evenly spaced, and the largest number in it belongs to a promotion that is not on this page.

L62, L63, and L64 compared

	L62	L63	L64
Band	SDE II, upper level	Senior SDE, entry level	Senior SDE, experienced level
Public title	Software Engineer II	Senior Software Engineer	Senior Software Engineer
Reported median pay	$215k	$242k	$265k
Typical experience	3 to 5 years	5 to 8 years	7 to 10 plus years
Scope	A component or service	A system across components	An area across systems
Influence stops at	The team boundary	Neighbouring teams	The organisation
Terminal level	No	Yes	Yes
Approval to reach it	Manager	Skip level manager	Skip level manager
Step up is worth	About $27k, and crosses a band	About $23k, inside the band	About $71k, and crosses into Principal

Two of these steps cross a band and one does not. L62 to L63 moves you from SDE II into Senior, which changes your title, your bonus target, and what a future promotion case is measured against. L63 to L64 keeps you in the same band with the same title, and is the smallest step of the three.

The step that is worth the most by a considerable distance is L64 to L65, which leaves this page entirely and crosses into Principal. If you are thinking about these three levels primarily in compensation terms, that is the number that should be shaping your plans.

In depth

Each level in depth

The honest difficulty in describing these levels is that L63 and L64 share a title and a job description. What separates them is consistency and reach rather than a different remit, so the descriptions below focus on where each one's influence stops.

L62

Software Engineer II

3 to 5 years$215k

Top of the SDE II band

The experienced end of mid level, not a senior title.

L62 is the upper level of the SDE II band. The engineer here is fully independent, owns a component or service without supervision, and is trusted to be handed an ambiguous problem and come back with a plan rather than a question.

The word Senior does not appear in the title, and that trips people up because the work often feels senior. An L62 mentors newer engineers, leads a workstream, and is frequently the person who actually knows how a given system behaves in production. What they are not yet doing is shaping direction outside their own team, which is the specific thing L63 tests for.

What they own

A component or service end to end, including its operational health
Design for features within their area, reviewed rather than directed
Onboarding and mentoring engineers at L59 to L61

The next step crosses into the Senior band and is contested.

L63

Senior Software Engineer

5 to 8 years$242k

Entry to the Senior band

The first genuinely senior level, and the first you can stay at forever.

L63 is where Senior begins. The change from L62 is not that the work is harder in isolation but that its consequences extend past the team boundary. An L63 owns a system rather than a component, and is expected to have views on how neighbouring teams should interact with it.

It is also the first terminal level on the ladder, which is why so many engineers arrive here and stay. Microsoft applies no pressure to keep climbing once you reach Senior, and a well regarded L63 can remain one for the rest of their career without anyone raising it as a problem.

What they own

A system spanning several components, including its architecture
Technical direction that other teams have to plan around
Design review authority over work produced by their team

The next step stays inside the Senior band and is worth about $23k.

L64

Senior Software Engineer

7 to 10 plus years$265k

Experienced end of the Senior band

The same title as L63, and the point where a real career decision arrives.

L64 carries the identical title to L63. There is no separate Senior II designation, which is why comparing the two by job description produces such unsatisfying answers. The distinction is depth and consistency rather than a different remit: an L64 has been operating at senior scope long enough that it is reliable rather than occasional.

What makes L64 interesting is not the level itself but where it sits. It is the last rung before Principal, and the step up to L65 is the hardest promotion on the ladder. Reaching L64 forces a decision that L63 lets you defer.

What they own

Technical direction for an area rather than a single system
The difficult, ambiguous problems that have no obvious owner
Mentoring engineers at L62 and L63 toward senior scope

The next step crosses into Principal, needs senior leadership review, and is worth about $71k.

The first contested step

The L62 to L63 promotion

Everything up to L62 is broadly a function of doing your job well for long enough, approved by your own manager. L62 to L63 is the first step where that stops being true. It needs skip level approval, which means someone has to argue for you to a person who does not watch you work.

That single procedural detail explains most of what makes this promotion difficult, and most of the reasons strong engineers stall at it.

Impact that left your team

The clearest single signal. A promotion case built entirely on work inside your own team reads as excellent L62 performance rather than as L63 readiness, however good the work was.

Design authority others deferred to

Not that you wrote a design document, but that another team changed their approach because of it. Named examples with named teams are what a skip level manager can actually argue from.

Problems you took without being assigned them

Senior scope is largely about what you notice. Picking up an ambiguous, unowned problem and driving it to resolution is worth more in a promotion case than delivering a large assigned project well.

A visible record, not a private one

Skip level managers approve these promotions and they do not watch you work. Written designs, review comments, and incident write ups are the evidence they read. Excellent work nobody can point to is a common reason strong candidates stall.

Sustained rather than singular

One strong project is not enough. The case needs a pattern across cycles, which is a large part of why this promotion typically takes two to four years rather than one.

A deliberate design

Why L63 is where most people stop

L63 is the first terminal level on the Microsoft ladder. You can stay there indefinitely without being managed out, and a large number of engineers do exactly that.

This is a real difference from companies that run up or out expectations at senior levels, where remaining at one rung for many years invites a conversation nobody enjoys. Microsoft applies no such pressure once you reach Senior. A well regarded L63 can stay one for the rest of their career and nobody will treat it as a problem to be managed.

Whether that reads as reassuring or as stagnation depends entirely on what you want from the job, and it is worth being honest with yourself about which. The ladder is not built on the assumption that everyone is trying to climb it, which is a materially different environment to work in and one of the more commonly cited reasons engineers stay at Microsoft.

The fork

The L64 decision point

L64 is the last rung before Principal, and reaching it forces a question that L63 lets you defer indefinitely: whether you want the job that comes next.

L64 to L65 is the hardest promotion on the Microsoft ladder. It requires senior leadership review rather than skip level approval, and the standard changes in kind rather than degree. Delivering excellent work reliably is no longer the question. The question is whether an organisation would be measurably worse off without you, which is a far harder thing to evidence and depends partly on circumstances outside your control.

It is also the largest pay step below Partner, adding roughly $71k to reported median compensation. That is more than the L62 to L63 and L63 to L64 steps combined, which is worth knowing if compensation is what is driving the decision.

The part that deserves more thought than it usually gets is that Principal is a different job rather than more of the same one. Hands on building drops substantially and organisational influence becomes the bulk of the work. Plenty of excellent senior engineers actively do not want that, and choosing to remain at L64 is a legitimate answer rather than a failure of ambition.

Using this

Negotiating an offer at these levels

Most Microsoft offers to experienced engineers land at L62, L63, or L64, so this is where the majority of negotiation actually happens. The first lever matters more than the rest combined.

Ask which level, not which title

L63 and L64 share the title Senior Software Engineer, and the reported gap between them is about $23k. An offer described only as Senior tells you nothing. Get the number in writing before discussing anything else.

External offers often land at the lower level of a band

If you are offered L63 and your experience genuinely supports L64, pushing on the level is usually more productive than pushing on the money inside L63. Band and level position set the ceiling for everything else.

The stock is where the flex is

Base salary at these levels sits inside a fairly tight band. The initial stock award carries more discretion, and at L63 and L64 it is a meaningful part of the package.

Count the bonus properly

Microsoft bonus targets rise with level and sit around fifteen per cent at Senior. Companies that push everything into equity will look better on headline total and worse on guaranteed cash, so compare like for like.

Sign on bonuses cover the vesting gap

A sign on is the standard tool for bridging equity you are leaving behind. It is also the component with the most room to move, because it costs one budget cycle rather than an ongoing commitment.

Questions

Frequently asked questions

The questions engineers ask most often about this part of the Microsoft ladder.

Is L63 a Principal Engineer at Microsoft?

No. L63 is a Senior Software Engineer and it is the entry point to the Senior band. Principal begins at L65, two levels higher.

This error is widespread enough that it is worth stating plainly, because any guide repeating it will also quote inflated salary figures. Levels.fyi states directly that a Senior Software Engineer at Microsoft is level 63, with reported median total compensation around $242k rather than the mid three hundreds a Principal level would command.

Is L62 a senior level at Microsoft?

Not formally. L62 is the upper level of the Software Engineer II band, and the Senior title does not begin until L63.

In practice the work at L62 often feels senior, since these engineers own systems independently and mentor others. The distinction Microsoft draws is about where your influence reaches rather than how good you are, and L63 specifically tests for impact beyond your own team.

What is the difference between L63 and L64?

They share the same title, the same band, and broadly the same remit. The difference is depth and consistency rather than a different job, which is why comparing them by responsibilities alone produces vague answers.

An L64 has been operating at senior scope long enough that it is dependable rather than occasional, and typically influences an area rather than a single system. Reported median pay differs by about $23k.

Which is the harder promotion, L62 to L63 or L64 to L65?

L64 to L65, by a wide margin. It crosses from Senior into Principal, requires senior leadership review rather than skip level approval, and adds roughly $71k to reported median pay.

L62 to L63 is the first genuinely contested promotion and the first requiring approval above your own manager, so it is a real step. But the standard at L65 changes in kind rather than degree: the question becomes whether an organisation would be measurably worse off without you.

Can you stay at L63 permanently?

Yes. L63 is a terminal level, meaning you can remain there indefinitely without being managed out. This is a deliberate feature of the Microsoft ladder rather than an oversight.

It is one of the more genuine cultural differences between Microsoft and peers that run up or out expectations at senior levels, and it is a commonly cited reason engineers stay.

Do most Microsoft engineers get past L64?

No. Reaching the Senior band and remaining in it is the normal outcome, and the ladder is built on that assumption rather than treating it as a failure state.

If you are weighing whether to push for Principal, it is worth being honest that the work changes substantially. Principal is much less about building and much more about organisational influence, and plenty of excellent engineers actively do not want that job.

How long does the L62 to L63 promotion take?

Typically two to four years at L62, though it depends far more on the kind of work you have been able to reach than on time served.

The most common reason for stalling is a promotion case built entirely on work inside your own team. That reads as strong L62 performance rather than L63 readiness, no matter how well executed it was.

Can external candidates join Microsoft directly at L63 or L64?

Yes, both are routine for experienced hires. This is quite different from L65 and above, which happens but is much less common.

External offers often land at the lower level of a band, so if you are offered L63 and believe your experience supports L64, that is a reasonable thing to push on. Doing so is usually more valuable than negotiating harder within L63.

Do engineers at L63 and L64 still write code?

Yes, substantially. These are hands on levels and the majority of the work is still building. The change from L62 is how much time goes into design, review, and cross team alignment alongside it.

The significant reduction in hands on work comes at Principal rather than within the Senior band, which is part of why the L64 to L65 decision deserves genuine thought rather than being treated as an obvious yes.

How do L63 and L64 map to Google, Meta, and Amazon?

Roughly, L63 and L64 correspond to Google L5, Meta E5, and Amazon L5 to L6, all of which are the Senior band at their respective companies.

Mappings like this are approximate because scope expectations differ, and pay at equivalent levels is generally somewhat higher at Google and Meta, with the gap concentrated in the stock component.

Does the level number or the title matter more?

The number. L63 and L64 carry identical titles with a real pay difference between them, and titles also vary between organisations at Microsoft.

When you receive an offer, ask for the level number explicitly and get it in writing. It determines your band, your bonus target, and what a future promotion case will be measured against.

Sourcing

Where these figures come from

Microsoft publishes no level to title map and no compensation bands. United States job postings in several states carry legally required base salary ranges, which is the only official figure available and covers base alone.

The mapping and the compensation figures here follow levels.fyi, cross checked against other reporting. The lack of any authoritative document is exactly why the incorrect mapping placing Principal at L63 spreads so easily, so be sceptical of any source that does not say where its level map came from.

Reviewed in August 2026.

More Microsoft guides

Microsoft engineering levels and salary

The full ladder from L59 to L70 with the corrected level map and pay at every level.

Microsoft Principal Engineer levels

L65 through L69, the band that begins one step above L64.

Microsoft software engineer salary

Pay broken out by level and by location.

Distinguished Engineer vs Technical Fellow

The two titles at the very top of the ladder.

Microsoft vs Google vs Meta levels

Where L63 and L64 land against the other two ladders.

Compare against other companies

Google engineer levels

The L3 to L10 ladder, where L5 is the Senior equivalent.

Amazon engineering levels and salary

Where L5 and L6 sit against the Microsoft Senior band.

NVIDIA engineering levels and salary

Pay by engineering discipline and by office worldwide.

Meta engineering levels

The E3 to E9 ladder, where E5 is the Senior equivalent.

Show impact that left your team

The difference between an L62 resume and an L63 resume is not the quality of the work. It is whether the impact described stops at your team boundary. Lead with what changed for people who do not report to the same manager you do.

Build Your Resume See the Full Ladder