J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 5 semaines. J'ai passé un entretien chez Microsoft (Redmond, WA) en sept. 2016
Entretien
Microsoft recruits at my college. I applied by talking to the recruiters at the career fairs.
The first round of interview was on campus. Standard 45-minute interview. The first half of the interview was behavioral, we chatted about my resume and experience and what I like to work on. The second half was technical, and the question was not difficult at all.
I heard back 2 weeks later and scheduled my on-site interview at Redmond, WA. I had four back-to-back interviews. The interviews were mostly technical on standard algorithms and data structures, but they weren't hard either.
Final thoughts: compared to Google and Facebook, Microsoft's interviews were much easier. They really want to see how you think, rather than grilling you with DP questions.
Questions d'entretien [2]
Question 1
You were part of the Microsoft Azure team. We got a call at 2am in the morning from a customer telling us that the service is down. What could possibly happen?
J'ai postulé en ligne. J'ai passé un entretien chez Microsoft (Melbourne)
Entretien
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.
Questions d'entretien [1]
Question 1
The assessment consisted of two LeetCode-medium-level coding questions to be completed within 75 minutes.
J'ai passé un entretien chez Microsoft (San Francisco, CA)
Entretien
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
J'ai passé un entretien chez Microsoft (Seattle, WA)
Entretien
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.