Snap Ios Engineer Interview Questions
& Process

First, a quick recruiter call to confirm I'm alive. Then, a 15-minute behavioral chat followed by a 45-minute LeetCode medium problem: reversing a string of words, like 'Hi nice to meet you' becomes 'you meet to nice Hi'.

I applied directly online through LinkedIn, no referral. A recruiter reached out via email for an initial chat. This was followed by a 60-minute phone interview that included about 15 minutes of behavioral questions, an iOS code debugging exercise on Hackerrank, and a medium LeetCode question specifically tagged by the company. The next step was an onsite interview, which lasted 4 hours and consisted of four 60-minute interviews. The first onsite interview involved declaring, defining, and implementing a Network Client API and using concurrency primitives like dispatch groups, semaphores, barriers, queues, and sessions to handle results. The second onsite interview featured a LeetCode medium problem (not company-tagged) combined with an Object-Oriented Design (OOD) problem, specifically a variation of BFS. The third onsite interview was a system design for a Snap-specific feature; mock interviews with other iOS candidates were really helpful for this. The fourth onsite interview required hitting an API, fetching data, building a simple app with a collection view, and displaying the data and images in cells. Overall, the process wasn't too difficult and felt practical. I made some silly mistakes that cost time, but the interviewers seemed to understand and offered hints or I managed to fix them quickly. It's important to know iOS concurrency well.

It was pretty straightforward. It started with an intro, then a coding challenge, and I had about 5 minutes at the end to ask questions. I managed to answer everything, my code worked, and I even had extra time to make it better. I heard back the next day and got rejected.