Solid engineering practices, respectful colleagues, great benefits, and amazing free food.
It sometimes feels like it's gotten very big. Lots of great brains behind every problem means it's not straightforward to make your mark.
The interview process consists of four rounds. After the first two rounds, an employee takes you to lunch. This lunch does not count as a behavioral question. The questions are all related to algorithms and data structures, and I have never seen simi
I had a phone screen where the engineer on the line sent me a link to a Google Doc. He asked me a question about how I would sort a list of strings that was too big to fit into memory. I got part of the question, but when he asked a follow-up about
Technical phone interview: Most questions were about systems design and a coding question at the end. They briefly asked about what you currently do and your past experience, but the focus was mainly on your knowledge of computer science and problem
The interview process consists of four rounds. After the first two rounds, an employee takes you to lunch. This lunch does not count as a behavioral question. The questions are all related to algorithms and data structures, and I have never seen simi
I had a phone screen where the engineer on the line sent me a link to a Google Doc. He asked me a question about how I would sort a list of strings that was too big to fit into memory. I got part of the question, but when he asked a follow-up about
Technical phone interview: Most questions were about systems design and a coding question at the end. They briefly asked about what you currently do and your past experience, but the focus was mainly on your knowledge of computer science and problem