# Snowflake Software Engineer (Intern) Interview Experience Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access. Source: https://www.aced.io/experiences/snowflake-software-engineer-intern-interview-f47cfb Source observed: 2026-11-04T22:42:49.244Z Last checked: 2026-11-04T22:42:49.244+00:00 Indexed: 2026-11-06T20:12:56.508+00:00 --- # Snowflake Software Engineer Interview Experience We publish interview preparation resources through Aced, formerly Exponent. This entry records a Snowflake Software Engineer intern interview experience submitted by a candidate in Canada. The candidate interviewed onsite, was rejected, and described the process as very difficult. ## Interview details - **Company:** Snowflake - **Role:** Software Engineer intern - **Location:** Canada - **Format:** Onsite - **Result:** Rejected - **Interview date:** 7 months before the source observation - **Timespan:** 3 weeks - **Difficulty:** Very difficult The associated Snowflake Software Engineer (SWE) Interview Guide was updated a month before the source observation by Snowflake candidates. It includes an [expert guide](https://www.aced.io/guides/snowflake-software-engineer-interview), [4 interview experiences](https://www.aced.io/guides/snowflake-software-engineer-interview/experiences), [10 questions](https://www.aced.io/guides/snowflake-software-engineer-interview/questions), and [33 resumes](https://www.aced.io/guides/snowflake-software-engineer-interview/resumes). ## Interview process The online assessment was sent automatically to everyone who applied, with resume screening afterward. The questions were generally very difficult. The phone interview was conducted through AI and asked technical questions about the candidate’s experience, projects, and challenges. - Online assessment - Phone interview ## Interview rounds The experience contains **5 questions across 2 rounds**. ### Online assessment **2 questions** Question types included [Coding](https://www.aced.io/questions?type=coding) and [Data Structures & Algorithms](https://www.aced.io/questions?type=algorithms). #### Question 1: subtree pair configurations A database team is moving a database to a new architecture of clusters. Given a tree with `network_nodes` nodes and edge arrays `network_from` and `network_to`, determine whether each node’s subtree can be configured by pairing every node with exactly one adjacent node, with no node used in more than one configuration. Return a string whose `i`th character indicates whether the subtree rooted at node `i` can be configured. The supplied text uses inconsistent OCR for the yes/no characters (`I`, `l`, `T`, and `O`); its example describes a successful configuration as `1` and an unsuccessful one as `0`. A subtree consists of a node and all of its descendants in the rooted tree. Node `x` is a descendant of node `y` when every path from `y` to the root passes through `x`. Edges connect consecutive nodes in a path. **Example:** - `network_nodes = 4` - `network_from = [1, 3, 2]` - The supplied `network_to` example is malformed in the captured text and appears as `12, 1, 4`; do not rely on that transcription as a complete edge array. The stated example says: - Node 1: pairs `(1,3)` and `(2,4)` are possible → `1` - Node 2: pair `(2,4)` is possible → `1` - Node 3: no valid configuration → `0` - Node 4: no valid configuration → `0` - Result: `"1100"` **Function:** `isColoringPossible` Parameters: - `int network_nodes`: number of nodes - `int network_from[network_nodes - 1]`: one endpoint of each edge - `int network_to[network_nodes - 1]`: the other endpoint of each edge Return a string in which the `i`th character indicates whether node `i`’s subtree can be configured. **Constraints:** - `2 ≤ network_nodes ≤ 3 * 10^5` - `1 ≤ network_from[i], network_to[i] ≤ network_nodes` #### Question 2: minimum transfer time A string is transferred through a custom network protocol. The protocol processes character pairs together. A pair containing matching characters, such as `"aa"`, adds `sameTime` seconds. The string may be divided into substrings before transmission; each partition adds `partitionTime` seconds. Calculate the minimum extra time: - time for matching-character pairs; plus - time for partitions. **Example:** `s = "abcabc"`, `sameTime = 1`, `partitionTime = 4` Two stated optimal approaches are: 1. Split into `["abc", "abcc"]`: - `"abc"` has no matching pairs: `0` seconds - One partition: `4` seconds - `"abcc"` has one matching `c` pair: `1` second - Total: `5` seconds 2. Keep the string together as `"abcabcc"`: - The supplied text describes five matching pairs and a total of `5` seconds. The stated minimum extra time is **5 seconds**. **Function:** `getMinimumTime` Parameters: - `string s`: string to transfer - `int sameTime`: extra time for a matching pair - `int partitionTime`: time for a partition ### Phone interview The supplied accessible text identifies **3 questions**. The visible interview details describe a 45-minute conversation with a senior interviewer, mostly open-ended questions, a short follow-up near the end, and substantial discussion of tradeoffs. Questions and candidate responses included: - **Question:** How would you improve a product you use every day for a new market? - **Response:** The candidate picked a segment first, sized it, and compared three options before choosing one and its success metric. The same question-and-response pair appears three times in the supplied text. ### Interview tips Practice out loud with a timer, keep a framework ready for every round, and ask the recruiter what each interviewer focuses on so you can tailor examples. ### Company culture The candidate described interviewers as collaborative and said they kept nudging toward the user. The team appeared to value structured thinking over polish, and everyone left time for questions at the end. ## Membership and contributions The full experience is gated with an invitation to unlock **1.8k+ interview experiences**, including the rest of this interview and new experiences added weekly. [Become a member](https://www.aced.io/upgrade?src=experience). You can also [share your experience](https://www.aced.io/questions/contribute?src=experience); a 24-hour trial starts once a submission is approved. ## More Snowflake interview experiences - [Software Engineer — Snowflake · Jul 2026](https://www.aced.io/experiences/snowflake-software-engineer-interview-d62928?returnPath=%2Fguides%2Fsnowflake-software-engineer-interview%2Fexperiences): “Fairly straightforward process. Why did you leave your last job? Are you interested in this role? That kind of thing. Just double-checking fit.” **1 round, 1 question.** - [Software Engineer — Snowflake · Jun 2025](https://www.aced.io/experiences/snowflake-software-engineer-interview-6d9e0f?returnPath=%2Fguides%2Fsnowflake-software-engineer-interview%2Fexperiences): “The question was a little harder than others. I didn't prep at all so didn't perform the best but it's just slightly harder leetcode.” **2 rounds, 1 question.** - [Software Engineer — Snowflake · Mar 2024](https://www.aced.io/experiences/snowflake-senior-software-engineer-interview-72abf5?returnPath=%2Fguides%2Fsnowflake-software-engineer-interview%2Fexperiences): “It was a very typical FAANG interview style. The coding questions are all very leet-code, so it's easy to practice. The design question was unique; I hadn't heard of it before. Not that not all engineers use a question from the internal question bank, but generally speaking it's fine. For system design, be sure to bank-of-envelope to justify why something needs to be a distributed system. Your approach might be overkill / underkill without doing this initial analysis, and you might come off as \"just regurgitation sys-design interview formula\".” **2 rounds, 2 questions.** [See all 4 Snowflake Software Engineer interview experiences →](https://www.aced.io/guides/snowflake-software-engineer-interview/experiences) ## Aced resources We provide preparation resources for Product Management, Forward Deployed Engineering, Engineering Management, Software Engineering, System Design, Data Science, Machine Learning, Data Engineering, AI Engineering, Investment Banking, Generative AI, Security Engineering, TPM, Solutions Architecture, UX/Product Design, and BizOps & Strategy. We also provide interview questions, practice, coaching, resume review, salary negotiation, job referrals, interview guides, interview experiences, and related career resources. --- [Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fsnowflake-software-engineer-intern-interview-f47cfb&trace=t_679ff9ab98f3) ## Ask a follow-up about this page Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required. Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup. `GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3` [Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fsnowflake-software-engineer-intern-interview-f47cfb). Opening a form does not execute a tool.