You must find opportunities to learn from others, and you have the most impact to drive your own career. Nothing comes to you automatically. This is a place where people who take initiative can thrive. People around you are very smart and ambitious. Employees can learn a lot from the right mentor.
Your experience, performance, and opportunities are heavily determined by your direct manager's support and, indirectly, your skip-level manager. Regardless of whether you do good work or bad, the process is highly political. If you have a bad relationship with your manager, even if it isn't "your fault," you're set up for failure. It is, unfortunately, a prerequisite that you manage this relationship first before your actual work performance, because little else matters if your manager does not go up to bat for you.
For me, I was lucky to have supportive direct managers. For many of my peers, however, I've seen very poor managers, and there is little the system can do to protect employees from bad managers. It's a crap shoot at times.
Too many managers at Microsoft. It seems like everyone is a manager-of-people, even when they have 0-2 direct reports. This results in too much hierarchy and too many management layers. Senior managers need to pay more attention to WHI numbers and feedback. There needs to be a better vetting process for managers.
Lots of brain puzzles and escalating interviews with different people on the team. Read the books on brain puzzles asked at MS interviews. They're not wrong. Most people interview with multiple teams. However, if all your interviews are with one te
The interview process was good. The interview was mainly based on coding. There were no specific testing questions. The interview covered: * A question on arrays. * A question on Linked Lists, specifically how to insert a node. * A question o
Initially, I was contacted by a recruiter. I had a quick phone screening and then was called for an onsite interview. The onsite interview was horrible because one of the interviewers was jumping randomly between questions. I believe the interviewer
Lots of brain puzzles and escalating interviews with different people on the team. Read the books on brain puzzles asked at MS interviews. They're not wrong. Most people interview with multiple teams. However, if all your interviews are with one te
The interview process was good. The interview was mainly based on coding. There were no specific testing questions. The interview covered: * A question on arrays. * A question on Linked Lists, specifically how to insert a node. * A question o
Initially, I was contacted by a recruiter. I had a quick phone screening and then was called for an onsite interview. The onsite interview was horrible because one of the interviewers was jumping randomly between questions. I believe the interviewer