Microsoft logo

Microsoft Interview Questions

Reconstructed from 134 verified candidate reports across 39 questions. Oct 2025 – Oct 2026.

This page is a live view of every Microsoft interview question AceOffer has indexed — pulled from candidate reports, not invented from job descriptions or one founder’s memory. Every question shows how many times it’s been reported and when it was last seen. The catalog gets a refresh pass every month.

AceOffer is not affiliated with, endorsed by, or sponsored by Microsoft. Questions are reconstructed from interview experiences candidates shared, not from Microsoft materials.

134
candidate reports
39
distinct questions
7
round types
Monthly
refresh cadence

Key facts

  • •39 distinct Microsoft interview questions indexed
  • •134 candidate reports across the catalog
  • •Most reported: Behavioral, Hiring Manager and "As Appropriate" Questions — 12× (last seen September 2026)
  • •Round mix across candidate reports: coding 39%, phone screen 15%, system design 12%, ML / research 10%, online assessment 10%, behavioral 9%, technical deep-dive 5%
  • •18 of the 39 questions were last reported in Aug–Oct 2026
  • •Reports span Oct 2025 – Oct 2026
  • •Refreshed monthly · last updated October 2026

Browse Microsoft interviews by topic

The Microsoft loop, from candidate reports

Reported Microsoft software engineering loops vary by team and by route. Hiring events start with a HackerRank online assessment of two problems, such as a balanced permutation check or the cheapest trip when fuel prices differ by city, then four rounds in one morning: three coding rounds and one system design. Team loops start with a phone screen that often spends time on a past project before one coding problem. Onsite coding is mostly LeetCode-style, with Number of Islands and its variants, LRU Cache, a rate limiter and Merge Intervals reported most, plus object-oriented and concurrency problems such as a per-key ordered task executor. MAI and Copilot teams ask more practical multi-part problems: DNA fragment assembly, stop-token detection over a stream of text, beam search decoding and an in-memory table built from CSV. System design rounds most often cover ticket booking, a URL shortener, re-engagement for inactive Copilot users, an online multiplayer game and log storage. Most rounds open with behavioral questions, many loops include a hiring-manager round or a project deep dive, and some 2026 loops add an AI-assisted coding round.

What does Microsoft ask in each interview round?

Microsoft interviews span 7 distinct round types, broken down below. Counts reflect distinct questions per round, not number of times asked. Frequencies on individual question cards show how many candidates reported getting that specific question.

LeetCode-style problems (Number of Islands and its variants, LRU and LFU Cache, Merge Intervals, Lowest Common Ancestor, Spiral Matrix, Alien Dictionary, distance to a cycle) and practical ones (a sliding-window rate limiter, a per-key ordered task executor, an in-memory table from CSV).
17 questions

A coding screen, often after a project discussion: DNA fragment assembly, stop-token detection over a text stream, suffix-maximum counts, top K problems, package install order and Longest Palindromic Subsequence.
6 questions

Two HackerRank problems: a balanced permutation check, the maximum XOR product, counting non-decreasing arrays with given digit sums, the cheapest trip with fuel prices by city, the most frequent substring within limits, and picking k non-adjacent servers.
6 questions

Ticket booking, a URL shortener, re-engagement for inactive Copilot users, an online multiplayer game and log storage, plus many designs drawn from the interviewing team's own work.
5 questions

ML coding (greedy decoding then beam search, k-means from scratch) and applied scientist ML fundamentals such as bagging versus boosting, metrics and regularization.
3 questions

Behavioral questions in most rounds and in hiring-manager rounds: conflict, a hard project, a missed deadline, changing requirements and why Microsoft.
1 question

A project deep dive or resume technical review: detailed questions on a past system, your own decisions and trade-offs, in one report latency layer by layer.
1 question

Which Microsoft interview questions come up most?

These are the Microsoft questions reported most across the loops we’ve indexed, sorted by candidate-report frequency.

The full index is below, or browse the Microsoft catalog →

Every Microsoft interview question we’ve indexed

All 39, grouped by round and sorted by how often candidates reported them. Each links to the question, its reported follow-up count, and when it was last seen.

Coding (17)

Phone Screen (6)

Behavioral (1)

Tech Deep Dive (1)

What passing candidates do
  • •Running your code against your own tests. Several reports say rounds expected a main function or test cases that run, not a dry run, and one new grad loop expected every follow-up written out.
  • •Preparing the concurrency follow-up. LRU Cache and the hash map are followed by multi-threaded access, the rate limiter by 100,000 requests a second, and the per-key executor asks for per-key ordering under a global concurrency limit.
  • •Taking multi-part MAI problems one part at a time. DNA assembly moves from tags with a known direction to an unknown direction and then several chains, and the CSV table from parsing to selecting columns to WHERE filters.
  • •Being ready to code part of your design. Some design rounds end with implementation, such as URL shortener code on HackerRank or the trie behind a typeahead.
Where candidates lose points
  • •Recursive DFS on large grids. On the region-size problem, one interviewer asked what is wrong with DFS; the candidate's answer was stack overflow on large input, fixed with a queue.
  • •Brute force on the OA. Slower solutions timed out on hidden tests, including on the fuel-cost graph problem.
  • •Buffering the whole stream in stop-token detection. One report says text must be returned as chunks arrive, with the stop token possibly split across chunks.
  • •Skimming the CSV rules. In the in-memory table problem, quoted values, commas inside quotes and type casting cost candidates the later parts.

Get the full Microsoft catalog

Every question. Every candidate-reported follow-up. The mistakes that sink people, and what passers do instead. Monthly refresh.

More company interview guides
Prefer to study first? Free reading guides & references — including the AI Training Papers reading guide.

Know someone interviewing at Microsoft?

Send them this guide: 39 questions from 134 candidate reports, with the rounds, the follow-ups and what passers do.

Is this helpful?