Opportunity to work with talented and smart individuals, and work on a product that has many users.
Lots of communities within Google, easy to meet people like yourselves outside of your team and cross-pollinate ideas.
Depending on your org, it can get highly political and bureaucratic. Feedback loops are slow and unhelpful (performance reviews happen once or twice a year and aren't actionable).
Encourage more real-time feedback between peers and up and down the reporting chain.
I was brought into the New York City office for five forty-five minute problem sessions. One session was with two interviewers, and the other four were with a single interviewer. In each session, I was asked to solve a technical problem, writing my
The recruiter brought me in. I then had five 45-minute, one-on-one sessions with different people, asking different questions. Most required writing code on the whiteboard. I had an HR break in the middle for lunch. It was quite intense, with tough
Scheduling the Google CoderPad interview was smooth. The interview itself was challenging yet stimulating. I was told that I was rejected due to the position being closed out, which was pretty weird.
I was brought into the New York City office for five forty-five minute problem sessions. One session was with two interviewers, and the other four were with a single interviewer. In each session, I was asked to solve a technical problem, writing my
The recruiter brought me in. I then had five 45-minute, one-on-one sessions with different people, asking different questions. Most required writing code on the whiteboard. I had an HR break in the middle for lunch. It was quite intense, with tough
Scheduling the Google CoderPad interview was smooth. The interview itself was challenging yet stimulating. I was told that I was rejected due to the position being closed out, which was pretty weird.