I applied online. The process took 2 months. I interviewed at Microsoft (Redmond, WA) in Mar 2019
Interview
I got an email from Recruiter and it was a team event. After applying for a position she sent me a online test. I completed the test(basic tree question and math question and find bugs in the given code snippet was an easy one ) and passed it. Fortunately or unfortunately I don’t know the event was full. So after two weeks she sent me one more team event recruiting this time I didn’t take any online test directly I got scheduled to attend onsite interview. I was scheduled to attend 4 back to back 45 min interviews with 15 min break between rounds. They asked me about my current project and general behavioral questions. Every one asked me one problem solving question and some follow up questions. They all are basic array, string, sorting and data structures implementation questions followed by i asking some questions. It was an easy interview overall and the interviewers and recruiters were very friendly and were helping me with some hints.
Interview questions [1]
Question 1
Binary tree questions, string, array, basic data structure development, searching and sorting. Only concentrate on basics, cs fundamentals and your current role and how it relates to their requirement.
I applied online. I interviewed at Microsoft (Melbourne)
Interview
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.
Interview questions [1]
Question 1
The assessment consisted of two LeetCode-medium-level coding questions to be completed within 75 minutes.
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
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.