A recruiter reached out on LinkedIn. I responded, and we chatted over the phone for 30 minutes about what I'm looking for next. I was specifically looking at the NYC office, which has a very different process than other offices.
My first round was a phone interview. I won't reveal too much due to an NDA, but it was definitely a strange format, and I was skeptical on how well I did. The next day, I heard back that I got the onsite.
Due to some upcoming holiday travel, I wanted to move quickly and asked for the onsite to be in the following week. They were able to schedule it internally, but the travel company they used (Amex Global Travel) was pretty terrible with response times and did not work weekends. I didn't get things booked until 3-4 days later, even though the recruiter promised it would all be booked within 24 hours. This was a painful process. They also did not sign off on prepaying for the hotel (which is standard for interview candidates), so the charge was made on my account instead. Since my stay was adjacent to the weekend, they were again unresponsive about this.
Aside from the travel booking woes, the onsite interview was a good experience overall. I was told to eat beforehand as there would be no lunch during the interview. It started at 12:30 PM and I was told it would end around 5:30 PM, but it actually ended around 5:50 PM.
I was interviewing for an Android role, but the question was more generalist. I could use my own laptop. It involved a single problem with multiple parts, and people came to check in on me every hour or so. They would ask me questions about how I structured things and whatnot. Then, the final interviewer came in. I described my entire solution, and he asked me to handle some cases I didn't have time to get to and answered any final questions I had. My personal feeling was that I did okay overall, but I didn't really know what to expect given how open-ended the project was.
A few days later, the recruiter emailed me about having an "update" and asked for a phone conversation. I expected positive news, but I was told I didn't get the offer. He told me the feedback was still positive but that it looked like it was not the right fit (standard messaging). This aligns with a lot of the other reviews on here for the NYC office.
Open-ended project lasting the entire onsite interview.
The following metrics were computed from 11 interview experiences for the Snap Software Engineer role in New York, New York.
Snap's interview process for their Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Snap's Software Engineer interview process in New York, New York.