Snowflake · Primly Community

Went through the Snowflake DE loop last month, here's the actual breakdown

hardware_hugo · 5 replies

Finished the loop for a Senior Data Engineer role on the platform team. Six rounds total, which felt like a lot but was actually pretty well-organized.

Round 1: Recruiter screen, 30 min. Standard background, comp expectations, timeline. No surprises.

Round 2: Technical phone screen with an engineer. 45 min live coding in CoderPad. Two LeetCode-style questions, both medium difficulty. One graph problem, one string manipulation. Nothing exotic.

Round 3: SQL deep dive. This one surprised me. Not just "write a query" stuff, they wanted me to talk through micro-partitions, when to use clustering keys, and how to think about query pruning. I did fine but if you haven't actually used Snowflake internals you should spend a week in the docs first.

Round 4: System design. Design a streaming ingestion pipeline at scale. Felt like a standard data infra design interview, they wanted to see how I thought about backpressure and schema evolution.

Round 5 and 6: Back-to-back behavioral panels. Two separate interviewers, STAR format, very explicit about wanting specifics. One interviewer kept asking for a "more recent example" when my first one was from 3 years ago. Take that as a hint.

Offer came 9 days after the final round. Overall felt fair. The SQL round is the one most people seem underprepared for based on the Glassdoor reviews I read.

5 replies

backend_bekah

the clustering keys question is genuinely tricky if you've only used Snowflake from the query side and not from the admin/optimization side. did they ask you to write DDL for a clustered table or just talk through the concepts?

de_derek

talked through concepts and then I sketched some pseudo-DDL but they weren't grading syntax. more interested in whether I knew WHY you'd cluster vs. just that the feature exists. i said something about high-cardinality filter columns on large tables and that landed.

sre_sol

"more recent example" is such a tell. they have it in the rubric. if your example is pre-pandemic you are basically asking them to discount it. I learned this the hard way at a different company.

market_realist

9 days is fast. most of my loops this year have been 3-4 weeks minimum from final panel to offer. was this a high-priority open req or just lucky timing?

de_derek

honestly no idea. recruiter mentioned they'd had a few declines and were trying to close the role. I think that accelerated things.