A recruiter contacted me for a hiring event three months after I applied through LinkedIn.
There were three rounds of interviews.
The first round was with a somewhat junior-level engineer. They asked a dynamic programming problem. I started with a brute-force approach, but the interviewer interrupted and wanted the most optimal solution in the first iteration. This felt negative, but I coded it up pretty fast, and it passed all scenarios. This might have led to negative feedback.
The second round was with a somewhat senior engineer. They asked a problem and, if time permitted, a few other sub-problems. I solved the main problem with recursion, and the sub-problems were also solved with minor code tweaks. I theoretically explained another sub-problem solution, and the interviewer seemed impressed with my approach, stating he saw a 'new' and 'interesting' way to solve the problem. After that, there was a design problem which I didn't completely understand, although I provided almost the right answer. My feedback for this round was strongly positive.
The third round was with the Group Engineering Manager, who spoke very nicely and professionally. I could sense their authority. They asked an abstract design problem which I understood but couldn't code up properly. I feel this is where my candidature went in a downward direction.
I received a rejection email after a day.
Dynamic programming: Even/odd max sum
Grid traveler problem with some tweaks
DFS/Graph/Forest related questions
The following metrics were computed from 2 interview experiences for the Microsoft Principal Engineer role in Bengaluru, Karnataka.
Microsoft's interview process for their Principal Engineer roles in Bengaluru, Karnataka is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Microsoft's Principal Engineer interview process in Bengaluru, Karnataka.