Great, unbeatable benefits covering most types that an employee would want.
Plenty of perks: free drinks, great quality cafeterias all over every campus, etc.
Though there's a feeling of being behind, there's also a strong sense of confidence that MS can once again come from behind to do well and even win.
Work-life balance was terrible, but it got much better in recent years. It is beginning to degrade again. Some teams and organizations have it much better than others; some are pretty terrible.
There is a strong feeling around the company of being behind in technology.
Building configuration is being changed from separate offices with several common gathering areas to large "open" areas of cubicles and general open areas for gathering amongst the cubicles.
Don't lose sight of the importance of maintaining work-life balance.
There have been plenty of studies of work environments that show that "open" cubicle types of environments reduce productivity when compared with separate offices for employees. Common gathering areas are great. This allows and even encourages employees to gather, discuss informally, and even socialize a bit. This improves morale and team cohesion without compromising individual or team productivity, as the cubicle approach does.
I'd strongly encourage the MS management to avoid losing the solid reputation that MS has had in terms of its employee environment, and to prevent the degradation of productivity and morale at such a critical time in Microsoft's history.
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