Microsoft Interview Process 2026: Rounds, Timeline, Salary Bands, and How to Prepare

Step 1: Application and recruiter screen

Applications go in either directly through Microsoft's careers site, via a university pipeline, or through a recruiter reaching out on LinkedIn after seeing your profile. Referrals still meaningfully improve your odds of getting a recruiter call, especially for experienced-hire roles where there's no structured campus pipeline.

The recruiter screen itself is short — usually 20-30 minutes — and is not a technical interview. The recruiter is confirming:

Your current role, notice period, and visa or work-authorization status
Your compensation expectations and location flexibility
Basic alignment with the team's mission (the recruiter will often name the org — Azure, Windows, M365, Xbox, Security, AI — and ask what draws you to it)
Whether you're interviewing elsewhere and on what timeline

Treat this call as a two-way filter, not a formality. Recruiters at Microsoft often manage dozens of open reqs, and being specific about the team or product area you want (and why) makes it easier for them to route you to the right hiring manager rather than a generic queue.

Step 2: The online assessment (OA)

For new-grad, intern, and many standard SWE/SDE roles, Microsoft uses an online assessment delivered through Codility. It's typically a 90-minute session with two coding problems — usually one medium and one medium-to-hard, in the same difficulty range as LeetCode Medium problems on arrays, strings, trees, graphs, and dynamic programming.

A few practical notes on the OA:

