Snowflake Software Engineer Onsite Coding Questions
112+ questions from real Snowflake Software Engineer Onsite Coding rounds, reported by candidates who interviewed there.
What does the Snowflake Onsite Coding round test?
The Snowflake onsite coding round is the core technical evaluation. Software Engineer candidates typically see 2-3 algorithm and data structure problems. Problems range from medium to hard difficulty, and interviewers evaluate both correctness and code quality.
Top Topics in This Round
Snowflake Software Engineer Onsite Coding Questions
Maximum Order Volume
Throughout the day, multiple call requests are recorded from customers with a start time, duration, and order volume. The manager aims to choose non-overlapping requests to maximize the total order vo
Efficient Deployments
### Problem Overview - Find an order to deploy n processors in a line to maximize total efficiency given whether 0, 1, or 2 neighbors were deployed before each. - Input: arrays noAdjacent, oneAdjacent
There is a list of meeting room usage requests, where each request is represented by an interval [start, end). At any given time, a meeting room can be occupied by only one request. The task is to det
Snowflake Onsite Coding Interview Tree Minimum Deletions Problem
Problem: Minimize Deletions to Target Tree Height **Inputs** * `root`: The root node of a binary tree. * `k`: An integer representing the target maximum height. **Definitions** * **Tree Height:**
#2742 Painting the Walls
LeetCode #2742: Painting the Walls. Difficulty: Hard. Topics: Array, Dynamic Programming. Asked at Snowflake in the last 6 months.
#202 Happy Number
LeetCode #202: Happy Number. Difficulty: Easy. Topics: Hash Table, Math, Two Pointers. Asked at Snowflake in the last 6 months.
#1136 Parallel Courses
LeetCode #1136: Parallel Courses. Difficulty: Medium. Topics: Graph Theory, Topological Sort. Asked at Snowflake in the last 6 months.
LeetCode #1242: Web Crawler Multithreaded. Difficulty: Medium. Topics: Depth-First Search, Breadth-First Search, Concurrency. Asked at Snowflake in the last 6 months.
#1236 Web Crawler
LeetCode #1236: Web Crawler. Difficulty: Medium. Topics: String, Depth-First Search, Breadth-First Search, Interactive. Asked at Snowflake in the last 6 months.
#1494 Parallel Courses II
LeetCode #1494: Parallel Courses II. Difficulty: Hard. Topics: Dynamic Programming, Bit Manipulation, Graph Theory, Bitmask. Asked at Snowflake in the last 6 months.
#706 Design HashMap
LeetCode #706: Design HashMap. Difficulty: Easy. Topics: Array, Hash Table, Linked List, Design, Hash Function. Asked at Snowflake in the last 6 months.
#261 Graph Valid Tree
LeetCode #261: Graph Valid Tree. Difficulty: Medium. Topics: Depth-First Search, Breadth-First Search, Union-Find, Graph Theory. Asked at Snowflake in the last 6 months.
#243 Shortest Word Distance
LeetCode #243: Shortest Word Distance. Difficulty: Easy. Topics: Array, String. Asked at Snowflake in the last 6 months.
#23 Merge k Sorted Lists
LeetCode #23: Merge k Sorted Lists. Difficulty: Hard. Topics: Linked List, Divide and Conquer, Heap (Priority Queue), Merge Sort. Asked at Snowflake in the last 6 months.
LeetCode #849: Maximize Distance to Closest Person. Difficulty: Medium. Topics: Array. Asked at Snowflake in the last 6 months.
#45 Jump Game II
LeetCode #45: Jump Game II. Difficulty: Medium. Topics: Array, Dynamic Programming, Greedy. Asked at Snowflake in the last 6 months.
#490 The Maze
LeetCode #490: The Maze. Difficulty: Medium. Topics: Array, Depth-First Search, Breadth-First Search, Matrix. Asked at Snowflake in the last 6 months.
#994 Rotting Oranges
LeetCode #994: Rotting Oranges. Difficulty: Medium. Topics: Array, Breadth-First Search, Matrix. Asked at Snowflake in the last 6 months.
#841 Keys and Rooms
LeetCode #841: Keys and Rooms. Difficulty: Medium. Topics: Depth-First Search, Breadth-First Search, Graph Theory. Asked at Snowflake in the last 6 months.
#42 Trapping Rain Water
LeetCode #42: Trapping Rain Water. Difficulty: Hard. Topics: Array, Two Pointers, Dynamic Programming, Stack, Monotonic Stack. Asked at Snowflake in the last 6 months.
What to Expect in the Snowflake Onsite Coding Round
The Snowflake Software Engineer Onsite Coding round has a specific calibration purpose distinct from other rounds in the loop. Across 112+ verified reports on LeakCode for this exact round type, the consistent expectations: clear scoping of the problem before diving into a solution, explicit reasoning about complexity, structured handling of edge cases, and the ability to discuss trade-offs between two reasonable approaches.
Reports tagged with the Onsite Coding round at Snowflake show recurring patterns in difficulty and topic distribution. The Onsite Coding round is typically 45-60 minutes; the interviewer is calibrated against a specific rubric. The discriminator between candidates who advance and candidates who do not is rarely the final correctness of the answer. It is the path: did you clarify, did you verbalize your approach, did you handle edge cases, and did you communicate throughout.
How To Prepare for This Specific Round
Filter the questions below to the most recent reports (past 6-12 months). Questions tagged for this exact round type from this exact company at this exact role level are the highest-signal data available. Older reports may reference questions that have since rotated out of the company's pool.
Practice 4-6 representative problems from this set under timed conditions. The goal is not memorization (companies rotate questions); the goal is to internalize the patterns the interviewer typically reaches for and the depth of follow-up to expect. Reports on LeakCode also tag the typical follow-up depth at this round type, which is the discriminating signal between hire and no-hire calibration.
Onsite Coding Round Timing and Format
The Onsite Coding round at Snowflake typically runs 45-60 minutes. Use the first 2-3 minutes to clarify requirements; you should never start coding or designing without verifying the input/output format, constraints, and edge cases out loud. Use the next 5-7 minutes to verbalize your approach before writing any code. The middle 20-30 minutes are implementation. Reserve the final 10 minutes for testing with concrete examples and discussing optimization or trade-offs.
Time budget discipline is one of the most reliable senior-vs-junior discriminators in this round. Strong candidates verbalize where they are in their budget out loud ("I've used about 20 minutes, I have 15 minutes left for testing and one optimization"). This signals engineering maturity to the interviewer and creates positive feedback they can capture in writing.
Common Failure Modes in This Round
Reports tagged "no hire" at Snowflake Software Engineer Onsite Coding commonly cite: coding silently without verbalizing approach, jumping to implementation before clarifying requirements, missing edge cases (empty input, single element, very large input), producing working code that the candidate cannot refactor when asked, and failing to test their solution with concrete examples before declaring done.
The single most predictive failure mode in 2025-2026 reports: not asking clarifying questions. Interviewers at all FAANG companies are explicitly trained to weight this dimension. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's notes.
See All 112 Questions from This Round
Full question text, answer context, and frequency data for subscribers.
Get Access