1p3a Experience · May 2026

snowflake software engineer tech phone screen interview experience

SWE Phone Screen newgrad
1 upvote 4 replies

Interview Experience

Coding: 类似于利口 鹅鹅陆无 区别是要确定root node是不是所有subtree的avarage。 做完之后又快速来了一个酒巴亿,但是直接问了如果input不是按照increasing order。直接答了treemap简单写了写,没跑test。 SD:这轮比较奇怪。问了一个和普通sd不沾边的问题,最后说是从snowflake以前的incident转变过来的。说你控制一个client,会定期和一个third party service拿token,然后用token来access你们的backend,问怎么能优化尽量让offline时间最短。 最大的问题是这里边没涉及到backend,说所有backend都是black box,纯做client。 瞎聊了一堆,最后说是他们之前service因为类似的事情down了很久,所以拿这个来考,但我也没看出他想考啥。

Full Details

🔒

Unlock all Snowflake questions

Full insider details, leaked discussions, and candidate experiences.

Get full access — from $50/mo

About Snowflake Interview Reports

This question was reported by a candidate who interviewed at Snowflake. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.

Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Snowflake are the higher-signal extractions to take from this report.

For broader preparation context, the Snowflake interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.

How To Practice This Type of Question

Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.

Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Snowflake reports consistently are the ones worth investing in; one-off niche problems are not.

During Your Snowflake Round

Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.

The single most predictive failure mode in Snowflake reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. 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 written notes.