Compensation & benefits
The Google stamp on your resume
Great "rest and vest" opportunities if you know how to be efficient at your job.
Very slow career growth.
Close to impossible to innovate and build products iteratively.
Performance review frameworks create a culture in which individuals and teams build fences around what they own and promote complex solutions even to trivial problems.
There is a big lack of clear leadership who hides behind promoting decisions by consensus and influence. This leads to endless conversations and painfully slow progress from user research to design to implementation.
Folks who have been at the company 5y+ (or their whole career) do not know that there is a world outside where better products are built faster and cheaper.
Stop looking at your own belly button. Instead of trying to rebuild in-house, take the risk of creating partnerships with smaller companies that have superior products.
Don't hire top programmers who want to build complex systems. Hire pragmatic engineers that strive for simple and elegant solutions.
It started with the HR call. HR was very polite and friendly, discussing how much time I needed to prepare for the interview. After we agreed on the date, there was a first technical interview where I had to show my knowledge in algorithms. After I
Initial phone call with a recruiter provided general information about Google and the role in question, followed by a coding interview. I failed the coding interview due to a misunderstanding with the interviewer. The question was simple (implement
A recruiter first contacted me on LinkedIn. After a couple of discussions, I was scheduled for a phone screen interview. Once I had the feedback from the phone screen interview, they decided to move forward with four on-site interviews.
It started with the HR call. HR was very polite and friendly, discussing how much time I needed to prepare for the interview. After we agreed on the date, there was a first technical interview where I had to show my knowledge in algorithms. After I
Initial phone call with a recruiter provided general information about Google and the role in question, followed by a coding interview. I failed the coding interview due to a misunderstanding with the interviewer. The question was simple (implement
A recruiter first contacted me on LinkedIn. After a couple of discussions, I was scheduled for a phone screen interview. Once I had the feedback from the phone screen interview, they decided to move forward with four on-site interviews.