Developer 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 Developer 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 Developer according to 8 Glassdoor interviews include:
Phone interview: 38%
Skills test: 38%
Presentation: 13%
Personality test: 13%
Here are the most commonly searched roles for interview reports -
4 technical rounds and no HR round, Very easy questions at campus related to linked list and tree, and from project.
Given a Heap find Nth largest node. you have access to left and right node.
Interview questions [1]
Question 1
There were few good questions related to linked list.
I applied online. The process took 2 days. I interviewed at Microsoft (Hyderabad)
Interview
They don't value experience, ask same thing to a fresher as well as to some 10 year exp guy.. Ask questions from DS, algo, puzzles, design.. No question from domain knowledge..
So cracking Microsoft is easier than cracking TCS..
Interview questions [2]
Question 1
1. Possible moves for horse on chess board and when the horse will go out of the board.
I applied through college or university. The process took 4 weeks. I interviewed at Microsoft (Redmond, WA) in Oct 2014
Interview
Attended on campus code competition, then submitted resume to the campus recruiter. Scheduled an on campus interview, 30 minutes. After one week got an on-site interview with 4 engineers. Received feedback within several days. In each interview been asked several normal behavior questions, and some coding questions, except the last one given a design question.
Interview questions [1]
Question 1
All but the last one were super straight-forward. The last one was about designing and finding problems in a mass-system.