You work with the smartest engineers in the world. You solve very difficult problems. You eat delicious food.
You eat too much delicious food.
On a more serious note, it may be a bit difficult to separate work from life because of how closely Google seems to integrate its people. You'll have to work very hard to have a life outside of your code.
The recruitment process sometimes seems a little messy.
I had two phone interviews. Both interviews consisted of coding for given problems. It was only coding; I wasn't asked about my research or areas of interest, even though I am a PhD candidate who mainly researches a specific topic.
Asked typical CS-style interview questions, such as: * Reverse a linked list * Print all permutations of a set of numbers * Graph traversal, etc. This involved writing code on a whiteboard, followed by time/space analysis of solutions, and di
Two 45-minute technical coding interviews, followed by an internship placement process. Google teams interview you in short 30-minute interviews and extend an offer. You can reject an offer and continue interviewing. This process continues until you
I had two phone interviews. Both interviews consisted of coding for given problems. It was only coding; I wasn't asked about my research or areas of interest, even though I am a PhD candidate who mainly researches a specific topic.
Asked typical CS-style interview questions, such as: * Reverse a linked list * Print all permutations of a set of numbers * Graph traversal, etc. This involved writing code on a whiteboard, followed by time/space analysis of solutions, and di
Two 45-minute technical coding interviews, followed by an internship placement process. Google teams interview you in short 30-minute interviews and extend an offer. You can reject an offer and continue interviewing. This process continues until you