Microsoft·Software Engineer·Onsite - System Design / Architecture
- Design and architect a link shortening service similar to Bit.ly. Walk through the full system.
“I started with the basic encode/decode flow and felt pretty good about that part.”
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
“I started with the basic encode/decode flow and felt pretty good about that part.”
“The core logic wasn't totally foreign but the input change threw me off more than I expected.”
“This question is basically a full ML system design in one shot.”
“I went straight to the replication factor and quorum math (W + R > N) which was the right call, but I fumbled when they pushed on what happens during a network partition.”
“This question kept growing.”
“Said no pretty quickly, which was right, but then stumbled trying to explain why in a clean way.”
“Easy opener but I rambled.”
“Pretty open-ended.”
“I jumped straight into the SQL groupby-sum approach and felt pretty good about it, then they asked about ties and I kind of stumbled.”
“Felt pretty solid on self-attention mechanics but stumbled a bit explaining why you'd want multiple heads instead of just one big attention matrix.”