Shortened loop due to a prior experience and a referral.
Five onsite interview rounds, including four technical and one culture fit round.
Overall, the questions were creative and not the usual LeetCode variants. The interviewers were more focused on ensuring I had experience designing large-scale distributed systems.
Here's a breakdown of interview questions and experiences:
Design a TinyURL service.
Describe technology trends that will disrupt the industry in the coming years.
Perform a back-of-the-napkin calculation on the number of Google Drive users worldwide. How would you relate this to known data and extrapolate?
Design an analytics stream pipeline for Microsoft Exchange Server logs that are highly sensitive and include PII. The challenge was to design it such that data does not leave the source. I designed with data anonymization leaving the source and traveling through a pipeline of independent systems loosely connected with a messaging system, which did not solve the problem 100%.
Design a logging utility, its major interfaces, and a class diagram.
Design a DevOps utility tool to allow resource allocation and automated deployment and rollback of software components. I had read the Google Borg paper and picked salient features from there. This interview stretched to an hour and a half and went into great detail on the choice of tech stack and solving interesting questions on resource allocation. The interviewer was very bright.
The culture fit round mostly included questions on past experience and leadership skills.
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.