There are some very smart, passionate people working there.
When you're on a good team, it doesn't seem like work. Employees feel excited and empowered.
The pay and benefits are good, and many people have their own office.
Your career growth and rewards are highly dependent on how well you get along with your manager, how much they'll fight for you, and how effective they are at working the system. Depending on your organization, there can be a lot of reorgs, and your experience and time at Microsoft account for zero if leadership doesn't know you. Lately, Microsoft has been making sweeping changes, such as "a person must be at X number level to have Y position," despite whether or not individuals have been working in and doing well at Y positions for years. Rather than promote the individual to the new level requirement, they are told they can no longer have that position.
Changes in leadership have changed the company from a place where employees felt open to challenge each other and do amazing things to a company where employees just want to work the system for promotions and titles.
Employees in various orgs fear that challenging their management leads to destroyed career paths. Leadership should not just look at those who manage up well, but look down into the company and see how the culture is changing, and not in a good way.
Lots of brain puzzles and escalating interviews with different people on the team. Read the books on brain puzzles asked at MS interviews. They're not wrong. Most people interview with multiple teams. However, if all your interviews are with one te
The interview process was good. The interview was mainly based on coding. There were no specific testing questions. The interview covered: * A question on arrays. * A question on Linked Lists, specifically how to insert a node. * A question o
Initially, I was contacted by a recruiter. I had a quick phone screening and then was called for an onsite interview. The onsite interview was horrible because one of the interviewers was jumping randomly between questions. I believe the interviewer
Lots of brain puzzles and escalating interviews with different people on the team. Read the books on brain puzzles asked at MS interviews. They're not wrong. Most people interview with multiple teams. However, if all your interviews are with one te
The interview process was good. The interview was mainly based on coding. There were no specific testing questions. The interview covered: * A question on arrays. * A question on Linked Lists, specifically how to insert a node. * A question o
Initially, I was contacted by a recruiter. I had a quick phone screening and then was called for an onsite interview. The onsite interview was horrible because one of the interviewers was jumping randomly between questions. I believe the interviewer