The process began with an online test featuring three straightforward problems. The first involved finding a bug in a function (it was to change an AND condition to an OR condition, or something similar). The second required converting a binary string to an integer, and the third was a very simple greedy algorithm.
Following the test, there were three consecutive interviews.
The first interview started with behavioral questions, followed by a technical problem that wasn't strictly algorithmic. Next was a system design component, and finally, the task was to implement a concurrent hash map, which also necessitated implementing a linked list. The code did not need to run, but clarity was essential.
The system design portion was particularly challenging for me. I struggled to comprehend the interviewer's explanations, and they didn't seem to grasp my questions. For instance, when asked about the expected number of vehicles to be sold for a system designed to sell vehicles, the response was "all of them." Furthermore, no feedback was provided on whether my approach was on the right track. The interviewer spoke very little during my design process.
Design a system that sells vehicles, which are also in a showroom.
Users can make a reservation to test one of the vehicles.
The following metrics were computed from 16 interview experiences for the Microsoft Software Engineer role in Bucharest, Romania.
Microsoft's interview process for their Software Engineer roles in Bucharest, Romania is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Microsoft's Software Engineer interview process in Bucharest, Romania.