As a software engineer, one reason to go to Google is because they have some of the most impressive software and hardware infrastructure in the business. How do they manage to answer any question you can think of in under a second? How many computers do they actually have? How can you possibly manage so many computers? What does it take to run security for them? If you work there, you can (eventually) learn something about everything. And with hard work, you can have a huge impact on this amazing system.
The company is big. Really big.
It has struggled for years to maintain a "startup-like" environment, and in many areas it succeeds. But as the company scales, there are more frequent instances of internal politics guiding decisions instead of pure technical merit.
Keep Google focused on building some of the world's most impressive technology, and you'll continue to attract the best technologists. If you get bogged down in incremental improvement, they will flee.
The infrastructure organizations need to have a cleaner division of responsibilities so that lower management feels empowered to get things done. Upper management doesn't have the bandwidth to manage if too many decisions get escalated to them.
First, an online assessment, then the HR call, then several rounds of technical interview (you need to solve data structure/algorithm problems), and finally a manager interview (mostly behavioral questions).
I had two online interviews with their software engineer. They first asked me about my research at school, and then we started the coding question part. The difficulty of the problems is around medium to hard on LeetCode.
I was invited to have an interview with two engineers for the Google Watch team. I had two rounds in one day, 30 minutes apart. Each round took 60 minutes to complete. They didn't tell me the result for two months, and no feedback was provided.
First, an online assessment, then the HR call, then several rounds of technical interview (you need to solve data structure/algorithm problems), and finally a manager interview (mostly behavioral questions).
I had two online interviews with their software engineer. They first asked me about my research at school, and then we started the coding question part. The difficulty of the problems is around medium to hard on LeetCode.
I was invited to have an interview with two engineers for the Google Watch team. I had two rounds in one day, 30 minutes apart. Each round took 60 minutes to complete. They didn't tell me the result for two months, and no feedback was provided.