Good health benefits are available for everyone at Microsoft. In the Seattle/Redmond area, you get a health club membership or can opt for $800/year in reimbursed expenses. Need a new bicycle to work out? You can use it for that.
Microsoft has been good on resumes for getting interviews at my new company; however, most experienced Microsoft engineers fail their interviews because the work at Microsoft doesn't prepare them well to get hired outside. You have to prepare yourself.
Your work at Microsoft prepares you to do your job at Microsoft, not a lot on the outside.
Every year someone would get a bad annual review, which meant everybody was on edge for the rest of the year.
What does that mean? There is incentive for your coworkers to stab you in the back.
Managers don't know much about your daily work, so presentation skills are vital to get the visibility you need to survive.
No matter how much Microsoft wants you to have work-life balance, everyone ends up sacrificing it due to the threat of a bad review.
That doesn't mean your boss wants to skewer you (he/she might; different story), it means everything is tinged with internal competition.
Internal competition is more important than external, because the customers won't fire you, but your boss will.
Figure out how to better utilize your workforce rather than pitting them against each other. Pit them against your competition instead!
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