Updated by Microsoft candidates
Software Engineer Interview Experience
Interview process
Screen plus three loop rounds, all four back to back in one day. Coding problems were standard stuff, nothing exotic. What got me was that every single one had a follow-up that killed my first answer. Bounded the input range on the median problem, pushed hard on edge cases in the editor. If you only have one approach ready you'll stall. What went well: recruiter was clear about the format, no surprises on logistics. Rounds started on time. What didn't: I underestimated how draining four in a day is. By the calculator round I was slower than I should have been on something I've done plenty of times. The behavioral questions were also mixed into the coding rounds instead of getting their own slot, so I was context switching the whole time.
- Phone interview
- Final round
Interview tips
Practice the follow-up, not the problem. Every round, the interviewer changed a constraint after my first solution and wanted to see if I'd catch the new approach. Know when a heap becomes a frequency map, when you can drop a data structure entirely. Say your edge cases out loud before they ask. Have four behavioral stories tight and short. Three minutes each. They come at the end of each coding round when you're already tired. Sleep. It's a full day.
Company culture
Interviewers were direct but not adversarial. They pushed hard technically, nobody was trying to trip me up. Behavioral questions were all customer angled, which tracks with what Microsoft says publicly about their values. No red flags.
Questions asked
Question types asked
Specific questions asked
Started with two heaps. Then he capped the value range, and at that point heaps are overkill, a frequency map works better. That follow-up is the actual question.
Detect the @, filter as the user types, arrow keys to navigate, insert as a token not plain text. Also asked about debouncing and what happens if you keep typing past the @.
Calculator with brackets.
Stack. Nested parens, operator precedence. Parse and evaluate as separate steps or it gets ugly.
Get full access with a membership, or share your experience to try it free.
