Microsoft is still a very powerful company. There are jobs and software it creates for just about everything. You feel like the company cares about you, far more than free soda. They have training classes on everything you could think of, and for those who manage to get themselves into the good graces of management who likes them, the sky is the limit. There are still good jobs at Microsoft, but it's hard to find them.
There is a strong tradition of failing upwards. The company has lost a lot of its best and brightest to other companies, and the bottom-feeders that are left tend to be very bad at their jobs.
The company's biggest problem is how political it is. You will never get a promotion on the merits of the job you do; you must get into the "inner circle" of a higher-up manager to have any chance.
Most of the time, instead of dealing with the politics, people just get fed up and leave -- and forever after have nightmares about their experience.
The company has a mandate to fire 7% of their employees a year, and if you aren't in the top-tier inner circle, you feel like you're always fighting for your job. Every promotion you get is one that someone else did not.
Avoid the Office division like the plague; it is the least innovative part of the company. The technical stagnation of "It's been done this way for years, and we'll continue to do it this way" permeates every part of the product. You will not grow or learn there.
For some, it's OK because they have a relatively high paying job that doesn't expect much of them. But I wanted more.
Get rid of HiPo, The Bench, 1+.
Or, if you decide to keep them, tell employees they exist. Explain who is and is not on them, and what the criteria for them are.
Listen to your employees and focus on making good managers, versus managers who are good at managing up.
Do something to fight attrition, and make it easier for employees to move between divisions of the company.
Invest in technical competence and be less results-driven.
Be a technology company that happens to need to make money, versus a business that happens to be a technology company.
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