Snap onsite, waiting to hear back
Replies (6)
Geohash bucketing for location sharing is a good design call. Did they push back on consistency guarantees?
The group anagrams streaming follow-up is a good filter. Did they want bounded memory or approximate solutions?
Bounded memory with a hash-based approach. They were fine with approximate frequency counts for the streaming part.
The AI-enabled round format varies a lot across candidates. Some get graph problems, some get DP. Doesn't feel consistent from what I've seen.
Sounds like a very solid loop, especially nailing the streaming constraints on the anagrams and the fan-out in the SD round! 8 days is definitely pushing it, but it's pretty normal for Snap and other big tech right now while they align headcount or wait on the hiring committee. If you don't hear back by tomorrow morning, definitely send a polite bump. By the way, the way you handled the AI round (using it for boilerplate but writing the core logic yourself) is exactly I recently saw questions companies are asking in these rounds on prachub, the kind of workflow I been practicing as well. Best of luck, hope you get that offer!"
Eight days is pretty normal for Snap. Recruiters there are slow. Email them.
Sent a follow-up yesterday. No response yet.
is this full stack(frontend leaning?)