real interview stories, told over a cup of tea ♡
Snowflake Interview Experiences
3935 interview stories from candidates at 857 companies: how each round went, what was asked and how it ended. Every company page links to practice questions in the same style.
- 3935
- Experiences
- 857
- Companies
- 532
- Offers
19 results
- In-Person Onsite with an AI-Augmented Rate Limiter Round and a Reference Check Before the OfferSnowflake · Machine Learning Engineer · Onsite · Sep 2026Offer
It's actually been a while since I interviewed, but I was recently looking back on my job switch this year and it came to mind. It was a pretty distinctive interview experience, so I'm writing it down to give back to the forum. I'm an MLE. Every other company I interviewed with leaned toward models; this was the only one that leaned toward agents, and the title was very on-trend: "AI Engineer". T…
- Tree Deletions and Four-in-a-Row DetectionSnowflake · Software Engineer · Technical Screen · Sep 2026
The author reports two Snowflake coding interviews, each lasting about an hour in an executable editor without AI assistance. The sessions included introductions or project discussion, technical work, and time for questions. The first round examined a multi-child tree where deleting a node promotes its children rather than removing its entire subtree. The initial task asked for the resulting heig…
- Two Coding Rounds and Four ProblemsSnowflake · Software Engineer · Technical Screen · Sep 2026In progress
IC1 phone screen, with two coding rounds. The interviewers were all very nice. I hope they will show mercy and let me pass. 🙏 Here is the timeline as well: 8/3: Referral 8/4: Scheduled the HR call 8/7: HR call, then the interview was scheduled that same day 9/3: Virtual onsite with two rounds First round: Question 1: Throne Inheritance. The only difference was that init did not provide the king.…
- Two Phone Screens, DAG Coding and a Control Plane DesignSnowflake · Software Engineer · Technical Screen · Sep 2026
Two phone screens, one coding and one system design. The coding question was a "privilege" problem that is already on the forum (the DAG allow/disallow letters one). The difference in the requirements was that each node passes down its own final state to its children, instead of passing allow and disallow separately. I propagated in topological order, and at each step every node computes its late…
- Rate Limiter in CoderPad, Ran Out of Time Before the Distributed Follow-upSnowflake · Software Engineer · Technical Screen · Aug 2026Rejected
Snowflake phone screen, one hour, writing Python in CoderPad, and I was allowed to use AI. The recruiter said this round looks at how you ask about requirements, how you test, and how you debug. [Question] Build a rate limiting service. Different clients can have different rate limit tiers, for example free, pro and enterprise. The limits for each tier can be updated at runtime without restarting…
- Snowflake Account Executive Interview Experience: fourth of five stagesSnowflake · Account Executive · Other · Jul 2026
I reached the fourth stage of a five-stage process. The interviews felt normal and focused mainly on my SDR background, target performance, and day-to-day work. Nothing about the questions felt overly complicated or mysterious. I did not get an offer, but the salary made the opportunity hard to walk away from. I still felt it was worth pursuing because the potential upside looked much larger than…
- Snowflake Account Executive interview: direct outreach without a clear application pathSnowflake · Account Executive · Jul 2026No response
I contacted a sales leader directly on LinkedIn after seeing her post. There was no job description or application link, so I didn't have a clear formal process to follow. She asked for my CV in English, a reference contact and an English cover letter. She said English would be needed because global leadership would take part in hiring. I resent my CV with the cover letter and references, then he…
- Two Onsite Coding Rounds, Rejected Over a Tricky Input AssumptionSnowflake · Software Engineer · Onsite · Jul 2026Rejected
Two onsite rounds, mid-level, both coding. Both rounds were repeat questions I'd seen before, but they happened to be from the few I hadn't practiced. A bit unlucky. Overall the interview experience was fine — the interviewers were all nice, and they asked me a lot about how I use AI in my day-to-day developing cycle. Wiki Hopper — basically a webpage has multiple links that let you jump to other…
- Two Technical Rounds, Set Card Game Follow-up Ran Out of TimeSnowflake · Software Engineer · Technical Screen · Jul 2026Rejected
I interviewed about a month ago. Mid level. The HR screen already told me they would ask medium to hard questions. There were 2 interviews of 1 hour each. In some of them you get 2 questions in the hour, in some just 1. We started with a quick self-introduction and then went straight into the problem. The first round was a variant of a known problem. It asked for the sum of all node values along…
- Onsite Coding and Job Scheduler System Design, No OfferSnowflake · Software Engineer · Onsite · Jun 2026Rejected
Coding: this was an OO design problem I hadn't seen anywhere on the forum before, implementing two functions. One function is addTask(taskId, priority, timestamp) — the same task can be added multiple times at different timestamps. The other is executeTask(), which is the tricky part — you first sort by priority, and if a task has already been executed, you skip it. System design: job scheduler.…
- Rate Limiter and N-ary Tree Rounds, No DP AllowedSnowflake · Software Engineer · Technical Screen · Jun 2026Rejected
3 YOE, mid-level. After talking with the HM, there were two phone screens, and they were still pretty hard. Coding 1 Design a rate limiter. Just one rule Multiple rules Is it thread-safe, and how would you make it thread-safe (lock) If the request handler throws an exception for a given request, that request shouldn't be counted Don't drop the other rate-limited requests — when there's spare capa…
- A Vague Distributed Tree Counting Design ProblemSnowflake · Software Engineer · Technical Screen · May 2026
Phone Screen 1 The interviewer gave me a distributed tree counting problem that took me a while to even understand. There was no starter code or example — he just said to imagine tree nodes distributed across different places on a network, and my job was to design a class to accomplish that. The problem was way too vague at the start, and we spent a long time discussing what exactly he wanted. I…
- Self-Written Test Cases in the Screens, Then an IC1 OfferSnowflake · Software Engineer · Onsite · May 2026Offer
Hi all! I got an offer from Snowflake for the IC1 level, and I'm posting my loop here in case it helps someone who's getting ready. It began with a recruiter contacting me, followed by a first conversation with the hiring manager. We went over the team, when the interviews would happen, and what they were looking for. Nothing surprising, but it gave me some context before the real interviews. Nex…
- Two Coding Phone Screens and a Quick RejectionSnowflake · Software Engineer · Technical Screen · Feb 2026Rejected
Both rounds of my coding phone screens were with interviewers from the company's tagged LeetCode question set. I'd recommend grinding more LeetCode before you go in. The first round was LC 210 style — directed graph topological sort. Not much to say about the problem itself, except I had to write my own test cases. The interviewer for this round didn't seem to be feeling well — she was coughing a…
- Built a Streamlit App Instead of LeetCode, Rejected After OnsiteSnowflake · Data Scientist · Onsite · Oct 2025Rejected
Got in through a referral. Hiring Manager interview — the whole thing was just chatting about my project, it went pretty well, and I moved forward to the next round. Technical round — I'd read a report on the forum saying they usually ask 3sum and some fairly hard SQL, but it turned out to be building a small data application with Streamlit instead. It really did require partition SQL, plus being…
- A Quota System Design That Ran Out of TimeSnowflake · Software Engineer · Technical Screen · Sep 2025Rejected
Interview process Both sides introduced ourselves. The interviewer asked about one of my projects — I don't quite remember what exactly they asked. Then system design. Then I asked the interviewer some questions. System design Question: design a Quota System that's shared by multiple upstream services. For example, Google Drive and Google Photos share 100GB of space, and each user has one global…
- A Trie Backtracking Bug I Never FixedSnowflake · Software Engineer · Technical Screen · Sep 2025
First round: the interviewer — I really feel bad, she kept trying to help me the whole time, but in the end I still didn't get the bug fixed within the hour. The input is a string array: [California, California/San Francisco, California/San Francisco/7th Street], etc. The other input is an array of the nodes to delete, e.g. [California/San Francisco], and the return should be [California]. LeetCo…
- Binary Search on Error Logs, Then a Graph BFS/DFS Follow-upSnowflake · Software Engineer · Technical Screen · Sep 2025
A classic problem in application-question form. Binary Search The input is a log history. There are three kinds of logs: Info, Warn, and Error, and each log starts with its own type — for example, an Info-type log looks like "[Info] ...". The log history follows two patterns: Once an Error shows up, the service is down, and every log after that is also Error. The first Error is always preceded by…
- Log Binary Search With Two Graph Follow-upsSnowflake · Software Engineer · Technical Screen · Sep 2025
A classic problem in applied-problem form. Binary Search The input is a log history. There are three types of logs: Info, Warn, and Error, and each log line starts with its own type — for example an Info log looks like "[Info] ...". The log history follows two patterns: Once an Error shows up, the service goes down, and every log after that is Error The log right before the first Error is always…
