Software Engineer applicants have rated the interview process at Microsoft with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 69.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 14 days to get hired, when considering 9 user submitted interviews for this role. To compare, the hiring process at Microsoft overall takes an average of 45 days.
Common stages of the interview process at Microsoft as a Software Engineer according to 9 Glassdoor interviews include:
Phone interview: 33%
One on one interview: 22%
IQ intelligence test: 11%
Other: 11%
Skills test: 11%
Group panel interview: 11%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at Microsoft (Le Caire, ) in Nov 2022
Interview
- Four Interviews in one day, all of them problem-solving Medium Leet Code Problem, - Some of them were not helpful people in the interview and didn't take with you and other people were more helpful and smiled and try to help you through the interview. - Overall experience good.
Interview questions [1]
Question 1
- Medium And Essay Problem-solving Leet Code Problem.
I applied online. I interviewed at Microsoft (Melbourne)
Interview
After submitting an online application, I received a HackerRank assessment after passing the resume screening stage, then I was rejected after completing the assessment and did not proceed to further interview rounds.
Interview questions [1]
Question 1
The assessment consisted of two LeetCode-medium-level coding questions to be completed within 75 minutes.
45 mins technical interview with a member of their San fran team. Very relaxed and informal but questions were focused and lots of follow ups. Easy to schedule as was over video conferencing platform
Straightforward technical loop overall, with strong interviewers at every stage. I genuinely enjoyed the in-depth conversations around technical challenges and algorithmic problem-solving — the entire process felt well-structured and genuinely engaging.