Microsoft has a long reach with its partner ecosystem. It may start slow on new efforts, but then builds a tidal wave across its product line. That assumes, of course, that the market hasn't shifted again in the meantime.
There are relatively few companies where your work will affect hundreds of millions of users. There are different mindsets and pacing with that than companies with a few dozen or hundreds of users.
Good benefits, up to 5 weeks of vacation (depending on tenure), et cetera.
Microsoft is continuing to implement its "Functional" organizations, putting common points of alignment among disciplines further up the food chain.
In some organizations, this puts a long distance to the person responsible for making sure the engineering disciplines work together as a team.
If you have the small company mentality of wearing many hats, read the Career Stage Profiles carefully.
In a small company, creating value is the top priority; Microsoft is emphasizing creating value within your discipline.
There were three technical rounds after the initial phone screen and take-home coding test. - HLD: Design a booking system for movie tickets. - DSA: Two simple, LeetCode easy, string-based questions. - LLD: Movie ticket booking system, the same as H
I secured a phone interview through a referral. A recruiter contacted me to schedule the interview, which took place a few days later. The on-site interview proved to be much more difficult.
I had an on-campus interview at my university, where the interviewer focused on design issues and basic algorithmic questions. I can recall a couple of questions: how to determine if two circles intersect, and how a server should behave if it has to
There were three technical rounds after the initial phone screen and take-home coding test. - HLD: Design a booking system for movie tickets. - DSA: Two simple, LeetCode easy, string-based questions. - LLD: Movie ticket booking system, the same as H
I secured a phone interview through a referral. A recruiter contacted me to schedule the interview, which took place a few days later. The on-site interview proved to be much more difficult.
I had an on-campus interview at my university, where the interviewer focused on design issues and basic algorithmic questions. I can recall a couple of questions: how to determine if two circles intersect, and how a server should behave if it has to