The technical people here are exceptional. I've worked with leaders and pioneers in my field much earlier in my career than I could have hoped to.
I also like the breadth of products that Microsoft builds, so the freedom to move from product to product as my career grows is valuable to me.
My coworkers across the company are also a great resource. I've learned a lot about several Microsoft products in great depth thanks to help from my coworkers.
The perks are also great:
The work-life balance is totally random. Some weeks/months I'll be able to do whatever I want, but some months I'll work 80+ hour weeks a few weeks in a row.
Management attempts to fix this, but I've seen the pattern of poor planning saved by last-minute heroics a few times now.
We also have a tendency to get out of touch with reality. Not everyone in the real world has a quad-core computer with 8GB of RAM and fast internet at home, but we get lulled into making that assumption because everyone we know here has all that stuff.
Continue to make smart investments in people and resources to position Microsoft products at the top of their respective markets.
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