Interview Experience: Unlike other big-name companies, the entire interview process was very smooth, quick, and well-structured. It took me about 2 weeks from the time the recruiter first contacted me to the time I got the offer. The recruiters were really prompt in following up on all the minor details, very adjustable to scheduling, and quick to respond on interview results.
The overall interview experience itself was unique, where I had my lunch interviewer take me for a walk by the beach after having lunch with the entire team. The interviews were very similar to what you expect at any top tech company, but I really liked the fact that I was allowed to code in an IDE of my choice instead of writing on a whiteboard.
On-boarding process: The new-hire on-boarding process is brief and to the point. It was a sweet surprise to see that people already know you by name when you are taken for a walk around the campus buildings.
Engineering team: The engineering team is well-organized and well-structured. It's a great opportunity to do full-stack development where you are allowed to work on features end-to-end. There is a strong sense of ownership and commitment to deliver features. Every team has a good mix of junior and senior developers. Since it is such a small team and the product is growing continuously, there are plenty of opportunities to showcase your potential and grow.
Work: Because of the unique and ephemeral nature of the product, the work is really challenging and interesting. It's good to have your entire day focused on solving the problem, as I spend less than 30 minutes a day on emails and meetings. It also allows me to get work done quickly and leave early.
Office space: Although I was initially skeptical about working in an office space right by the beach, I have started to really like it now. It's literally a beach house transferred to office space, and it has all the amenities with an amazing view from the rooftop and the deck.
Whenever I see myself getting stuck in a problem, I tend to go for a walk by the beach to the shore and refresh myself. Sometimes, we just go out and relax ourselves with a game of volleyball. The office staff are really kind, and there are security people in and around the building 24/7.
Food: It's really great that I can turn up at work and not worry about cooking lunch or dinner, as food is prepared by the chef daily, and the entire team has lunch together. If you want to eat outside, there is also an option to eat at a few handpicked restaurants just by showing your badge.
Transparency: Every engineering team meets with the leadership team on a weekly basis, where we are told about all the different things happening within the company - new features, growth, monetization strategy, etc. It is quite amazing to see the level of business details shared with the engineering team.
Compensation: The base pay is comparable to any other top tech company, and no other tech company can match the equity portion provided here.
Staying at Venice can be a little expensive.
Continued growth means that the cafeteria is getting crowded during lunch and dinner. It might be worth considering having another one.
It's easier to get distracted by events happening at the beach.
Keep up the good work and ensure that the culture of Snapchat remains intact as we continue to grow.
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 process consists of an online code challenge, a phone screen, and a full-day onsite. The process can move very quickly, but it was I who was slowing it down. Recruiters are prompt to respond, and their communications are concise and efficient.
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
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 process consists of an online code challenge, a phone screen, and a full-day onsite. The process can move very quickly, but it was I who was slowing it down. Recruiters are prompt to respond, and their communications are concise and efficient.
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