Snowflake Software Engineer candidates report algorithm-heavy coding, follow-up extensions, design discussions, and behavioral or manager conversations. Reported loops range from four to six interviews.
$195K
Avg. Base Comp
$405K
Avg. Total Comp
4-6 rounds
Typical Rounds
3 weeks
Process Length
Snowflake Software Engineer candidates most consistently describe live, algorithm-focused coding with meaningful follow-ups. Reports include graph problems, BFS, trees, tries, regular-expression matching, dynamic programming, backtracking, event-log processing, and an O(1) insert/delete/get-random variant with duplicates. Several candidates say the initial solution was only the starting point: interviewers then introduced constraints such as out-of-order or duplicate records, missing events, optimization requirements, edge cases, or complexity comparisons. Practice narrating assumptions, testing a baseline, and improving it under discussion rather than coding silently.
Design is also a recurring part of the reported process. One candidate designed recurring notifications and discussed recurrence rules, retries, duplicate prevention, worker failures, time zones, and daylight saving time. Another described a system-design discussion touching on networking, cloud, and database fundamentals. The exact scope may depend on seniority, so be ready to clarify requirements and make tradeoffs explicit.
Recruiter, hiring-manager, behavioral, and sometimes presentation conversations appear alongside technical evaluation. Prepare concise examples of challenging projects, disagreement or feedback, platform ownership, and why you want to join Snowflake. One report involved a recruiter screen, coding, system design, and behavioral round, while another included an HR screen, hiring-manager conversation, technical interview, presentation, and director discussion. Use these stages as preparation themes rather than assuming a fixed loop.
Synthesized from 22 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Snowflake process.
My Snowflake process started with both a recruiter conversation and a separate AI recruiter interview. The recruiter screen covered my background and the process. The AI interview required my camera to be on, lasted about 25 minutes, and asked about my experience, including the most complex backend work I had done. I also received an online HackerRank coding round early in the process.
After that, I had two technical coding screens on CoderPad. The questions were medium-to-hard LeetCode difficulty and algorithm-heavy. Both screens involved trees: one was a traversal problem and another was a variation on deleting nodes. I also encountered graph/BFS-style questioning, including a modified shortest-path problem, and a hard Trie question. The follow-ups mattered, so landing an initial solution was not enough.
The onsite included one coding interview, one system-design interview, and one behavioral conversation. The system-design prompt was a shared quota system for multiple products under one storage plan, where all services consume from the same quota bucket. The interviewer wanted a different solution direction than I expected.
Overall, I found the technical bar high, especially for data-structure and graph/tree questions with follow-ups. I did not receive an offer.
Prep tip from this candidate
Practice tree traversal and delete-node variants, Trie problems, and BFS shortest-path questions with follow-ups. For system design, practice a shared quota service coordinating usage across multiple products and adapt when the interviewer takes the discussion in a different direction.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Snowflake
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Comments Histogram | |
| Random SQL Sample | |
| The Brackets Problem | |
| Level Of Rain Water In 2D Terrain | |
| Real-Time Transaction Streaming | |
| Basic Regex | |
| LLM Enterprise Search | |
| Cumulative Sales By Product | |
| Merge N Sorted Lists | |
| Log Anomaly Detection Model | |
| Sample Time Series | |
| Average Unique Counts | |
| Blob Indexing | |
| Minimum Days for Scheduling All Meetings | |
| Shortest Path Algorithms | |
| Order Assignment and Delivery Time | |
| Client Solution Pushback | |
| Reddit-like Notifications | |
| Empty Neighborhoods | |
| Merge Sorted Lists | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Top 5 Turnover Risk | |
| String Shift | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Prime to N |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report recruiter screens and, in some cases, an AI recruiter conversation or hiring-manager discussion early in the process. These conversations may cover prior work, a challenging project, technical background, why Snowflake, and how you handle pressure; prepare concise, specific examples.
Candidates report HackerRank or other online coding assessments as well as one or more live coding sessions. Questions ranged from medium to hard and included graphs, trees, BFS, hashmaps, tries, regex, and event logs. Expect to explain complexity, edge cases, alternate approaches, and improvements after a correct baseline.
Candidates report system-design, low-level design, behavioral, hiring-manager, and occasionally presentation conversations. Design prompts varied, including notifications, quotas, authentication, and multiplayer extensions, so focus on clarifying requirements, reasoning about tradeoffs, and connecting decisions to operational concerns.
