Snowflake Backend Engineer interview questions

2 Backend Engineers have shared notes from their Snowflake interviews, with the questions they were asked in each round. That is 3% of the 69 Snowflake interview notes on Screna AI.

2 Backend Engineer interview notes

Snowflake·Backend Engineer·Technical Phone Screen

Jun 2026
Snowflake backend interview centered almost entirely on graph problems. The core question was a topological sort variant and they kept pushing with follow-ups that got progressively trickier. Not a bad experience but I definitely underestimated how deep they'd go on a single topic.
  • Given a list of tasks labeled 0 to n-1 and prerequisite pairs indicating dependencies, can all tasks be completed without a cyclic dependency? If yes, produce a valid ordering.
  • What is the minimum number of parallel batches (or semesters) needed to complete all tasks, assuming tasks with no remaining dependencies can run simultaneously?
  • How would you modify the approach to return the lexicographically smallest valid ordering?
  • Given a directed graph that contains exactly one cycle, how would you find the single edge whose removal makes the graph a valid DAG?

“Classic topological sort.”

View Post

Snowflake·Backend Engineer·Onsite - System Design / Architecture

May 2026
Snowflake backend engineering interview focused entirely on a system design problem: build a client-side logging library for web and mobile plus the backend that ingests it. The interviewer kept drilling deeper on each layer, which I wasn't fully prepared for.
  • Design the API surface for a client-side logging library: what log levels do you expose, how do you handle structured fields, and how does sampling fit in?
  • Design the backend ingestion endpoint that the logging library sends data to.
  • How does the client library batch log entries to avoid making one HTTP request per log event?
  • What happens when log volume is too high for the system to handle? Walk through both the client-side and server-side backpressure strategies.
  • How do you ensure that calling log() never blocks the caller or impacts foreground performance?
  • How do you handle cross-cutting concerns like schema evolution, PII scrubbing, authentication, offline buffering, and observability for the logger itself?

“Started okay here.”

View Post