My Microsoft On-Campus Internship Interview Experience
Anonymous User
309

My Microsoft Internship Interview Experience

Sharing how my Microsoft on-campus internship process went, OA to offer. Nothing fancy, just how it actually happened.

Background

Microsoft came on-campus, we registered, and after resume + CGPA-based shortlisting, around 200 of us got through to the OA.

OA

75 minutes, two questions — basic and intermediate, different for everyone. Mine:

  • Basic: Given an array, cost = sum of (curr − prev)² over consecutive elements, 0-indexed starting from index 1. You get one move — insert any value anywhere in the array — to minimize the cost after that move.
  • Intermediate: Asteroid Collision.

Solved both in 16 minutes. Interview invites came 3 days later.

Round 1

Right before the round, my laptop's mic and speaker stopped working. I didn't have earphones with me, so after trying to fix it and then borrowing a pair from a friend, I joined about 20–25 minutes late.

I apologized, and since we'd already lost time, the interviewer went straight into the question — LeetCode 79 (Word Search), a fairly standard one.

I asked a clarifying question, explained my approach, then coded it, checking in along the way. It ran fine, I walked through an edge case, and then got some tough follow-up questions which I managed to answer. Everything — coding, explanation, follow-ups — was done in 25 minutes. Feedback at the end was positive.

Got the Round 2 link about 20 minutes later, scheduled 45 minutes out, so I went back to my hostel for headphones and returned.

Round 2

This interviewer was a Principal Engineer. After introductions, he asked about my area of interest and I ended up talking about one of my projects for about 10 minutes.

Then he gave a problem with very little detail: a list of tuples, where each tuple says the first racer finishes before the second. Then three questions:

  1. Is the data valid?
  2. Is the data complete?
  3. Who finishes first and last?

He asked me to restate the problem myself before starting. My approach was a bit different from the usual way, and after reviewing my code he said, "Don't talk while you code, I'll just review it after."

I solved questions 1 and 3 and explained my reasoning. On question 2, with about 15 minutes left, I kept jumping between different approaches — all correct, but not optimal — and missed the simpler idea I should've seen. He told me to just stay quiet for a bit and think instead of talking it out. After about two minutes I got it, explained why it worked, and then went through the implementation.

He'd mentioned from the start that the round was about thought process, not implementation. At the end he said he'd pass feedback to HR, and when I asked what I could improve, he said: when you're stuck under pressure, stop talking and focus on thinking instead of explaining — and that looking for edge cases was a good habit to keep up.

Result

Got the offer the next day.

One extra detail: our campus had actually been told Microsoft wasn't visiting that year since their slot was full, but they came anyway. And despite the mic/speaker issue costing me 20+ minutes in Round 1, it still worked out.

(refined wording using AI)

Comments (3)