← Back to Directory

Snowflake interview notes, page 11 of 14

Large Enterprises

Most of these Snowflake write-ups come from Software Engineers (118), then Data Scientists (12) and Backend Engineers (2). The most reported rounds are the technical phone screen (91), the system design round (30), the behavioral / leadership round (5) and the online assessment (2).

135 interview notes · updated Oct 2026

Snowflake·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Snowflake software engineer interview with a system design round focused on building an in-memory key-value store from scratch. The scope kept expanding with follow-ups and I wasn't fully prepared for how deep they'd go.
  • Design and implement an in-memory key-value store supporting set, get, and delete operations. Be prepared to discuss data structure choices and time complexity.

“Started fine, hashmap for O(1) ops, nothing groundbreaking.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Jun 2026
Snowflake software engineer coding round, one question, nothing too wild. Started with a naive solution and worked up to something cleaner by the end.
  • Determine whether a given number is a 'happy number'.

“Came up with the linear space solution pretty quick, tracking visited numbers in a set.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Jun 2026
Two fairly meaty coding problems back to back for a Snowflake SWE screen. The first was a topological sort with some follow-up pressure on edge cases, and the second was a full expression evaluator with precedence rules that honestly took me by surprise in terms of scope.
  • Given n tasks labeled 0 to n-1 and a list of prerequisite pairs, return a valid ordering that completes all tasks, or an empty array if no valid ordering exists. Implement this, then walk through both BFS and DFS approaches, explain how you detect cycles, discuss complexity, and talk about how you'd handle streaming edges or multiple valid orderings.
  • Implement a function that parses and evaluates an arithmetic expression string supporting integers, spaces, parentheses, unary minus, and the operators +, -, *, /, %, and ^. Exponentiation is highest precedence and right-associative; division truncates toward zero; use 64-bit integers; raise an error on malformed input. Target O(n) time and space.

“I went straight to BFS with in-degree tracking which felt natural, but then they asked me to also sketch the DFS version and I fumbled explaining the three-color visited state.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Jun 2026
Did a technical screen for a Software Engineer role at Snowflake. Pretty short on details but the first real question was about Java experience, which set the tone for a technically focused conversation.
  • What is your experience with Java?

“Pretty standard opener but I always fumble these a bit because I never know how deep to go.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Jun 2026
Snowflake SWE interview that came down to a spatial assignment problem, the kind where the naive greedy solution works fine until it doesn't. One question, but it had real depth if you let it.
  • Given a set of customers and a set of cake vendors at fixed locations, first assign each customer to the nearest vendor, then redesign the assignment globally to minimize total distance while respecting a maximum customer limit per vendor. Walk through your approach and compare the tradeoffs.

“Started with the obvious greedy pass, each customer just picks the closest vendor, O(n*m), easy to explain.”

View Post

Snowflake·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
Behavioral round at Snowflake for a software engineer role, three questions all in the conflict/deadline/mentorship bucket. Pretty standard stuff but I fumbled the delivery on a couple of them.
  • Describe a time you had a conflict with a teammate or cross-functional partner. How did you handle it and what happened?
  • Tell me about a time you were working under a very tight deadline. How did you prioritize, flag risk, and still get it done?
  • Can you walk me through a time you mentored or coached someone, or helped onboard a new teammate? What did you do and what was the impact?

“I had a real story for this but rambled way too much setting up the context.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Jun 2026
Snowflake software engineer interview with a coin exchange problem that looks like a greedy question but has a twist that trips you up if you're not careful.
  • You have unlimited coins in denominations [1, 5, 10, 50, 100, 200]. To pay an amount n, you can overpay and receive change back using the same denominations. What is the minimum total number of coins exchanged in both directions combined?

“Saw 'coins' and immediately started thinking greedy, which is the wrong instinct here.”

View Post

Snowflake·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Snowflake system design round for a software engineering role. The whole thing was one meaty design problem about real-time trending search, and they pushed pretty hard on the tradeoffs once you got past the surface-level answer.
  • Design a system that returns the top-K trending search terms within a sliding time window, where repeated searches of the same word by the same user count only once.

“This one took me a minute to even scope correctly.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Jun 2026
Snowflake SWE interview, got a classic scheduling problem that I've seen before but still managed to overthink it a little. Two valid approaches came up and I ended up walking through both, which felt like either a flex or a waste of time depending on how you look at it.
  • Given a list of meeting time intervals, find the minimum number of conference rooms needed to accommodate all meetings.

“I knew this problem but still second-guessed myself on the heap approach.”

View Post

Snowflake·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Snowflake system design round for a software engineering role. The question was a deep dive into trie serialization, which sounds manageable until they start asking about streaming, evolvability, and Unicode all in the same breath.
  • Design and implement serialization and deserialization for a trie (prefix tree) that stores a large dictionary of lowercase English words. Your solution should define a compact wire format, handle end-of-word markers, support faithful reconstruction, and address traversal order, framing schemes, robustness to malformed input, streaming, forward/backward compatibility, Unicode, optional compression, memory constraints, and time/space complexity. Provide pseudocode for both serialize and deserialize.

“I came in thinking this was a coding question with a bit of design flavor.”

View Post