Call with recruiter: This was a standard call with one of the recruiters. The conversation was pleasant, and the recruiter seemed genuinely interested in learning more about my experiences. Nothing technical was discussed.
Technical Google Hangout Interview: This was a standard technical video screen with an engineer. We first discussed previous projects and what I was looking for in a role. Then, I had about thirty minutes to solve a coding problem. It was a problem I hadn't encountered before, but it wasn't too difficult. The question was different from typical "Cracking the Coding Interview" problems, but it was definitely doable.
New York Office Project: The New York office has a different process than other locations. This part of the interview was project-based rather than a typical Superday. I received a project upon arriving at the office and was given five hours to complete all tasks. Employees discussed my work with me every hour or so, with a longer coffee break halfway through. I completed four out of five tasks, but I believe all tasks must be finished to get the job.
Overall, it was an awesome experience with great people!
Coding question that required a fundamental understanding of bit manipulation.
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.