Decent pay and benefits, work/life balance. Lots of seemingly "intelligent people". Playing catch-up can be fun. Game Dept. is the best to work at.
Shark Tank. Contractors and blue-badgers, fighting for the scraps mentality, as Microsoft slowly sinks. All the really talented people already left. Ranking reviews leave everybody always at each other's throats, looking for ways to degrade you. It's a bad environment for innovation. The really nice people end up leaving due to the aggressive, competitive nature of the environment. Intellectual bullies. Lots of bureaucracy to deal with. Stratification. Contractors are treated as in the same category as janitors, for the most part.
Windows Team people are the worst to work with. The mentality reeks of obsolescence and a Nazi camp work ethic. One of the Indian program managers raped a janitor in building #27 (Windows Group).
Buildings 25, 27, and 28 are toxic, and so are most of the people. The Windows Group harbors obsolete mentalities that need to be flushed out before they destroy Microsoft from the inside.
In building #26, the Automation Group consists mostly of senior-citizen-like people: old, grey-haired, fat, unhealthy, resource hogs, who are on the edge of retirement. All the good people have left, or purposely forfeited their jobs in lieu of better offers.
Change the ranking system. Fire yourselves and get open-minded people with vision, innovative, forward-thinking, and diverse mindsets that hire diverse people.
A full-day process, broken into multiple individual one-on-one interviews. These interviews can include time at the blackboard, writing snippets of code or scripting. Not for the faint of heart or the unprepared.
The initial phone screen was friendly. The recruiter was helpful and gave some good tips on what kind of questions to expect. However, they should be doing a better job screening candidates and not just randomly interviewing developers with no testi
I submitted my resume and spoke briefly with a representative at the job fair on campus. I received a call back a couple of days later. They were extremely fast to schedule an on-site interview, which took place in about two weeks. The interview was
A full-day process, broken into multiple individual one-on-one interviews. These interviews can include time at the blackboard, writing snippets of code or scripting. Not for the faint of heart or the unprepared.
The initial phone screen was friendly. The recruiter was helpful and gave some good tips on what kind of questions to expect. However, they should be doing a better job screening candidates and not just randomly interviewing developers with no testi
I submitted my resume and spoke briefly with a representative at the job fair on campus. I received a call back a couple of days later. They were extremely fast to schedule an on-site interview, which took place in about two weeks. The interview was