Very smart coworkers, all the way from search and AI to business. They have impressive backgrounds, and lots of people are truly mission-driven about building the next great search engine.
Tons of opportunity to work on a range of products across various verticals like shopping, finance, ecommerce, etc., and contribute to AI products like Labs, Deep Research, and the browser. The office is well located, and feeling the energy and growth is always exciting.
You'll feel very stretched, especially as it seems like we always need more engineers. The usage and speed of shipping means lots of things break, so you might get called in a few times a month if whatever you shipped is having issues. Don't think you can clock out at 6 p.m.
The massive AI wave makes this all worth it, but for those that simply want a job, this likely wouldn't be your favorite thing. The leadership is trying their best to grow along with the company, but can definitely be a bit too direct, which rubs certain people the wrong way.
Hire faster to keep up with demand, so no one gets burned out too quickly.
Continue to reinforce the vision of being the best search engine possible.
I had a phone screen which was just discussing my past experience and about the projects the team is working on. The interviewer was very intelligent and was curious about my experience. Great experience!
Provided a functional requirement for a chat app to identify what would be a good fit: SQL or NoSQL. Implemented the Low-Level Design (LLD) for the same. More discussion is expected, and the thought process should be explained well.
Smooth process, typical to what you’d expect. There was a "medium" methods question, and another one that was seen on HackerRank. I would recommend someone who goes down this process to brush up on data structures and algorithms.
I had a phone screen which was just discussing my past experience and about the projects the team is working on. The interviewer was very intelligent and was curious about my experience. Great experience!
Provided a functional requirement for a chat app to identify what would be a good fit: SQL or NoSQL. Implemented the Low-Level Design (LLD) for the same. More discussion is expected, and the thought process should be explained well.
Smooth process, typical to what you’d expect. There was a "medium" methods question, and another one that was seen on HackerRank. I would recommend someone who goes down this process to brush up on data structures and algorithms.