Google has a rich history of engineering excellence and brilliance. Even many years removed from the height of the company's innovation, some of this is still evident through a strongly ingrained engineering culture, where things are mostly done with an engineering-first mindset.
Engineering excellence is obvious across the organization, and the products and infrastructure built at Google are a testament to this.
Work-life balance is, for the most part, extremely good. Good work-life balance is ingrained in the culture. I have never experienced pressure from managers to work more than 40 hours a week, and the vacation and holidays are decent, though maybe not the absolute best.
There is a clear lack of vision from top management, as many of Google's recent "big" initiatives seem to be reactive to other tech companies, instead of proactive. When compared to top executives at similar large companies, the current management falls quite short.
A complicated performance/promotion process exists at Google in an effort to measure employees fairly across the large company. However, this comes at the cost of wasted cycles and the gamification of the system. This, along with the large variation in teams, results in non-uniform opportunities for promotion and career advancement.
It was a 1-hour technical phone interview. Questions covered algorithms and certain data structures, such as hash maps. You actually coded with the interviewer on a Google Doc. Ask questions if something is unclear; they want to know that you're thin
I was contacted after submitting my resume through their website. The recruiter was friendly and helpful, making sure I knew what to expect throughout the process. After a technical phone interview, which involved answering a coding problem, I was a
It was a hard, long day of coding questions. It was hard to tell how I was doing. I was nervous and didn’t enjoy coding difficult problems under a short time constraint. The soft skills part was also hard to get a read on if I was doing well; the i
It was a 1-hour technical phone interview. Questions covered algorithms and certain data structures, such as hash maps. You actually coded with the interviewer on a Google Doc. Ask questions if something is unclear; they want to know that you're thin
I was contacted after submitting my resume through their website. The recruiter was friendly and helpful, making sure I knew what to expect throughout the process. After a technical phone interview, which involved answering a coding problem, I was a
It was a hard, long day of coding questions. It was hard to tell how I was doing. I was nervous and didn’t enjoy coding difficult problems under a short time constraint. The soft skills part was also hard to get a read on if I was doing well; the i