You get an email with a link and a deadline, usually 5-7 days out — don't let it sit in your inbox unopened.
The environment supports multiple languages (C++, C#, Java, Python, JavaScript, and others); pick whichever you're fastest and most accurate in, not whatever Microsoft's stack happens to use internally.
Partial credit exists for passing a subset of test cases, so don't abandon a problem just because you can't get a fully optimal solution — submit a working brute force and iterate if time allows.
Experienced hires (typically SDE II and above) are frequently routed straight to a phone screen without an OA, since a live coding round with an engineer serves the same filtering purpose.

Step 3: The phone or video technical screen

This is a 45-60 minute call, almost always on Microsoft Teams, with one engineer from the hiring team (sometimes the hiring manager). Expect one to two coding problems in a shared code editor, plus a handful of behavioral questions woven in at the start or end.

The bar here isn't just "did you get the right answer." Interviewers are scoring:

Problem-solving approach — do you clarify constraints and edge cases before writing code, or dive straight in?
Communication while coding — Microsoft interviewers consistently note that narrating your thinking matters as much as the final solution, because the write-up they submit afterward has to justify a hire/no-hire recommendation to people who weren't on the call.
Code correctness and complexity — can you state the time and space complexity of what you wrote, and do you catch your own bugs when asked to trace through an example?

If you clear this stage, the recruiter will schedule the onsite loop, typically one to three weeks out.

Step 4: The onsite loop

The loop is almost entirely virtual now — even local candidates rarely go to a Microsoft campus for it — and consists of four to five interviews scheduled back-to-back in a single day (with breaks), each 45-60 minutes. For a standard Software Engineer or SDE II loop, you can expect a mix like:

Two coding/DSA rounds — data structures and algorithms, similar difficulty to the phone screen but sometimes with a second, harder follow-up problem if time allows.
One low-level design (LLD) round — for many SWE loops, this shows up as an object-oriented design problem (design a parking lot, an elevator system, a rate limiter) where you're expected to produce clean classes, interfaces, and extensibility, not just a working script.
One system design round — standard for Senior SWE and above, and increasingly present even in some SDE II loops for teams building distributed or large-scale services (design a URL shortener, a notification system, a chat backend).
One behavioral/"culture fit" round — heavy on Microsoft's internal leadership principles, which show up repeatedly across interviewer feedback: growth mindset, customer obsession, diversity and inclusion, and "one Microsoft" (collaborating across team boundaries rather than optimizing locally).

Every one of these interviewers submits an independent written scorecard immediately after your session — before seeing what anyone else scored you. That independence is deliberate: Microsoft wants the AA interviewer to weigh five honest, uncorrelated opinions rather than a groupthink consensus.

The behavioral rounds matter more than people expect

Microsoft's culture questions are not a rubber-stamp formality bolted onto the technical loop — they carry real weight, and "growth mindset" specifically comes up in interviewer training. Expect prompts like "tell me about a time you got critical feedback and what you did with it," "describe a time you disagreed with your manager," or "walk me through a project that failed and what you'd do differently." Structuring these answers clearly (situation, task, action, result) is one of the highest-leverage things you can do to prepare, since unstructured behavioral answers are the single most common reason otherwise-strong technical candidates get "lukewarm" written feedback. ClavePrep's STAR Builder is built specifically to help you turn a messy work story into a tight, interview-ready STAR answer before you're on the call.

The "As Appropriate" (AA) round

The AA round is the last interview of the day, and it's the one candidates most often misunderstand. The name comes from Microsoft's own internal hiring vocabulary — "as appropriate," abbreviated "as-app" in speech and "AA" in writing — for a role that dates back decades. Historically, the AA interviewer's job was literally to review the other interviewers' feedback and decide whether it was "appropriate" to continue the loop at all; if the early rounds went badly, the candidate would sometimes be sent home before ever reaching the AA slot. Microsoft's own engineering blog has documented this history and how the role evolved into a mandatory final interview that every candidate now receives, even though the "AA" label itself is no longer official terminology and mostly survives as inside-baseball shorthand among longtime employees (Microsoft Developer Blogs: "Microspeak: The As-Appropriate (AA) interviewer").

In practice, in 2026 the AA is usually conducted by a director-level manager or a senior engineering leader who is not on your immediate team but has visibility into the broader org. Two things distinguish it from the earlier rounds:

They've read every other interviewer's written feedback before you walk in. If two interviewers flagged a specific weak spot — say, hesitant system design tradeoffs, or a behavioral answer that felt rehearsed and shallow — expect the AA to probe exactly that gap rather than start from scratch.
They have real veto power. A candidate with four strong "hire" scores can still be turned down at the AA stage, and a candidate with one weaker score can still get an offer if the AA interview reassures the panel. This is genuinely the decision point, not a formality, so don't coast into it assuming the loop already decided the outcome.

Prepare for the AA by assuming it will be a mix of: probing follow-ups on whatever felt thinnest in your earlier rounds, higher-altitude questions about how you think about tradeoffs and impact (not just "did you solve the LeetCode problem" but "why did you choose that architecture and what would you change at 10x scale"), and genuine culture-fit conversation about how you handle ambiguity, conflict, and feedback.

Timeline: how long does the whole process take?

Microsoft doesn't publish a single official timeline, and candidate experiences genuinely vary — some hear back the next day, others wait weeks between stages. That said, a reasonably typical path looks like this:

Recruiter screen: within 1-2 weeks of applying or being contacted
OA (if applicable): sent immediately after the recruiter screen, with a 5-7 day window to complete it
Phone/technical screen: scheduled 1-2 weeks after the OA or recruiter screen
Onsite loop: scheduled 1-3 weeks after the phone screen clears
AA round and final decision: often bundled into the same loop day, with a decision communicated within 5-10 business days
Offer and negotiation: 1-2 weeks after the final decision, depending on approvals and level calibration

End to end, budget roughly four to eight weeks from first recruiter contact to a written offer for a standard process, and closer to two to three weeks if you move through everything quickly with no scheduling gaps. Senior and staff-level loops, or roles requiring additional approvals (security clearance-adjacent teams, or roles that need cross-org sign-off), can run longer. If you're mid-process and it's gone quiet for more than two weeks, a polite check-in with your recruiter is normal and expected — it usually means internal scheduling or calibration, not rejection.

Salary bands for 2026

Microsoft's engineering ladder uses level numbers rather than public titles internally (roughly SDE/L59-60 for entry-level, SDE II/L62-63 for mid-level, Senior SWE/L63-64 and up for senior, with Principal and Partner levels above that). Compensation is a mix of base salary, an annual cash bonus, and RSUs that vest over four years — commonly front-loaded less evenly than Amazon's schedule, but still with a one-year cliff before quarterly vesting kicks in.

Based on current aggregated compensation data from Levels.fyi, rough US total-compensation bands for 2026 look like this:

SDE / entry-level (L59-61): roughly $140,000-$190,000 total comp
SDE II / mid-level (L62-63): roughly $160,000-$205,000+ total comp, with a reported median total comp around $184,000
Senior SWE (L63-64) and above: total comp climbs well past $250,000-$300,000+ once senior-level bonus multipliers and larger RSU grants are factored in, and can extend into the high six figures at principal and partner levels

These figures move by location — Seattle/Redmond, the Bay Area, and New York generally sit at the higher end of the band, while other US metro offices trend lower — and by team, since some product groups (particularly AI-focused orgs) have been offering more aggressive packages to compete for talent.

Outside the US, Microsoft's India engineering hubs (Hyderabad, Bengaluru, Noida) run on a separate, India-market-calibrated band — commonly cited experienced-hire ranges land roughly in the ₹25-45 LPA range for SDE II-equivalent roles and materially higher for senior and principal levels, with RSUs still a meaningful part of the package for more senior bands. Remote and international candidates interviewing for globally distributed teams should ask the recruiter directly, early, which pay geography and level a given req maps to — this varies by country and by whether the role is scoped as a local hire or a globally mobile one, and it's a completely normal question to ask during the recruiter screen rather than waiting until an offer is on the table.

A week-by-week preparation plan

If you have a Microsoft loop coming up and roughly four weeks to prepare, here's a realistic split of your time.

Week 1 — Foundations and gap assessment. Do a timed mock of 4-6 medium LeetCode problems across arrays, strings, trees, and graphs to see where you're actually rusty, not where you assume you are. Refresh core data structures (hash maps, heaps, tries, union-find) and make sure you can state Big-O for anything you write without pausing. If it's been a while since your last interview loop, this week is also the right time to map out 3-4 real work stories you can draw behavioral answers from — projects with a clear conflict, ambiguity, or failure-and-recovery arc.

Week 2 — Coding depth and low-level design. Shift toward harder DSA problems (medium-to-hard, some hard) and start practicing object-oriented / low-level design problems out loud: design a parking garage, a vending machine, a ride-sharing dispatch system. Microsoft's LLD rounds reward clean class boundaries and extensibility over cleverness, so practice narrating your design decisions, not just producing a diagram.

Week 3 — System design and behavioral structuring. If you're at SDE II or above, spend real time on system design fundamentals — load balancing, caching, database sharding, message queues, consistency tradeoffs — and practice 2-3 full system design walkthroughs end to end, including the "how would this scale 10x" follow-up questions that Microsoft's senior interviewers and the AA round both like to ask. In parallel, tighten your behavioral stories into STAR format so they're crisp under time pressure; ClavePrep's STAR Builder is designed exactly for turning a rough story into a structured answer you can deliver naturally rather than reciting from memory.

Week 4 — Full mock loops and recovery practice. Run at least two full mock interview loops back-to-back to simulate the fatigue of a real onsite day — this is where candidates who prepared well on paper often stumble, because round four of five is a very different mental state than round one. Practice recovering gracefully from a stuck moment (asking clarifying questions, thinking aloud, trying a brute-force fallback) since interviewers consistently rate composure under difficulty higher than a silent, correct-on-the-first-try answer. If you want structured, on-demand mock practice with realistic follow-up questions rather than static problem lists, ClavePrep's interview prep tools are built around exactly this kind of rehearsal — see how it works for a walkthrough of the practice flow.

Common mistakes candidates make

Treating the recruiter screen as a formality and being vague about the team or role. Recruiters route you faster and more favorably when you can name specifically why you want the team, not just "I love Microsoft's mission."

Skipping OA edge cases under time pressure. Candidates lose points on the Codility OA not because they can't solve the core problem, but because they run out of time to handle empty inputs, negative numbers, or duplicate values — budget the last few minutes of each problem specifically for edge-case review.

Under-preparing for low-level design. Many candidates over-index on LeetCode-style DSA and system design, and walk into the LLD round without having practiced translating a vague prompt ("design a parking lot") into concrete classes and interfaces. It's a distinct skill from both coding and high-level system design, and it shows up in a large share of SWE loops.

Treating behavioral rounds as low-stakes small talk. Given how much weight growth-mindset and culture questions carry in Microsoft's internal interviewer guidance, a rambling, unstructured answer to "tell me about a conflict with a teammate" can quietly sink an otherwise strong loop.

Assuming a strong loop guarantees the offer, and coasting into the AA round. As covered above, the AA interviewer has real veto authority and reads every prior scorecard before your conversation starts — walking in without having thought about what might have been your weakest round is a common and avoidable mistake.

Not asking about level and location pay bands early. Especially for remote, international, or India-hub candidates, waiting until the offer stage to discuss compensation geography wastes negotiating leverage that's easier to establish earlier in the process.

Ignoring layoff-related uncertainty in the org you're joining. Microsoft has gone through multiple rounds of restructuring and layoffs in the last two years, and it's fair — and increasingly common — to ask a recruiter or hiring manager directly about team stability and headcount plans for the org you'd be joining. If you're navigating a Microsoft-related layoff yourself right now, ClavePrep's Microsoft layoffs 2026 career transition guide walks through severance, timing, and how to relaunch a search.

How ClavePrep can help

Most of the mistakes above come down to the same root cause: rehearsing content instead of rehearsing the actual interview experience — the follow-up questions, the time pressure, the moment where you get stuck and have to recover out loud. ClavePrep's AI-powered interview prep tools are built to simulate that experience for Microsoft-style coding, system design, and behavioral rounds, with realistic follow-ups rather than static answer keys. If you're specifically working on behavioral rounds — including the AA — the STAR Builder helps convert your real work history into structured, interview-ready stories, and how it works explains the full practice flow if you want to see it before diving in.

If you're comparing offers or preparing for another Big Tech loop at the same time, it's worth reading our companion guide to the Adobe interview process for 2026, since a lot of the same behavioral and design-round strategies transfer directly.

Frequently asked questions

Is the Microsoft interview process the same for new grads and experienced hires?

No. New grads and university hires almost always go through the online assessment (OA) as a first technical filter, while experienced hires — especially at SDE II and above — are frequently routed straight to a phone screen with an engineer, skipping the OA entirely. Experienced loops also lean more heavily on system design and architecture rounds relative to pure algorithmic coding.

What is the Microsoft "AA" round, and do all candidates go through it?

AA stands for "As Appropriate," a longstanding internal Microsoft term for the final interview in the loop. Historically it was conditional — only candidates with strong early feedback would reach it — but it has since become a standard, mandatory final round for essentially all candidates, typically conducted by a director-level or senior leader who reviews every prior interviewer's written feedback before talking to you. Microsoft's own engineering blog has documented the term's history in detail.

How long does the Microsoft interview process take in 2026?

Budget roughly four to eight weeks from your first recruiter conversation to a written offer for a standard process, though timelines vary a lot by team, level, and how quickly internal scheduling and calibration happen. Some candidates move through in two to three weeks; others see multi-week gaps between stages that are normal rather than a red flag.

What coding languages can I use in the Microsoft OA and interviews?

The Codility-based online assessment and the live coding rounds both generally support a wide range of languages — C++, C#, Java, Python, JavaScript, and others. Use whichever language you can write correct, bug-free code in fastest; interviewers are scoring your problem-solving and code quality, not your familiarity with Microsoft's internal stack.

What's a realistic Microsoft SDE II salary in the US in 2026?

Aggregated compensation data puts SDE II total compensation roughly in the $160,000-$205,000+ range depending on location and team, with a reported median around $184,000 including base, bonus, and RSUs. Senior and above levels climb well past that once larger equity grants and bonus multipliers apply.

Does Microsoft pay differently for remote or international candidates?

Yes. Pay is generally calibrated to a specific geography — the country or metro area tied to the role — rather than a single global band. India-hub roles (Hyderabad, Bengaluru, Noida) run on a separate, locally calibrated compensation structure, and fully remote roles are usually still mapped to a specific pay geography rather than paid on a flat global scale. Ask your recruiter directly and early which geography your offer will be benchmarked against.

Do I need to solve every OA problem perfectly to advance?

No. Partial credit exists on the Codility OA, and passing most test cases on both problems is often enough to advance, especially combined with clean, readable code and correct handling of the obvious edge cases. A rushed, buggy "complete" solution frequently scores worse than a clearly reasoned partial one.

What should I do if the process goes quiet for a few weeks?

A gap of one to two weeks between stages is common and not itself a bad sign — Microsoft doesn't run on a single standardized internal clock, and scheduling across interviewers, especially for the AA round with a senior leader, can take time. A polite, low-pressure check-in with your recruiter after roughly two weeks of silence is appropriate and won't hurt your candidacy.

The Microsoft interview process 2026: how it works