The people are pretty fantastic, as are the perks -- food, HR really does have innovative ways of taking care of you, and transportation options. Google has been willing to open up offices where its people want to be, which has been great.
There is a lot of opportunity to travel and communicate your vision to a wider audience. I appreciate some of the hard work that has gone into building the culture, and Google tries hard to maintain that.
There is a sense of legacy, and that great things are yet to come. This is not something that is easily sustained, yet there is so much effort here that it just might work.
Certainly, it's a big company. It tries hard to not be. It tries to rekindle some of the old things that made it unique, but it seems like a lost cause for the most part.
There is much less opportunity to shoot to the top. There is less and less exposure to people outside your organization and too far above your management chain.
There is a lot of work to be done, and Google is pretty cheap about the way that work gets accomplished. It puts added burden on many people, including engineers and lower-level managers. Getting actual things accomplished and seeing how it fits into the company goals has been hard.
Be more proactive in helping your employees.
Make sure they are given the proper tools to succeed.
Don't just rely on large swaths of hardworking, smart people to figure stuff out on their own.
I got referred internally. The recruiter screen was light, mostly asking 'Why Google?' and walking through my current EM role (team size, day-to-day, projects). Then, a technical phone screen with algo questions in CoderPad. One was to design a graph
I applied online and had a phone screening in about three weeks. Next, a technical screening focused on data structures and algorithms. I was given a problem statement to generate code and optimize it. They intentionally missed edge cases within the
The interview loop was pretty standard. I was interviewing for an L6 loop. One coding review, one system design on one day. One team match on the first day. One people management, one technical leadership, and one system design one week later. Ove
I got referred internally. The recruiter screen was light, mostly asking 'Why Google?' and walking through my current EM role (team size, day-to-day, projects). Then, a technical phone screen with algo questions in CoderPad. One was to design a graph
I applied online and had a phone screening in about three weeks. Next, a technical screening focused on data structures and algorithms. I was given a problem statement to generate code and optimize it. They intentionally missed edge cases within the
The interview loop was pretty standard. I was interviewing for an L6 loop. One coding review, one system design on one day. One team match on the first day. One people management, one technical leadership, and one system design one week later. Ove