Microsoft Rejected Me 3 Times Before Saying Yes

The first rejection from Microsoft came in January of my second year, for their Explore internship program. I was not surprised. I had barely started preparing and applied mostly on the encouragement of a senior who said I should get the experience of the process. The second rejection came in August, for the full-time SDE role during placement season. That one stung. I thought I had been ready.

The third rejection came from off-campus, in February of my final year, after I had already accepted an offer from another company. I had applied anyway because I genuinely wanted to understand what I kept getting wrong. When the rejection came this time, I emailed the recruiter and asked if there was any feedback they could share. She responded. That email changed how I thought about the whole experience.

What the Recruiter Actually Said

She was more candid than I expected. The feedback on my third attempt: my technical answers were strong, but I kept solving problems without first confirming the constraints with the interviewer. In one case I had solved a problem optimally for a constraint that the interviewer had not actually specified, and when they gave a different constraint, my whole approach needed rethinking. It made me look inflexible rather than thorough. This was the same mistake in a different form across all three interviews, and I had never seen it because nobody had told me.

What I Was Actually Doing Wrong All Three Times

Microsoft interviews, in my experience, weight communication more heavily than many other companies. They want to know how you think, not just whether you can arrive at the answer. I was a fast thinker who was also a quiet thinker. I would process everything internally, arrive at a solution, and then explain it. This is fine if you are correct. It reads poorly if you are wrong, because the interviewer cannot tell where the thinking broke down. Talking through uncertainty is a skill I had to specifically practice.

The other issue was behavioural. Microsoft asks a lot of competency-based questions and I was answering them with vague, short responses. 'I worked with my team to solve the problem' is not an answer. The specific details of how you identified the problem, what you did, how you measured whether it worked — that is what they are evaluating.

The Fourth Time

There was no fourth time. I had already accepted my other offer. But three months into that job, a Microsoft recruiter reached out on LinkedIn for a senior role. I prepared differently, got through all rounds, and this time I got an offer. I did not take it — I was happy where I was — but I understood what had changed. Patience, specific feedback, and a willingness to repeat a process that had failed before with different inputs. That is most of what improvement actually looks like.