Snowflake · Primly Community

Snowflake onsite / final round: how it really goes, day-of notes from someone who just did it

qa_quinn · 4 replies

Writing this the morning after my Snowflake virtual onsite. Going to do stream-of-consciousness before the details fade.

Background: senior SWE candidate, 10 YOE, coming from embedded systems / infra. Applied because a friend works there and the distributed query engine work genuinely interested me. Not a traditional FAANG pipeline person.

Structure I had (may vary by team):

Five rounds over two sessions. Three rounds one morning, break, two rounds the following afternoon. Virtual via Zoom, coding in Coderpad.

Round 1: Coding - data structures Heap problem. More specifically, finding the K-th largest element in a streaming data feed with some constraints. Classic but the interviewer added a twist partway through. I got it but took longer than I'd have liked.

Round 2: Coding - systems-flavored Design and implement a simplified query planner. Not full system design, not pure LeetCode. Somewhere between: given a query AST, implement the execution order considering a simple rule set. This was Snowflake-flavored in a way I didn't expect. Interesting problem actually.

Round 3: System design Design a multi-tenant caching layer for a query engine. See my earlier notes on what they're looking for at L5+.

Round 4: Behavioral See the other thread on behavioral questions. Mine matched almost exactly.

Round 5: Hiring manager Chatted more about the team roadmap and my experience with distributed systems. Light technical depth, more about fit and whether I'd thrive in their eng culture. They asked what I find most challenging about working in distributed systems and then drilled down for 15 minutes on my answer.

Overall vibes: Interviewers were engaged and specific. No one looked bored. The coding problems required actual thought, not just pattern matching. The query-planner problem in particular is probably unique to Snowflake or at least rare to see elsewhere.

Expecting to hear back within a week. If you have questions about what it feels like on the day, ask below.

4 replies

content_cole

the 'systems-flavored coding' problem is actually really smart design from their side. it screens for people who've thought about query execution specifically, not just LeetCode farmers. harder to game with a week of prep.

pivot_pat

how long did the debrief take after onsite? asking because i've heard 5-10 business days from a few people and I'm currently on day 7 trying not to check my email every 20 minutes

hardware_hugo

heard from a friend it was 6 business days for them. i was told 'a week' by my recruiter and I'm taking that literally. you're probably fine. no news in the first week doesn't mean bad news.

mobile_mara

The hiring manager round being focused on fit and how you handle distributed systems challenges is very consistent with what I've seen at Snowflake. They're building a specific type of culture: humble but technically exacting. If you come in as a know-it-all you will not get an offer regardless of your coding score.