← Back to Directory

Microsoft interview notes, page 16 of 60

FAANG / Big Tech

Most of these Microsoft write-ups come from Software Engineers (372), then Product Managers (124) and Machine Learning Engineers (53). The most reported rounds are the technical phone screen (255), the product sense round (111), the system design round (93) and the behavioral / leadership round (49).

597 interview notes · updated Oct 2026

Microsoft·Software Engineer·Onsite - Coding / Algorithms

May 2026
Microsoft coding round, pretty much just the LRU cache problem. Classic question but the O(1) constraint is where people trip up if they haven't seen it before.
  • Design and implement an LRU cache with get and put operations, both running in O(1) average time. The cache should evict the least recently used entry when it exceeds capacity.

“The question itself is fine, I knew what an LRU cache was.”

View Post

Microsoft·Software Engineer·Onsite - Multi Round

May 2026
Microsoft software engineer loop, heavy on resume deep-dives and behavioral questions with some AI coding follow-ups sprinkled in. Nothing too wild but the behavioral portion was more thorough than I expected.
  • Walk me through a specific project on your resume and explain the technical decisions you made.
  • Tell me about a time you had to adapt when requirements changed mid-project.
  • How have you used AI tools in your coding workflow, and what are the limitations you've run into?

“They picked a project I hadn't mentally prepped for and just started drilling.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Microsoft SWE interview with a grid traversal problem that looks like BFS but has a twist that'll trip you up if you're not careful. One question, fairly well-defined, but the edge cases pile up fast.
  • Given an m x n grid of open and blocked cells, find the minimum number of moves to travel from a start cell to a target cell, where each move lets you travel 1 to k cells in a straight cardinal direction as long as every cell along the path is open and within bounds. Return -1 if the target is unreachable.

“My first instinct was plain BFS and I started coding before fully thinking through what 'move' meant here.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Microsoft SWE interview, one question about a tough engineering problem you've worked through. Not much else to go on from what was shared.
  • What's the hardest engineering challenge you've ever solved?

“Classic opener that sounds easy until you're actually in it.”

View Post

Microsoft·Software Engineer·Onsite - Behavioral / Leadership

May 2026
Microsoft software engineer loop round, heavy on resume grilling and behavioral questions with a real focus on AI coding project details. Nothing too exotic but they pushed hard on specifics.
  • Walk me through your AI coding project in detail, including the technical decisions you made.
  • Tell me about a time you had to adapt your approach mid-project when something wasn't working.

“They didn't just want the high-level pitch.”

View Post

Microsoft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Microsoft product design interview, one question, pretty open-ended. The prompt sounds straightforward but there's a lot of surface area to cover and it's easy to go in circles without a clear framework.
  • How would you design a version of LinkedIn specifically built for freelancers?

“I started by trying to define what makes freelancers different from full-time job seekers and that actually helped a lot.”

View Post

Microsoft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Microsoft PM interview with a single product design question about rethinking a TV remote. Pretty open-ended, which I wasn't fully prepared for.
  • How would you redesign a TV remote control?

“I fumbled the opening by jumping straight into features without clarifying who the user even is.”

View Post

Microsoft·Product Manager·Onsite - System Design / Architecture

May 2026
Microsoft PM interview with a system design question that pushed into both product and technical territory. Not a pure coding screen but definitely not just vibes either.
  • Design the front-end and backend system for a food truck.

“I went straight to the customer-facing app and spent way too long on the ordering flow before they nudged me toward the backend.”

View Post

Microsoft·Data Scientist·Onsite - Behavioral / Leadership

May 2026
Behavioral round at Microsoft for a Data Scientist role. One question, but it was a beast. They wanted the full story: conflict, root cause, what you actually said, numbers, and what you'd do next time.
  • Tell me about a specific conflict you had with a teammate or stakeholder. What caused it, what options did you consider, and what did you actually do to resolve it? Walk me through the outcome with real numbers, and what you'd change if it happened again.

“This question has so many layers that I started answering before I'd figured out where I was going.”

View Post

Microsoft·Software Engineer·Onsite - System Design / Architecture

May 2026
Microsoft system design round focused entirely on building a rate limiter from scratch. One question, lots of depth expected, and I felt the pressure pretty quickly once the follow-ups started stacking up.
  • Design a rate limiter service. Walk through your algorithm choice, how you'd enforce it locally vs across distributed instances, how counters get shared, and how you'd handle bursts versus steady traffic while balancing accuracy, latency, and availability.

“I jumped straight to token bucket because it felt cleanest for burst handling and kind of glossed over fixed vs sliding window.”

View Post