Great benefits/perks. Great work/life balance. Good internal mobility. Surrounded by smart, understanding people. Great place to learn and grow your career.
Very Bay Area-centric, so high earnings don't go nearly as far if you want to be where most things are happening in the company.
Often hard to feel impact, especially if working deep in back-end systems or systems you're not very excited about.
Pretty locked into Google frameworks even when other options are better. Can sometimes feel like Google is a bit of a tech island.
Foster more innovation from the bottom up. Improve internal communication/organization systems.
It was painful to contact the recruiter to set up the onsite interview after I passed the phone screen. She would drop off and then come back weeks later. The onsite interview was easy. It included: * A dynamic programming problem * String processi
I was given a medium-hard question on graphs during the exam. I spent too much time trying to figure it out. Unfortunately, I ran out of time before finishing the code.
The interview was 45 minutes in total. At the beginning, there was a bit of introductory small talk about his role, mine, etc., lasting roughly 5-7 minutes. Then we moved to the technical question. We first went over the question, asked a few clarif
It was painful to contact the recruiter to set up the onsite interview after I passed the phone screen. She would drop off and then come back weeks later. The onsite interview was easy. It included: * A dynamic programming problem * String processi
I was given a medium-hard question on graphs during the exam. I spent too much time trying to figure it out. Unfortunately, I ran out of time before finishing the code.
The interview was 45 minutes in total. At the beginning, there was a bit of introductory small talk about his role, mine, etc., lasting roughly 5-7 minutes. Then we moved to the technical question. We first went over the question, asked a few clarif