Microsoft continues to expand its portfolio of software and hardware products, providing development positions in a very wide variety of technologies and areas of interest.
Although flagship products have a very large organization size, individual working teams are small, providing cross-discipline fraternity within the larger context.
The working environment is casual with respect to dress codes and personal communication. Work hours are flexible.
Commute options are plentiful. If you drive, there's ample parking, while Microsoft bus or city transit covers much of the Greater Seattle area.
In general, there's more work to be done than fits into an 8-hour day. For nearly 20 years, I generally worked a 10-hour day, 5 days a week, with another half-day accumulated across evenings or weekends.
The annual review process imposes a ranking across team members, which is not representative of how well they did their jobs. This can lead to deflated compensation and advancement opportunities for individuals who are doing their job well. Conversely, it can advance employees who don't deserve it simply because they did better work than their teammates who were less competent.
This process is slowly changing, but I have no insight as to what new policies will be in place or when.
There were two stages of interviews: * One on campus * One on site This took only a few hours total. On site, I talked to a few full-time engineers about their roles.
I had four one-on-one interviews and a lunch interview. The first three interviews involved being asked many different technical problems to code. The lunch interview, which took place at the restaurant, focused on how well I carried myself. For bo
Coding-based, several programming problems. Coding on the whiteboard, which is not as straightforward as it may sound. There were several different interviews, all quite long, so you had to stay focused throughout the whole day.
There were two stages of interviews: * One on campus * One on site This took only a few hours total. On site, I talked to a few full-time engineers about their roles.
I had four one-on-one interviews and a lunch interview. The first three interviews involved being asked many different technical problems to code. The lunch interview, which took place at the restaurant, focused on how well I carried myself. For bo
Coding-based, several programming problems. Coding on the whiteboard, which is not as straightforward as it may sound. There were several different interviews, all quite long, so you had to stay focused throughout the whole day.