J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Microsoft en oct. 2016
Entretien
Firstly I got an email from Microsoft and talked with a staff on skype. Secondly, I had a technical interview too on skype. Thirdly I went to microsoft office in another country and had a big interview which was done by 4 people. All of them is controlled by many people and all of them are very friendly and professional.
Questions d'entretien [2]
Question 1
question on skype:
think that there is a string like this : axxxxaxbxxb
write a function that will find the closest space between a and b. according to above string, the closest space is 1. (...axb..)
during my big interview, I had 4 different interview with four difderent people. they were very polite and helpfull so you feel relaxed during the interview. they asked some questions which should be done using linkedlist, quicksort. besides one of them asked about how I can test my code and what kind of things should be important for testing.. they also asked for about what is race condition, scaliability of project, testing techniques, agile methodologies..
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.