Software Engineer applicants have rated the interview process at Microsoft with 3.4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 63% positive. To compare, the company-average is 67.6% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 60 days to get hired, when considering 8 user submitted interviews for this role. To compare, the hiring process at Microsoft overall takes an average of 30 days.
Common stages of the interview process at Microsoft as a Software Engineer according to 8 Glassdoor interviews include:
Skills test: 38%
Phone interview: 38%
Presentation: 13%
Personality test: 13%
Here are the most commonly searched roles for interview reports -
Applied through a campus recruiting system and a referral. Had a short interview on campus. Moved on to an on site in my city that was 1 day. I had four interviews, where the questions were all leetcode easy and medium, or a famous hard. Interviewers typed on their laptop to write notes while I was whiteboarding, and whilst they did pre-emptively say that they weren't intentionally being rude, many typed so much that it gave me a bad vibe.
Interview questions [1]
Question 1
Asked a question about how I would store a painting that contained shapes, which contained points. Didn't realise the interviewer expected me to do a system design, awkwardly talked to her for half an hour about what she meant.
I applied through college or university. The process took 1 day. I interviewed at Microsoft (Patiala)
Interview
Online test consisted of three questions to be solved in 1.5 hours. Trim a BST, pattern matching and non repeating character.
68 students were shortlisted out of 250 and there was another test conducted on paper. We were asked to solve 2 DP problems: number of deletions required in an array to make it sorted in increasing order and word break problem. There was a group discussion round after this where we were given a problem and we had to come up with plausible approaches to solve the problem as a part of the discussion. After this round there were 3 rounds of technical interviews and 1 HR interview.
Recruiter invited me to apply for a role and do an Online Technical Screen and said I could use any language I like. The questions were straightforward and I completed them in Python easily and included the description of the thought process. I soon got a rejection -- asked why and the feedback was they don't want built-in methods (which was not mentioned in the question) and the array was not initialized (it was -- and it ran fine when I tested locally). My guess is the grader was reviewing the answers with a mindset from C/C++/Java and my Python solutions got penalized under their mindset. As someone who passed multiple rounds of Facebook/Airbnb whiteboard algorithm grilling, I have to say this feels kinda absurd.