The complete ladder
Microsoft Engineering Levels and Salary: L59 to L70, With the Level Map Corrected
A great many Microsoft level guides claim that L63 is a Principal Engineer. It is not. L63 is the entry point to Senior, and Principal does not begin until L65. That single error shifts every title by two bands and inflates the salary figures attached to them, sometimes by more than a hundred thousand dollars. This guide sets out the actual mapping, the reported pay at every level from L59 to L70, and how the promotion and reward system behind them works.
- Last reviewed
- August 2026
- Levels covered
- L59 to L70
- Senior begins at
- L63, not L62
- Principal begins at
- L65, not L63
Start here
The level to title map, corrected
Microsoft uses numbers internally rather than public titles, and it publishes no official map between the two. That gap is why an incorrect version has spread so widely, and why it is worth being precise before looking at any salary figure.
The mapping below follows levels.fyi, which states directly that a Senior Software Engineer at Microsoft is level 63.
| Levels | Title | Typical experience | Scope | Terminal level |
|---|---|---|---|---|
| L59 to L60 | Software Engineer (SDE) | 0 to 3 years | Well scoped features inside one component | No |
| L61 to L62 | Software Engineer II (SDE II) | 2 to 5 years | Independent ownership of a component or service | No |
| L63 to L64 | Senior Software Engineer (Senior SDE) | 5 to 10 years | System ownership and cross team technical direction | Yes |
| L65 to L67 | Principal Software Engineer | 9 to 15 plus years | Technical strategy across an organisation | Yes |
| L68 to L69 | Partner | 15 plus years | Multi organisation strategy, equivalent to General Manager | Yes |
| L70 and above | Distinguished Engineer and Technical Fellow | 20 plus years | Company and industry wide technical direction | Yes |
| Level | What many guides claim | What it actually is |
|---|---|---|
| L61 | Senior Software Engineer | Software Engineer II |
| L62 | Senior Software Engineer II | Software Engineer II |
| L63 | Principal Engineer | Senior Software Engineer |
| L64 | Senior Principal Engineer | Senior Software Engineer |
| L65 | Partner or Distinguished Engineer | Principal Software Engineer |
| L68 to L69 | Not usually listed | Partner |
| L70 | Not usually listed | Distinguished Engineer or Technical Fellow |
The practical cost of the error is not academic. An engineer told that L63 is Principal will walk into a negotiation expecting figures in the mid three hundreds, when the reported median for that level is around $242k. They will also badly misjudge how far they are from Principal, which is two levels and, for most people, several years away.
Structure
Why levels come in pairs
Microsoft levels group into bands, and almost every band contains two or three levels sharing a single title. Understanding this explains most of the confusion around the ladder, including why comparing two adjacent levels by job description alone rarely produces a clear answer.
The number governs, not the title
Two engineers can both be called Software Engineer II and sit at L61 and L62, with a reported pay difference above thirty thousand dollars. Internally the number is what determines your band, your bonus target, and what you are measured against.
Titles vary between organisations
The same level can carry different titles in different parts of Microsoft, which is a large part of why incorrect level maps circulate so widely. Always ask for the number.
The lower level in a band is the entry point
L63 is where you arrive when promoted into Senior. L64 is the experienced end of the same band. Neither is a different job description, which is why comparing them by responsibilities alone tends to produce vague answers.
Bands are where the pay jumps sit
Movement inside a band is worth twenty to thirty thousand dollars. Movement between bands is worth far more, and the step from L64 into L65 adds roughly seventy thousand dollars in reported median compensation.
The three levels spanning the top of SDE II and the whole of Senior are where most Microsoft engineers actually sit. They are covered in depth in the L62 versus L63 versus L64 comparison.
Compensation
Compensation at every level
Reported medians for the United States. Component splits are published directly up to L62; above that they are estimated from known bonus targets, so read the total as the firm number and the breakdown as its likely shape.
The pattern worth noticing is where the money actually jumps, which is not evenly spread across the ladder.
| Level | Title | Base | Stock, annualised | Bonus | Total compensation |
|---|---|---|---|---|---|
| L59 | SDE, entry | $123k | $23k | $3.9k | $151k |
| L60 | SDE | $138k | $24.5k | $8.1k | $170k |
| L61 | SDE II | $148k | $29.3k | $4.6k | $183k |
| L62 | SDE II | $170k | $29.6k | $14.6k | $215k |
| L63 | Senior SDE | About $185k | About $32k | About $25k | $242k |
| L64 | Senior SDE | About $198k | About $40k | About $27k | $265k |
| L65 | Principal SDE | About $225k | About $65k | About $46k | $336k |
| L66 | Principal SDE | About $248k | About $115k | About $58k | $421k |
| L67 | Principal SDE | About $268k | About $155k | About $69k | $492k |
| L68 | Partner | About $300k | About $400k | About $137k | $837k |
| L69 | Partner | About $330k | About $550k | About $160k | $1.04M |
| L70 | Distinguished Engineer | About $345k | About $575k | About $160k | $1.08M |
Movement inside a band is worth twenty to thirty thousand dollars. Movement between bands is worth several times that. The step from L64 into L65, crossing from Senior into Principal, adds roughly seventy thousand dollars, and the step from L67 into L68 into the Partner band adds close to three hundred and fifty thousand.
That shape has a direct career implication. Grinding for the next number inside your current band is worth far less than most people assume, while the band crossings are worth far more. If you are optimising for compensation, the question is not how to get from L63 to L64 but whether you are on a path toward L65 at all.
The bonus is also doing more work here than at most large technology employers. Target percentages rise with level rather than falling away, so cash remains a substantial part of the package even at Principal. Companies that push everything into equity at senior levels will look better on a total comparison and worse on a guaranteed one.
The machinery
How Connects decides your bonus and stock
Microsoft runs a single annual performance process that sets both your bonus and your stock award together. Understanding it matters more than it does at companies where those are negotiated separately, because here one score moves both.
The fiscal year ends on 30 June
Microsoft's compensation cycle follows its fiscal year rather than the calendar. The main Connects discussion and the resulting pay decisions land in the July and August window, which is also when promotions take effect.
A single reward score drives both bonus and stock
Performance produces a reward score, and that score maps to your bonus percentage and your annual stock award together. They are not negotiated separately and they move as one, so a strong year raises both at once.
Connects replaced stack ranking
Microsoft abandoned the forced curve years ago. Reviews now assess results, contribution to the success of others, and use of the work of others, which is a deliberate attempt to reward collaboration rather than penalise it.
Bonus targets rise with level
The target sits around ten per cent at SDE, roughly fifteen per cent at Senior, twenty per cent or more at Principal, and higher again at Partner. This is why the cash share of the package grows rather than shrinks as you climb, which is unusual.
Stock refreshers are the compounding piece
Annual awards vest over several years and stack on top of each other. An engineer four years into a level has several overlapping grants vesting at once, so realised pay runs ahead of what a fresh offer at the same level would show.
The compounding effect of overlapping stock grants is the part most candidates underestimate. An engineer several years into a level has multiple annual awards vesting simultaneously, so what they realise runs meaningfully ahead of what a new hire at that same level would be offered. This is a large part of why internal pay and external offers at the same level can look so different.
Getting up the ladder
Promotion mechanics and approval gates
Promotions become progressively harder to approve as well as harder to earn. The approval authority required is a good proxy for how contested each step actually is.
| Step | Approval needed | Typical time in level | What it turns on |
|---|---|---|---|
| L59 to L60 | Manager | Close to automatic | Effectively a tenure step for anyone performing adequately |
| L60 to L61 | Manager | 1 to 2 years | Demonstrated independence on scoped work |
| L61 to L62 | Manager | 1.5 to 3 years | Owning a component without supervision |
| L62 to L63 | Skip level manager | 2 to 4 years | The first genuinely contested promotion, and the entry to Senior |
| L63 to L64 | Skip level manager | 2 to 5 years, often never | Consistent impact beyond your own team |
| L64 to L65 | Senior leadership review | 3 to 6 years, often never | The hardest step on the ladder, and the entry to Principal |
| L65 and above | Partner or executive approval | Highly variable | Organisation wide influence with named, attributable impact |
The first three steps are largely a function of doing your job competently for long enough. L62 to L63 is where that stops being true, because it is the first step requiring approval above your own manager and the first where someone has to argue for you against other candidates.
L64 to L65 is the hardest step on the ladder by a wide margin. It requires senior leadership review, and the standard changes in kind rather than degree: the question is no longer whether you deliver well but whether an organisation would be measurably worse off without you. Many strong engineers never clear it, and that is the expected outcome rather than a failure.
A real difference
Terminal levels and what they mean
A terminal level is one you can remain at indefinitely without being managed out. Microsoft has several, and this is one of the more genuine cultural differences between it and its peers.
L63 to L64
Senior Software Engineer (Senior SDE)
System ownership and cross team technical direction
L65 to L67
Principal Software Engineer
Technical strategy across an organisation
L68 to L69
Partner
Multi organisation strategy, equivalent to General Manager
L70 and above
Distinguished Engineer and Technical Fellow
Company and industry wide technical direction
Senior at L63 is the one that matters most, because it is the first terminal level and the one the largest number of engineers reach. An engineer who arrives there and performs well can stay for the rest of their career without pressure to keep climbing.
Whether that reads as reassuring or as stagnation is a fair question, and the answer depends entirely on what you want. It does mean the ladder is not built on the assumption that everyone is trying to get to the top of it, which is a materially different environment from an up or out culture.
Questions
Frequently asked questions
The questions that come up most often about the Microsoft ladder, starting with the one this page exists to settle.
Is L63 a Principal Engineer at Microsoft?
No. L63 is a Senior Software Engineer, and it is the entry point to the Senior band rather than the top of it. Principal begins at L65.
This is the single most common error about the Microsoft ladder and it circulates widely enough that plenty of otherwise reasonable guides repeat it. Levels.fyi states directly that a Senior Software Engineer at Microsoft is level 63. If a source tells you L63 is Principal, its salary figures will also be inflated, because it is quoting Principal money against a Senior level.
What level is a Senior Software Engineer at Microsoft?
L63 and L64. L63 is where you land on promotion into the band and L64 is the experienced end of it.
Reported median total compensation is roughly $242k at L63 and $265k at L64.
What is the highest engineering level at Microsoft?
L70 and above, carrying the title Distinguished Engineer or Technical Fellow, with reported median compensation around $1.08M. Below that sit Partner at L68 and L69, and Principal across L65 to L67.
These are genuinely rare. Technical Fellow in particular is a handful of people across a company of well over two hundred thousand.
Which Microsoft promotion is the hardest?
L64 to L65, the step from Senior into Principal. It requires senior leadership review rather than a skip level manager, and it is the point where the question changes from whether you deliver well to whether an organisation would be measurably worse off without you.
It is also the largest single pay step below Partner, adding roughly seventy thousand dollars to reported median compensation. Many engineers reach L64 and stop there permanently, which is an accepted outcome rather than a failure.
What does it mean that L63 is a terminal level?
You can stay there indefinitely without being managed out. Microsoft does not require continued progression once you reach Senior, so an engineer who performs well at L63 can remain there for the rest of their career.
This is a genuine cultural difference from companies that operate an up or out expectation at senior levels. It is one of the more commonly cited reasons engineers stay at Microsoft.
How does Microsoft decide bonuses and stock awards?
Through the Connects review process, which produces a reward score that maps to both your bonus percentage and your annual stock award. They move together rather than being set separately.
The cycle follows the fiscal year ending 30 June, so decisions land in July and August. Microsoft replaced its old stack ranking system some years ago, and reviews now explicitly assess how you contributed to the success of others alongside your own results.
Why does the bonus grow as a share of pay at Microsoft?
Because target bonus percentages rise with level, from around ten per cent at SDE to twenty per cent or more at Principal and higher at Partner.
This runs opposite to companies like NVIDIA, where the bonus effectively disappears above the mid levels and everything moves into equity. If you are comparing a Microsoft offer against one of those, comparing base plus bonus alone will mislead you in both directions.
Can external candidates be hired directly into senior Microsoft levels?
L63 and L64 external hires are routine. L65 and above happen but are much less common and generally require demonstrable Principal equivalent scope at a comparable company.
External hires 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 and fairly common thing to push on.
Is Microsoft pay lower than Google or Meta?
At the mid levels, yes, modestly. Microsoft has historically paid somewhat below Google and Meta at equivalent scope, with the gap most visible in the stock component.
The picture narrows higher up and the comparison is genuinely complicated by other factors: Microsoft levels are terminal, the review system is less punitive, and the stock has been less volatile than several peers. Whether that trade is worth it is a personal judgement rather than a numerical one.
Does the level number or the title matter more?
The number, without much competition. Titles vary between organisations at Microsoft, and the same title can appear at two different levels with a meaningful pay difference between them.
When you receive an offer or discuss a promotion, ask for the level number explicitly and get it in writing. Everything downstream, including your band, bonus target, and promotion expectations, follows from it.
How long does it take to reach Principal at Microsoft?
For engineers who get there at all, typically nine to fifteen years, though the range is wide and the path is not primarily a function of time.
The more useful framing is that most engineers do not get there. Reaching L63 or L64 and remaining is the normal outcome, and the ladder is deliberately built to make that a sustainable place to be.
Does Microsoft publish its levels or salary bands?
No. Microsoft publishes no official 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.
Everything else on this page is crowdsourced reporting, primarily levels.fyi. That is also why incorrect level maps spread so easily: there is no authoritative document to check them 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 data available and covers base alone.
The mapping and the total compensation figures here follow levels.fyi, cross checked against other reporting. Component splits are published directly up to L62 and estimated above it from known bonus targets. The absence of any authoritative document is precisely why incorrect level maps circulate so freely, so treat any source that does not say where its mapping came from with caution.
Reviewed in August 2026.
More Microsoft guides
L62 vs L63 vs L64 compared
The SDE II to Senior transition in depth, which is where the majority of Microsoft engineers sit.
Microsoft Principal Engineer levels
L65 through L69, the band that begins where most engineers stop.
Microsoft software engineer salary
Pay broken out by level and by location.
Distinguished Engineer vs Technical Fellow
The two titles at the very top and how they differ.
Microsoft vs Google vs Meta levels
Side by side mapping across three large ladders.
Compare against other companies
Google engineer levels
The L3 to L10 ladder with compensation for sixteen offices worldwide.
Amazon engineering levels and salary
Year by year pay and the back loaded vesting schedule behind it.
NVIDIA engineering levels and salary
Pay by engineering discipline and by office worldwide.
Meta engineering levels
The E3 to E9 ladder and what each rung requires.
Apple software engineer levels
The ICT ladder and where it lines up.
Write your resume for the level number
Microsoft levels are separated by scope rather than by skill. The difference between an L62 resume and an L64 resume is whether the impact described stops at your own team, so lead with the breadth of what your work changed.
