Microsoft Graduate Software Engineer interview questions
Updated Oct 30, 2025
based on 14 ratings
Difficulty
Average
Experience
Mostly positive
How others got an interview
67%
Applied online
Applied online
11%
Other
Other
11%
Employee Referral
Employee Referral
11%
Campus Recruiting
Campus Recruiting
Interview search
14 interviews
Viewing 1 - 5 of 14 Interviews
Microsoft interviews FAQs
Graduate Software Engineer applicants have rated the interview process at Microsoft with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 80% positive. To compare, the company-average is 66.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Graduate Software Engineer roles take an average of 109 days to get hired, when considering 5 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 Graduate Software Engineer according to 5 Glassdoor interviews include:
Phone interview: 67%
One on one interview: 33%
Here are the most commonly searched roles for interview reports -
The OA was two Leetcode Medium questions, although the difficulty seemed to vary from Easy to Medium. Optimisation was critical to pass the tests. I think it was first come first serve.
Interview questions [1]
Question 1
Combinations of binary digits, modifying strings in a certain manner.
Short interview over the phone about the neurodiversity hiring program. The interviewer was very nice and the program is tailored to neurodiverse individuals. Adjustments allowed:
-Longer breaks between interviews.
-Don't have to tell your manager or anyone else about your neurodiverse nature.
-Don't have to prove your neurodiversity.
The process took 2 weeks. I interviewed at Microsoft (Dublin, Dublin) in Feb 2022
Interview
One first interview with Human Resources, then a code test (leetcode, you already know) and then a round of four interviews in the same morning of 1 hour each. Solving problems and asking questions about code, behaviour...