← Back to Directory

Microsoft interview notes, page 29 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·Product Manager·Onsite - Product Sense / Strategy

May 2026
Got a product sense question for what seemed like a PM role at Microsoft, just the one question about Instagram of all things. Short session, nothing too wild, but it made me think harder than I expected.
  • What features would you build to help Instagram users form better connections with each other?

“I went straight to surface-level stuff like shared interest tags and better DM discovery, which felt thin the moment I said it out loud.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Microsoft SWE interview that went deep on string processing fundamentals. One question, but it had a lot of layers: tokenization design, implementation, streaming, testing, and complexity analysis all rolled in.
  • Given a text document, count the number of words. Before coding, define your tokenization rules precisely (contractions, hyphenated words, decimals, punctuation, Unicode quotes, whitespace), then implement a function that handles large files or streams, write unit tests for edge cases, and analyze the time/space complexity. Also compare regex-based tokenization against a manual character scanner.

“This looked like a warm-up question until it wasn't.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Phone screen for a software engineer role at Microsoft. One technical problem, memory allocation, and they wanted me to write my own test cases too which I wasn't expecting.
  • You have a contiguous block of memory with n units. Design a system that supports allocating a chunk of size X and freeing a previously allocated region.

“Went with a doubly linked list and first-fit allocation.”

View Post

Microsoft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Microsoft PM interview with a product design question around parental controls for screen time. Pretty open-ended, which I wasn't fully prepared for.
  • Design a product that helps parents manage and limit their children's phone and screen time usage.

“I jumped straight into features way too fast.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Applied Scientist interview at Microsoft that went deep on regularization theory. One long question covering a lot of ground, which felt more like a lecture prompt than a conversation.
  • Walk through the main regularization techniques used in machine learning (L1, L2, dropout, early stopping, data augmentation, label smoothing) and explain how each one works and when you'd actually choose it over the others.

“This was basically one giant question that unfolded over like 20 minutes.”

View Post

Microsoft·Product Manager·Onsite - Product Sense / Strategy

May 2026
PM interview at Microsoft with a metrics question focused on delivery logistics operations. Single question, product analytics angle, no frills.
  • What North Star metric would you recommend for a COO of a ground delivery company (like FedEx, UPS, or a regional carrier) to track operational health?

“I went with on-time delivery rate as my North Star and then had to defend why that beats cost-per-package or utilization.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Microsoft SWE interview focused on a deep dive into recent project work, specifically the design decisions and tradeoffs involved. Pretty light on algorithm stuff from what I can tell, more about how you think through real engineering problems.
  • Walk me through the design tradeoffs you made in one or two recent projects you've worked on.

“They actually suggested sending over PR links beforehand so you can reference real code during the conversation, which I thought was a nice touch.”

View Post

Microsoft·Software Engineer·Onsite - System Design / Architecture

May 2026
Microsoft SWE interview that was basically one big system design question about org hierarchies. The problem sounds straightforward until you actually have to think through the update semantics and cycle prevention simultaneously.
  • Design a data structure or service that stores manager-to-report relationships in an organization and supports two operations: querying the total number of people in an employee's reporting chain (all levels down), and updating the hierarchy when someone changes managers. Queries should stay fast, and updates need to handle edge cases like cycles.

“I went straight to a tree with cached subtree counts per node.”

View Post

Microsoft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Interviewed for a PM role at Microsoft and got hit with a metrics question right out of the gate. Pretty standard stuff for this type of role but I definitely fumbled parts of it.
  • How do you define success metrics when launching a new feature?

“I started with adoption and engagement numbers and thought that was enough.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Microsoft SWE interview with a classic LRU cache design problem. Pretty standard for this type of role but the O(1) constraint is where it gets real and I fumbled explaining my data structure choices out loud.
  • Design an in-memory key-value cache with an LRU eviction policy, where both get and put operations must run in O(1) amortized time. Walk through the data structures you'd use and why.

“I knew the answer involved a hashmap plus a doubly linked list but explaining WHY the doubly linked list specifically took me longer than it should have.”

View Post