Snap · Primly Community

Just finished my Snap iOS loop. Full breakdown.

mobile_mara · 5 replies

finished the loop last week, got the offer, taking it. here's what actually happened:

round 1: recruiter screen, 30 min. she was fast and organized, had clear timelines. said 2-3 weeks total which was accurate.

round 2: coding with a mid-level iOS eng. two questions, both on the easier-medium end. one was a string manipulation thing, one was basically 'implement an LRU cache.' i coded in Swift because they said i could pick any language but then the interviewer seemed mildly surprised? ended up fine. he asked me to walk through memory management at the end, not leetcode, just conceptual.

round 3: system design. i got 'design a photo/video upload pipeline that degrades gracefully on flaky networks.' very on-brand for Snap. i talked a lot about client-side buffering, retry logic, progressive upload chunking. they liked that i thought about the mobile client experience as part of the system, not just the backend.

round 4: behavioral with a senior eng and a PM. they asked about a time i shipped something imperfect under a deadline, and a conflict with a PM where i thought we were building the wrong thing. no gotcha energy, they seemed genuinely curious.

offer came 5 business days after the final round. salary + RSUs + 10% annual bonus target. team is working on camera features which is honestly why i'm taking it. the product has issues but the camera stack is legitimately interesting.

5 replies

newgrad_neil

this is so helpful, thank you. did they give you any feedback on the system design round during the debrief or was it just pass/fail? i have mine in two weeks and that's the round i'm most worried about

mobile_mara

no real-time feedback during the round itself. recruiter said the debrief generally doesn't get shared in detail but she mentioned 'strong systems thinking' when she called with the offer so i assume that landed. just talk through tradeoffs out loud, they seem to value the narration as much as the answer.

corp_refugee

the 'mildly surprised by Swift' thing tracks. a lot of these consumer companies say 'any language' but the interviewers are mostly set up for Python or Java. Swift was a reasonable call given the role though. congrats on the offer.

ux_uma

really glad they asked about the conflict with a PM in behavioral. that's actually a revealing question when it goes both ways. did they push back on your answer or just listen?

mobile_mara

mostly listened, the PM in the room nodded a lot. i tried to frame it as 'here's what i learned about communicating earlier' rather than 'i was right and the PM was wrong' which i think was the right call