The perks, food, and transportation are the main ones, but there are lots of things that make it a geek's paradise if you're into that sort of thing. Games everywhere, free tickets, and shuttles for some movies when they open (Transformers was one), etc.
Let's face it, it looks good on your resume.
The chance to meet some very bright and interesting people.
There are so many opportunities to educate yourself about the world through your employer. Everything from tech talks on a variety of technical topics to visits by politicians and public figures.
It's cool to be on the inside and learn about new products everyone else will be talking about soon.
My experience was that of an intern, so it may not be typical. I ended up doing work I had absolutely no interest in and didn't envision getting my degree for, without much opportunity to do something different.
When interns are recruited, they don't have much of a say on what type of work they'd like to do. So, if you're stuck with something you don't like and want to work on more interesting things, that's what evenings and weekends are for.
If you have a PhD, you can do some fascinating things at Google. But if you just have an undergrad degree, you might be better off at a smaller company, where you will get more opportunities to do different kinds of work that span several job positions at Google.
Products like Lively are released while some others with much more potential have been languishing in development for years. Seriously, what are you thinking?
The interview process included: * Two technical rounds (LeetCode medium-hard). * One research round, focusing on prior projects. * One recruiter screen. After the initial interviews, the process moves to team matching, where candidates meet with va
The early "phone screen" rounds caught me somewhat off guard. Online, I read that I would have around 45 minutes to work on the problem, with the rest of the time dedicated to getting to know the interviewer and so on. In reality, I only had 45 minut
The process took a long time at every step, and communication was lacking throughout. However, the interviews themselves were enjoyable, relatively easy, and everyone was nice. It seems they primarily assess how you handle new problems, so simple me
The interview process included: * Two technical rounds (LeetCode medium-hard). * One research round, focusing on prior projects. * One recruiter screen. After the initial interviews, the process moves to team matching, where candidates meet with va
The early "phone screen" rounds caught me somewhat off guard. Online, I read that I would have around 45 minutes to work on the problem, with the rest of the time dedicated to getting to know the interviewer and so on. In reality, I only had 45 minut
The process took a long time at every step, and communication was lacking throughout. However, the interviews themselves were enjoyable, relatively easy, and everyone was nice. It seems they primarily assess how you handle new problems, so simple me