Higher total compensation than competitors. Competitive salaries are augmented by large cash bonuses, equity awards, 401k matching, commuter benefits, and incredible on-campus perks, such as free meals and massages, and much more.
Incredibly bright coworkers. Famous computer scientists from all over the world are working in small teams at Google, and the average engineer is able to approach any one of them.
Very thorough annual 360-degree feedback and promotion committees decide promotions, allowing individuals to succeed even if there is a disagreement with their direct manager.
Google hires so aggressively that you don't necessarily get to meet your manager and teammates before you start. There are so many new people coming in each week that they literally can't arrange this. That is a big downside compared to other companies where you would meet your potential manager before agreeing to work there.
I provided feedback to senior management frequently on Fridays by posing questions at the weekly TGIF session.
Google faces a number of technological, regulatory, and employee-retention challenges, but I am sure senior management is more aware of these issues than I am.
It was good. Two system design interviews, one code review, and two management interviews. The first two interviews were normal. I had to design two different systems. The first one was about sending emails to clients. The second one was about a plat
Everything was ordered, and the process was well designed. It started with a phone screen with HR, covering basic questions from the selected area. Then, a phone screen with an engineer followed. It included one Unix-based operating system question
I breezed through the interviews with all the seasoned engineers. Many phone interviews involved tough questions where I had to think on my feet. I got to the end, and the hiring manager brought in a young woman to watch as I struggled with an overl
It was good. Two system design interviews, one code review, and two management interviews. The first two interviews were normal. I had to design two different systems. The first one was about sending emails to clients. The second one was about a plat
Everything was ordered, and the process was well designed. It started with a phone screen with HR, covering basic questions from the selected area. Then, a phone screen with an engineer followed. It included one Unix-based operating system question
I breezed through the interviews with all the seasoned engineers. Many phone interviews involved tough questions where I had to think on my feet. I got to the end, and the hiring manager brought in a young woman to watch as I struggled with an overl