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."
A recruiter came to my college campus and conducted an on-campus interview. This interview was fairly simple; he asked me to talk about a project I had done and then asked me to write a method in Java that determines whether a given string is a palin
The interview process was very good. I had an initial phone interview, followed by an on-site interview. In total, I had six on-site interviews. These interviews were very challenging, but fun. The interviewers made them seem casual. They mainly cons
Submitted my application in late December 2012. Got a call from the recruiter in late January 2013. Had one phone interview discussing some background and technical questions. Then went to Redmond for a one-day onsite interview, and had four intervie
A recruiter came to my college campus and conducted an on-campus interview. This interview was fairly simple; he asked me to talk about a project I had done and then asked me to write a method in Java that determines whether a given string is a palin
The interview process was very good. I had an initial phone interview, followed by an on-site interview. In total, I had six on-site interviews. These interviews were very challenging, but fun. The interviewers made them seem casual. They mainly cons
Submitted my application in late December 2012. Got a call from the recruiter in late January 2013. Had one phone interview discussing some background and technical questions. Then went to Redmond for a one-day onsite interview, and had four intervie