Microsoft uses numeric levels, not titles, internally, and publishes no official map. This page lays out the commonly reported SDE ladder with levels.fyi pay (accessed June 2026), the scope each band signals, and the resume language that matches it.
The quick answer
Microsoft uses numeric levels for engineers rather than public titles. The software engineer ladder is commonly reported as SDE (L59 to L60), SDE II (L61 to L62), Senior SDE (L63 to L64), Principal (L65 to L67), Partner (L68 to L69), and Distinguished Engineer or Technical Fellow (L70 and above). Microsoft does not publish an official level-to-title or level-to-pay map, so these come from levels.fyi and community reports accessed in June 2026, not official Microsoft figures. Commonly reported total compensation runs from around $163K at entry-level L59 to about $281K for a Senior SDE, roughly $339K to $611K across Principal, and around $1.08M at the Distinguished Engineer tier. L63 Senior is a recognized terminal level where engineers can stay indefinitely, and the step that changes a resume most is Senior to Principal. Scan your resume to see whether its scope language matches the level you are targeting. Scan your Microsoft resume.
Microsoft uses numeric levels for engineers rather than public titles, and it does not publish an official level-to-title or level-to-pay map. The ladder below, SDE (L59 to L60) through Distinguished Engineer or Technical Fellow (L70 and above), is commonly reported by the community: levels.fyi crowdsourced compensation uploads plus community reports. Every comp figure on this page is levels.fyi crowdsourced data accessed June 2026, not an official Microsoft number.
The structural reason this matters: because Microsoft surfaces no level on its job postings, candidates who do not cross-reference levels.fyi consistently misjudge the band they are targeting and either underpitch the resume or aim a band too high. Treat every number here as a commonly reported, community-sourced estimate, not a band midpoint.
The defensible public scope is L59 to L70 and above, which covers essentially every realistic applicant. L63 (Senior SDE) is a recognized terminal level where engineers can stay indefinitely, and the step that changes a resume most is Senior to Principal.
Public comp data thins out above L67: at Partner (L68 to L69) and beyond, few people report figures, so any single number should be read as a wide, uncertain bracket. For any anchor number on a resume or in a negotiation, cite levels.fyi by name and date the data as June 2026.
For each band, the audit covers the commonly reported title, scope of ownership, and the resume signal the level expects, with levels.fyi-anchored compensation folded into each signal. Titles and bands are community-sourced, not official Microsoft figures. All compensation is levels.fyi crowdsourced data accessed June 2026. For the wider hiring picture, start with the Microsoft resume guide.
0 to 2 years. Owns well-scoped tasks and features under guidance. The standard new-grad entry point.
Lead with clean problem-solving and measurable results from internships or projects. levels.fyi total comp commonly reported ~$163K (L59) to ~$182K (L60), accessed June 2026, not official Microsoft numbers.
~2 to 5 years. Owns features and small systems with limited guidance. The first fully independent IC band.
Show ownership of a component plus one quantified outcome. levels.fyi ~$197K (L61) to ~$214K (L62) total comp, accessed June 2026.
~5 to 10 years. Owns systems and drives cross-team work. L63 is a recognized terminal level: you can stay indefinitely.
Pair domain depth with cross-team drive and a number. levels.fyi ~$233K (L63) to ~$281K (L64) total comp, accessed June 2026.
Late-IC. Sets technical direction across teams and owns ambiguous, org-level problems. The Senior-to-Principal jump is the steep one.
Lead with scope and ambiguity: an initiative you defined, multi-team impact, a measurable bet. levels.fyi ~$339K to ~$611K total comp across the band, accessed June 2026.
Rare and nomination-based. Company-level technical or organizational leadership.
Company-scale impact only. Public comp is sparse at this tier; treat any figure as a wide, uncertain bracket rather than a band midpoint.
Top of the track. Company-wide technical authority.
The systems, standards, or products you are known for. levels.fyi shows the top of the track around ~$1.08M total comp, accessed June 2026; treat as indicative, not a band midpoint.
RSUs vest over four years, 25 percent per year with a one-year cliff. From L65 up, annual stock refreshes tied to performance reviews increasingly dominate total compensation. Bay Area and New York roles typically run 15 to 25 percent above national averages. Titles like Partner and Distinguished Engineer are nomination-based and rare, and public comp data thins out above L67.
Place yourself by the scope you actually own, not tenure: SDE (L59 to L60) owns well-scoped tasks, SDE II (L61 to L62) owns features and small systems, Senior SDE (L63 to L64) owns systems and cross-team work, and Principal (L65 to L67) sets direction across teams.
Execution for SDE and SDE II, owned systems and cross-team drive for Senior, and org-level scope for Principal. A resume written one band too low reads as the lower level before a human compares it to the ladder.
Attach a numeral and a denominator to every claim: the component you owned, the system you ran, the teams a platform served, or the measurable bet you made. Cross-reference levels.fyi comp for your target band, accessed June 2026.
Upload to ResumeAdapter to see your ATS score against the Microsoft job description, the scope language missing for your target level, and a rewrite plan that quantifies the band you are pitching.
FAQ
The questions most candidates surface when they cross-reference their experience against Microsoft's numeric ladder. Answers are byte-identical to the FAQPage JSON-LD, because AI engines that extract HTML and AI engines that extract JSON-LD should not see different text.
Microsoft's software engineer ladder is commonly reported as SDE (L59 to L60), SDE II (L61 to L62), Senior SDE (L63 to L64), Principal SDE (L65 to L67), Partner (L68 to L69), and Distinguished Engineer or Technical Fellow (L70 and above). Microsoft does not publish an official level-to-title map, so these mappings come from levels.fyi and community reports, accessed June 2026.
L62 is the upper end of the SDE II band, a mid-level software engineer with roughly three to five years of experience who owns features and small systems with limited guidance. levels.fyi commonly reports total compensation around $214K at L62, though Microsoft does not publish official figures and actual pay varies by location and team.
L69 is a Partner-level role, an extremely senior, nomination-based band above Principal and below the Distinguished Engineer or Technical Fellow tier. Public compensation data at L68 and L69 is sparse because few people report it, so treat any specific number as a wide, uncertain bracket rather than a reliable band.
Senior SDE covers L63 and L64, typically five to ten years of experience, owning systems and driving cross-team work. L63 is a recognized terminal level, meaning engineers can stay there indefinitely without being managed out. levels.fyi commonly reports total compensation around $233K at L63 and $281K at L64, accessed June 2026 and not official Microsoft numbers.
Commonly reported total compensation on levels.fyi, accessed June 2026, ranges from around $163K for an entry-level SDE (L59) to around $281K for a Senior SDE (L64), about $339K to $611K across Principal (L65 to L67), and roughly $1.08M at the Distinguished Engineer tier (L70). These are crowdsourced figures, not official Microsoft numbers, and Bay Area and New York roles typically run 15 to 25 percent higher.
Yes. L63 Senior SDE is commonly described as a terminal level, where an engineer can remain indefinitely without an up-or-out requirement. Moving beyond it to Principal (L65) is a significant step that requires demonstrating broad, cross-organizational impact, which is why the resume signal shifts from execution to scope at that point.
The pillar covers how Microsoft hiring works end to end: what recruiters screen for, how leveling is decided, and the level summary. Start here if you have not already.
The cultural attributes Microsoft screens for, what each one means in practice, and how to evidence them on a resume without resorting to values statements.
The stages from recruiter screen through the loop, what each round assesses, and how leveling and calibration get decided after the interviews.
A worked software engineer resume with scope quantified at each bullet, the format that survives an ATS, and annotations on what moved the score.
For the data behind the median pre-edit score, see the ATS statistics. To compare hiring playbooks across employers, browse the full company library.
Get your ATS score against the Microsoft job description, the scope language missing for the level you are targeting, and a rewrite plan that quantifies the band you are pitching. Free to scan; no signup to see the score.
