Did the Snap OA and two coding rounds this cycle. Here's the breakdown since I couldn't find much recent info when I was prepping.
Online assessment: Two problems, 90 minutes. Hosted on HackerRank. Problems I got were a medium array manipulation and what felt like a modified graph BFS problem. Not super hard, but the second one had an edge case that tripped me up initially. I'd say LC medium difficulty overall, with the harder one pushing toward medium-hard.
Time pressure is real. 90 min for two problems sounds fine until the second one requires thinking through a non-obvious traversal.
Phone screen coding: 45 minutes with an engineer, collaborative editor (CoderPad). One problem, and they asked me to walk through my approach before writing code. The problem was a string manipulation thing, nothing exotic. But they DID ask about time and space complexity mid-solution, not at the end. Be ready for that.
Onsite coding rounds (virtual): Two 45-minute rounds. I got a dynamic programming problem in round 1 and a two-pointer/sliding window in round 2. Both were LC medium. One interviewer mentioned after the fact that they're not supposed to ask hard, so if you're getting smoked, something is off with your prep or the interviewer misread the rubric.
Overall I'd rate it: solidly medium difficulty, not the grind-LC-hards-for-weeks gauntlet some companies require. Python and JavaScript are fine. I used Python and they seemed completely unbothered.
I did not get any Snap-specific questions (like, nothing about how Snap's architecture works or anything product-specific). Purely algorithmic.
I am now in debrief wait hell so cannot report on outcome yet.