Microsoft doesn't just build great tools; it builds entire platforms. No other company can do this anywhere near the degree that MS can. It's great knowing not just that I have the best tools in the industry, but that I'm part of a company that can do what no other can: making computers useful for people.
Politics: People aren't looking to do the best job or learn the best practices; they're trying to look good for stack-ranking time at the end of the fiscal year.
If you're an Anglo-American male working for Microsoft, get used to being a persecuted minority (see "advice to senior management").
Racism within Microsoft sucks, and so does sex discrimination.
Racism: Yes, I can see the business need for "diversity," even if management usually can't see beyond the color of someone's skin. But making any preference for URM (under-represented minorities, whoever they are at the moment) is racism. Stop it now, or Microsoft might face a very expensive lawsuit.
Ditto sexism: Management commitments for the fiscal year are very explicit about preferential treatment for women. I don't know from the inside, but Google, Apple, Yahoo, etc., probably open opportunities to people according to their ability to deliver for the corporation. Their websites suggest that they are more egalitarian than Microsoft in this respect.
I suggest that Microsoft treat people equally, or again, it could be very expensive for the corporation.
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