You will get the opportunity to change the world.
What you do will have a big impact.
You will get the chance to create something that your friends and family will actually directly use.
First, your co-worker is officially your enemy. Expect to be stabbed in the back. Some will say they will help you and tell everyone else how much they are helping you, but then will actually do barely any actual work to deliberately undermine you. Others will talk badly about you. Others will take credit for your work, possibly your own manager. Most people are good, honest folks, but watch out for the bad ones. Especially be watchful for managers who were forced to get themselves promoted out of whatever it was they originally did very well. This is well beyond the normal level of office politics. Your first years will seem great, but problems compound over time.
This is a result of 3 things:
Second, technical ability is not valued as much as management ability. If you love to code, expect to find less and less time to code as you do more management of either other full-time employees and/or contractors and/or vendors. Contractors and vendors do much of the technical work these days.
They need to fix the review system so that teams function as teams. However, there is no point in saying this since, as Microsoft would say, inter-employee competition "is in their DNA."
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