← Back to Directory

Microsoft interview notes, page 30 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·Technical Phone Screen

May 2026
Microsoft SWE coding round with one meaty design question about app ranking. The problem sounds straightforward but there's a real design decision buried in it that I didn't handle as cleanly as I should have.
  • You have roughly 500 apps, each with a mapping of keywords to relevance scores. Given a query of one or more keywords and an integer K, return the top K most relevant apps. How do you rank them, and what's your implementation?

“I jumped straight into a heap-based solution before nailing down the aggregation rule, which was a mistake.”

View Post

Microsoft·Product Manager·Hiring Manager Screen

May 2026
Interviewed for a PM role at Microsoft and got hit with a pretty foundational question about core PM skills. Short and to the point, not a lot of fluff.
  • What are the top 3 or 4 skills you think every PM needs to have?

“I rattled off the usual stuff: prioritization, communication, data-driven thinking.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Microsoft SWE interview with a classic URL shortener design problem. Pretty standard stuff but the details trip you up if you're not careful about the round-trip contract and keeping things O(1).
  • Design and implement an in-memory URL shortener with encode and decode methods, where encode converts a long URL to a short one with a fixed prefix, and decode reverses it. Both operations should run in expected O(1) time.

“My first instinct was to use a hash of the URL as the key, which works until you realize collisions are a real problem and you need to handle them.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Microsoft SWE interview with a classic interval merging problem. Pretty standard algorithmic round, nothing too surprising, but the complexity discussion at the end was where things got interesting.
  • Given an array of possibly overlapping and unsorted intervals, merge all overlapping ones and return a sorted list of non-overlapping intervals covering the same ranges. Also discuss the time and space complexity of your approach.

“Sorting first is the move and I knew that, but I second-guessed myself for a minute wondering if there was some O(n) trick I was missing.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a security analyst role at Microsoft, got a pretty foundational crypto question that I thought I'd nailed but second-guessed myself halfway through.
  • What is the difference between encryption and hashing?

“I knew this one cold but somehow started rambling about SHA-256 before actually defining either term.”

View Post

Microsoft·Product Manager·Hiring Manager Screen

May 2026
Interviewed for a PM role at Microsoft and got hit with the classic weaknesses question. Not a lot of process to describe here, just one question that I spent way too long overthinking.
  • What are your weaknesses as a product manager, and what do you do to address them?

“I fumbled this a bit.”

View Post

Microsoft·Product Manager·Onsite - Product Sense / Strategy

May 2026
Microsoft PM interview with a single product design question focused on monetization. Pretty open-ended, which I wasn't fully prepared for.
  • Design an app for an airport that can be monetized. Walk through your thinking.

“I jumped straight into features before even picking a user segment, which was a mistake.”

View Post

Microsoft·Machine Learning Engineer·Technical Phone Screen

May 2026
Had a Microsoft MLE interview that was basically just an A/B testing question. Not much else to report.
  • Walk through how you would design and evaluate an A/B test.

View Post

Microsoft·Software Engineer·Onsite - Coding / Algorithms

May 2026
Microsoft SWE interview that went pretty deep on data structures. The main coding question was a full HashMap implementation, which felt manageable until the follow-up about thread safety turned it into a mini system design conversation I was not prepared for.
  • Implement a HashMap from scratch with put, get, remove, and contains operations, all averaging O(1). Your implementation should handle hash collisions, resize based on load factor, and use a reasonable hash function.
  • Now make your HashMap implementation thread-safe. Walk through different locking strategies and explain the trade-offs between throughput and consistency for each.

“I went with separate chaining because open addressing under pressure felt like a recipe for off-by-one disasters.”

View Post

Microsoft·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a security engineer role at Microsoft, got a networking fundamentals question that felt almost too basic but apparently trips people up more than you'd think.
  • What are some common ports used by a typical Windows or Unix workstation?

“Rattled off the obvious ones: 22 for SSH, 80 and 443 for HTTP/HTTPS, 3389 for RDP, 445 for SMB.”

View Post