Microsoft has an outstanding benefits package and generally respects a clear work/life boundary. There is also generally a lot of support in terms of tools and infrastructure.
The Microsoft development cycle is painfully slow. Organizational changes happen quite often, so engineers are at a disadvantage when it comes to providing support and/or documentation for their software. The culture seems to have embraced this, rather than creating incentives for collaboration and ownership.
Microsoft should take a closer look at whether maintaining proprietary and inferior versions of existing open-source tools is worthwhile. It should also consider making greater efforts to foster collaboration between teams.
1st round: phone interview. 2nd round: onsite. Onsite: * Meet 4 people. * Each person will ask you 1 or 2 questions.
I had one phone interview and then an in-office interview. On the phone, I described my experience and was asked one simple technical question, which I answered. After a week, I received an offer for an interview. I had two one-on-one talks, with a
A recruiter emailed me in late June, asking if I was interested in Microsoft. I replied "yes" with my resume attached. There were two phone screenings about data structures and algorithms in the following two weeks, and then I flew to Seattle for an
1st round: phone interview. 2nd round: onsite. Onsite: * Meet 4 people. * Each person will ask you 1 or 2 questions.
I had one phone interview and then an in-office interview. On the phone, I described my experience and was asked one simple technical question, which I answered. After a week, I received an offer for an interview. I had two one-on-one talks, with a
A recruiter emailed me in late June, asking if I was interested in Microsoft. I replied "yes" with my resume attached. There were two phone screenings about data structures and algorithms in the following two weeks, and then I flew to Seattle for an