← Back to Directory

Snowflake interview notes, page 1 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·Recruiter / HR Screen

Sep 2024
Applied for an SDR role at Snowflake in September, got nowhere through the careers page, so I cold emailed hiring managers and actually got a response. Made it to a recruiter screen that lasted maybe five minutes, felt fine, then woke up the next morning to a rejection email and genuinely couldn't tell if it was an automated system rejection from my original application or a real one after the call.
  • Walk me through your background and relevant experience.
  • What is your current compensation and notice period?

“Standard opener, went through my background quickly.”

View Post

Snowflake·Data Scientist·Technical Phone Screen

Aug 2025
A Snowflake data scientist interview that went deep into experiment design for a ranking change, with a lot of moving parts around conflicting metrics and decision frameworks. The question was essentially one long case study broken into four parts, and it felt more like a product analytics design review than a standard interview.
  • You're launching a new 'Smart Sort' ranking for a content feed that's expected to improve relevance but may hurt short-term ad impressions. Pick a single primary success metric and two or three guardrails from a given candidate list, and justify your choices using statistical properties like variance, sensitivity to bots, weekday stability, and susceptibility to Simpson's paradox. Define precise formulas and whether you'd use winsorization or log transforms.
  • Design the A/B experiment for this ranking change: choose the randomization unit, identify interference risks specific to ranking, describe mitigations like sticky bucketing or ghost ads, determine test duration, and compute the required sample size for a 1% relative MDE at 90% power and alpha of 0.05. Also explain how you'd use CUPED or stratification to reduce variance, given a baseline window of August 18 to August 31 and a test end date of September 1.
  • If the primary metric is up 0.8% but a guardrail metric like creator payout per impression is down 2.5% with statistical significance, how do you make the launch decision? Walk through a principled trade-off method, and also cover how you'd handle novelty effects, ramp strategies, sequential monitoring, and heterogeneous treatment effects across countries.
  • After a 10% rollout, what on-call dashboards and alert thresholds would you set for the first week post-launch?

“This is where I spent most of my mental energy.”

View Post

Snowflake·Data Scientist·Technical Phone Screen

Sep 2025
Snowflake Data Scientist technical screen, heavy SQL focus with a pretty gnarly multi-part problem involving deduplication, window functions, and time windowing. The kind of question where you think you understand it and then realize halfway through that the edge cases are doing most of the work.
  • Given a 7-day UTC window, compute daily metrics: unique viewers (after deduplicating exact duplicate events), count of completed orders per day, and the conversion rate between the two. Write this as a single Standard SQL query.
  • At the user level, within the same 7-day window, return each user's first completed order timestamp, last completed order timestamp (NULL if no completed orders), and total completed order count. Use window functions, not correlated subqueries.
  • How would you deduplicate events where rows with identical user_id, event timestamp, event type, product_id, and device_id should be treated as duplicates, keeping only one row per group?
  • Sketch a Pandas solution that replicates the SQL logic: correct UTC time windowing, event deduplication, daily unique viewer counts, and completed order counts per day.

“The dedup piece is what gets you.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Apr 2026
Snowflake coding round with a tree traversal problem. Nothing too wild but the path-finding angle made it trickier than a standard LCA question.
  • Given a binary tree and two nodes A and B, return the shortest sequence of moves (up to parent, left to left child, right to right child) that walks from node A to node B.

“The key insight is that you go up from A to the lowest common ancestor and then descend to B.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Apr 2026
Snowflake software engineer interview with a grid-based coding problem. Pretty standard algorithmic round, nothing too flashy, but the problem had a few wrinkles worth thinking through.
  • Given a 2D grid where some cells represent cakes and others represent people, find the minimum Manhattan distance between any person and any cake.

“My first instinct was to just brute-force every person-cake pair and compute the distance.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Apr 2026
Snowflake coding interview with a graph/scheduling problem that looks like a topological sort question but has a twist on how time accumulates across batches. Not the hardest problem I've seen but the batch timing rule tripped me up for a bit.
  • Given a set of courses with prerequisites and individual completion times, courses with satisfied prerequisites can be started in parallel as a batch. You must wait for the entire batch to finish before moving to the next one, so each batch takes as long as its slowest course. Find the total time to complete all courses, or return -1 if a cycle makes it impossible.

“My first instinct was just BFS with level-by-level traversal, which is the right skeleton.”

View Post

Snowflake·Software Engineer·Onsite - Behavioral / Leadership

Apr 2026
Behavioral round at Snowflake for a software engineer role. Three questions, all pretty standard conflict/deadline/mentorship territory. Nothing too surprising but the mentorship one tripped me up more than I expected.
  • Tell me about a time you had a conflict with a teammate or stakeholder. What was the disagreement and how did you work through it?
  • Describe a time you had to deliver something under a tight deadline. How did you prioritize and handle the pressure?
  • Give an example of a time you mentored a junior engineer or a peer. What did you do and what came out of it?

“Had a decent story ready for this one.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Apr 2026
Snowflake software engineer coding round, one problem about tax calculation. The interviewers were chill and handled the test cases themselves, which was a nice change, but apparently that's not guaranteed depending on who you get.
  • Implement a tax calculation function that computes the correct tax amount given an income and a set of tax brackets.

“Classic progressive tax bracket problem.”

View Post

Snowflake·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Snowflake for a software engineering role. The prompt felt like the interviewer made it up on the spot, which made it hard to know what they actually wanted.
  • Design an abstraction layer that wraps low-level REST API calls so that callers can invoke a clean interface without worrying about constructing HTTP requests manually.

“The prompt was weirdly long and vague, no latency targets, no scale requirements, nothing.”

View Post

Snowflake·Software Engineer·Technical Phone Screen

Apr 2026
Snowflake coding round with a weighted interval scheduling problem. Not the typical course schedule DAG thing you'd expect, which threw me off a bit at first.
  • Given a list of courses each with a start time, end time, and credit value, and a maximum number K of courses you can take, find the maximum total credits you can earn from at most K non-overlapping courses.

“I went in expecting the classic DAG prerequisite version and had to mentally reset when I saw the interval constraints.”

View Post