When I was at Google, the company was growing rapidly, and I was able to grow with the company. I was quickly promoted and benefitted from having a lot of senior, experienced people to learn from. I got to work on products used by billions of people, which is an impact that few other places can match.
Google has a lot of bad managers. They spend a ton of money trying to figure out how to make it better, but the tl;dr is that at the senior levels, a lot of the promotion committees (it's an anonymous committee, not your manager, who decides) look favorably on managing people. Especially on the manager track, the size of the organization you manage seemed to matter more than how good of a manager you were.
In many parts of the org, it became impossible to get the promotion to the next level unless you had a manager who was really good about helping you carve out space to manage a large organization within their org.
Career development is mostly an exercise for the reader. There are lots of opportunities available, but you have to go out and find them and push. Don't expect someone to guide you along career development.
At the senior levels, you're at a huge disadvantage outside of Mountain View. And if you're in MTV, you're either suffering a huge commute from SF, or living in an extremely overpriced, boring suburb.
This was a long process with a lot of back and forth. I interviewed for an Engineering Manager, Tools and Infrastructure role. The process started with a recruiter introduction and a call with managers. This was followed by an onsite interview cons
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 was contacted by a recruiter for an EM (Engineering Manager) role. I set up a 30-minute phone screen with the hiring manager. It was a general conversation about my background and experience, with no technical questions. Following this, I was inv
This was a long process with a lot of back and forth. I interviewed for an Engineering Manager, Tools and Infrastructure role. The process started with a recruiter introduction and a call with managers. This was followed by an onsite interview cons
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 was contacted by a recruiter for an EM (Engineering Manager) role. I set up a 30-minute phone screen with the hiring manager. It was a general conversation about my background and experience, with no technical questions. Following this, I was inv