Being able to take ownership of huge projects that will have a direct impact on the product.
Having passionate coworkers.
Being led by people with an amazing vision for the company/product.
Seeing others use the product every day.
Working on innovative features.
Having lots of responsibilities.
Having lots of responsibilities means having to work a lot. But that's part of the fun.
The interview process was quite straightforward. If you have a solid programming background from personal projects or open-source contributions, you should do well. I also recommend the book "Cracking the Coding Interview"; it contains some excellent
The interview process began with an initial HR phone interview, followed by a 45-minute screen with an engineer, which involved two medium to hard LeetCode problems. The on-site portion consisted of lunch with an engineer and then four one-hour inte
Overall, the process was very easy. To put it into perspective, I was rejected from Facebook, Uber, and Google at various points in their pipelines, but I passed Snapchat. Essentially, there were four coding questions on a laptop, and a lunch sessi
The interview process was quite straightforward. If you have a solid programming background from personal projects or open-source contributions, you should do well. I also recommend the book "Cracking the Coding Interview"; it contains some excellent
The interview process began with an initial HR phone interview, followed by a 45-minute screen with an engineer, which involved two medium to hard LeetCode problems. The on-site portion consisted of lunch with an engineer and then four one-hour inte
Overall, the process was very easy. To put it into perspective, I was rejected from Facebook, Uber, and Google at various points in their pipelines, but I passed Snapchat. Essentially, there were four coding questions on a laptop, and a lunch sessi