Flex schedule - I don't get hassled on when I come in, leave, or need time off. The pay is decent, enough so that I don't have to worry about anything. I get to learn about cool technology before others; there is a lot of that on the inside. The product you work on will reach millions of people, if that makes you feel better. It looks quite good on a resume. You will meet some very smart people here, especially if you look for them. Alas, you do have to look. Depending on the group, you will have an office for yourself or share it with one other person. If privacy is your thing, you'll love it.
The tools we get to work with in most of the groups are arcane - mostly C/C++. Some groups do use C# or even F#, so make sure to ask if you care.
Also, our code bases are huge, and we have to maintain a lot of backward compatibility where I work. It is not nearly as agile as banging out a new Web 2.0 cool app.
Also, there is a huge disconnect between customers and {engineers, marketing, etc.}. This leads to a lot of stupid or "evil" outcomes.
If I knew what to do, I would be in Senior Management. I think they should rethink the company vision because we are clearly lacking the focus and motivation we had from "PC on every desk."
A short phone conversation with a recruiter/HR led to a Skype-based technical screening/interview. After passing the technical screen, I was flown out to Seattle for on-site interviews. The morning included two one-on-one interviews, followed by a "
A very standard interview process for technical software engineering jobs. It started with resume submission, followed by a couple of phone interviews and then an on-campus interview loop. The on-campus interview loop mostly consisted of whiteboard
The interview consists of 5 rounds. The first round is easy. The following three rounds increase in difficulty. If you are lucky, you may encounter a "hard mode" (HM) round. Sometimes, depending on the team, there might be 6 rounds.
A short phone conversation with a recruiter/HR led to a Skype-based technical screening/interview. After passing the technical screen, I was flown out to Seattle for on-site interviews. The morning included two one-on-one interviews, followed by a "
A very standard interview process for technical software engineering jobs. It started with resume submission, followed by a couple of phone interviews and then an on-campus interview loop. The on-campus interview loop mostly consisted of whiteboard
The interview consists of 5 rounds. The first round is easy. The following three rounds increase in difficulty. If you are lucky, you may encounter a "hard mode" (HM) round. Sometimes, depending on the team, there might be 6 rounds.