Good work-life balance, ~36-40 hour work week, respect for vacation time, etc.
Some extremely smart people around to learn from, especially when it comes to developing real-time, low-latency systems.
Really spacious, cool campus with a lot of little perks.
Everyone spends most of their time on frivolous busywork: meetings, manually sideloading files because the proper build process takes too long, refactoring code, or dealing with forced refactoring.
It's so bad that there's actually a term for meaningful work to distinguish it from normal daily tasks: "Impact". You're "making an impact" if you manage to actually do something that will improve customers' experiences or make other engineers more productive rather than waste more of their time.
FYI, at most companies I've worked with, "Impact" is the standard. A lack of impact results in termination of the employee, team, or the entire company itself.
Microsoft under Satya Nadella is paying lip service to the philosophy that made Microsoft great in the first place and has been serving other companies so well recently. But in practice, the company is a bloated, ineffectual behemoth of failure.
Most of the people who brought the tech industry to its knees in the 80s and 90s got rich and got out. They trained a generation of quiet, useless busybodies to replace themselves.
Anyone with any passion or dedication to quality got slowly extruded out the back end of the company over the last 20 years, until we got to this point where Microsoft abandons and reboots their failed phone platform every two years. They make laughably terrible moves like removing the Start Button and forcing updates on people mid-presentation.
It's easy to QQ anonymously online, but I'm not sure what I could do to eliminate all this worthless dead weight if I were the CEO. Just telling people to quit refactoring and going to meetings isn't going to make them into a bunch of dynamic, self-starting go-getters.
I had two technical interviews over the phone. Both technical interviews were challenging but doable. I had to write code using a web application that allowed both me and the interviewer to see what I was typing. After those interviews, I had one mo
There was a meet and greet at a restaurant in my area. Microsoft paid for food and such. Soon after, I received some emails and LinkedIn profiles, and then a phone interview. I did well and went straight to the onsite. It was a full day of intervi
Overall, the interview process is professional. It started with a phone screen, then I flew to Redmond for an on-site interview. The team was quite interested in my past projects and asked for a lot of details. The coding questions were not very har
I had two technical interviews over the phone. Both technical interviews were challenging but doable. I had to write code using a web application that allowed both me and the interviewer to see what I was typing. After those interviews, I had one mo
There was a meet and greet at a restaurant in my area. Microsoft paid for food and such. Soon after, I received some emails and LinkedIn profiles, and then a phone interview. I did well and went straight to the onsite. It was a full day of intervi
Overall, the interview process is professional. It started with a phone screen, then I flew to Redmond for an on-site interview. The team was quite interested in my past projects and asked for a lot of details. The coding questions were not very har