Nice pay. WFH first culture. Great office culture. Very impactful work in Azure orgs and lots of career growth. WLB may be poor or good depending on how quickly you ramp up and understand the systems.
Recent layoffs across the company shocked many people.
Azure orgs have a steep learning curve because the systems are complex. On-call and incident-driven work may not be for everyone.
Azure is quite complex to ramp up. Depending on your manager and the level you are hired at, you may be expected to understand the systems in an unreasonable amount of time. This gets worse when senior employees do not help well with ramp-up or do not have good documentation available.
Azure has lots of different orgs, so all I am saying here is that it's team-dependent. I don't know how it is in other orgs or teams across Microsoft.
The quicker you ramp up, the easier the job becomes, and the better your confidence and WLB will be.
I had a phone screen, followed by a technical style interview covering LeetCode and system design. The LeetCode portion included two questions with clarifying follow-ups that mirrored typical processes. The interviewers were nice, but I didn’t get
Easy Interview 6 rounds: * 5 coding * 1 human resources Topics covered: * System design of a recommendation system * Microservices vs. monolith * High-level design * Low-level design * Dynamic programming * Bipartite graph * Loop in a linked list
All of my interviews were remote, even though I'm in town. There was an initial behavioral/get-to-know-you interview, followed by a circuit of several technical interviews, all scheduled for one day. Each interview was conducted with a member of the
I had a phone screen, followed by a technical style interview covering LeetCode and system design. The LeetCode portion included two questions with clarifying follow-ups that mirrored typical processes. The interviewers were nice, but I didn’t get
Easy Interview 6 rounds: * 5 coding * 1 human resources Topics covered: * System design of a recommendation system * Microservices vs. monolith * High-level design * Low-level design * Dynamic programming * Bipartite graph * Loop in a linked list
All of my interviews were remote, even though I'm in town. There was an initial behavioral/get-to-know-you interview, followed by a circuit of several technical interviews, all scheduled for one day. Each interview was conducted with a member of the