Good work-life balance (depending on the team). Well-known brand, which opens up opportunities. Good pay, especially considering the work-life balance. Intelligent, friendly co-workers and a culture of helping others. You probably won't get in trouble with your manager for taking time away from your tasks to help someone else (although I hear it's become more political at higher levels). You will learn a lot, especially if this is your first job out of school. Mostly stable (although there have been some cutting of teams).
Decline in quality of in-office perks (due to recession).
Mandatory in-office 3 days a week policy.
Old products, limited opportunities for meaningful impact.
Although its relatively stable, its position in the future is threatened by emerging competitors like TikTok and OpenAI.
Most of the resources are being funneled away from certain teams and into LLMs.
Not very diverse, although this is a critique of the whole industry, and Google is admittedly better than other companies and at least offers identity-based employee resource groups.
Do some soul searching and think hard about the future direction of the company and how to reinvigorate stale products. Have empathy for employees and avoid layoffs, especially now that the economy is beginning to recover.
This was a pretty standard process for a software position. It included: * A phone screen with an HR representative. * A phone screen with an engineer. For the in-person interview, I met with four engineers during the day, for an hour each. Th
I had an all-day interview at Google in California. Five interviewers grilled me on questions ranging from graph theory to binary search tree algorithms. A lunch break provided a chance to enjoy some good food and learn more about Google. Unfortuna
It was hard, and ultimately I didn't get a job offer. People were very nice, though. Questions included algorithms, systems design, and others. At one of the interviews, an interviewer pointed out a mistake in my code, saying, "Is there anything w
This was a pretty standard process for a software position. It included: * A phone screen with an HR representative. * A phone screen with an engineer. For the in-person interview, I met with four engineers during the day, for an hour each. Th
I had an all-day interview at Google in California. Five interviewers grilled me on questions ranging from graph theory to binary search tree algorithms. A lunch break provided a chance to enjoy some good food and learn more about Google. Unfortuna
It was hard, and ultimately I didn't get a job offer. People were very nice, though. Questions included algorithms, systems design, and others. At one of the interviews, an interviewer pointed out a mistake in my code, saying, "Is there anything w