J'ai passé un entretien chez Microsoft en déc. 2018
Entretien
The interview process is very smooth , applied online and got a call from recruiter in 2 days . 1 phone screen and one OTS test and then onsite .
OTS has 3 easy and medium level leet code questions , where we also had to comment and provide analysis of the code .
1) square root without inbuilt function
2) merge two unsorted linked list to sorted array
3) find the bug in the code snipped
Questions d'entretien [1]
Question 1
Onsite
1) replace blank spaces in a string with % with no extra space
2) rotate 2 D array by next 2 positions .
3) find if graph is acyclic
4) find Kth position between two given nodes
For eg 1->2->3->4->5
Node 2 and 4 are inputs , and K is 4 return -1 as only one element lies in between 3 .
J'ai passé un entretien chez Microsoft (Vancouver, BC)
Entretien
HR screening, one technical interview with the hiring manager then three interview loop which covered two system design and one dsa round.
System design was intensive and challenging.
It took them 5 weeks to come back with an offer. Background check was completed in a week, got joining date after 3 days.
Questions d'entretien [1]
Question 1
Design a system for a startup company that let users post various types of content and get a unique url which can be shared with others to access the content
J'ai passé un entretien chez Microsoft (San Jose, CA)
Entretien
Started with a recruiter phone call and a 30 minute phone call with the hiring manager to negotiate a remote role since the job was based in Seattle and the manager agreed. Following up with five rounds of virtual on site. Four of them are coding/design. One of them is behavioral mostly leetcode medium level questions which I finished and I was able to do all the follow up and answer the design and time complexity questions correctly after the interview got ghosted for a whole month and got an automatic rejection email.
Questions d'entretien [1]
Question 1
Leet code medium level questions. DFS, BFS, sliding windows and greedy algorithm. Follow up, asking some design questions and the time complexity of the code.