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 1% of the 135 Snowflake interview notes on Screna AI.

2 Backend Engineer interview notes

Snowflake·Backend Engineer·Technical Phone Screen

Jun 2026
Snowflake backend interview that leaned heavily on graph algorithms. The core problem was topological sort but they kept pushing into follow-ups that honestly caught me more off guard than the main question did.
  • Given a list of tasks with prerequisite dependencies, determine if all tasks can be completed without circular dependencies, and return a valid ordering if one exists.
  • How would you modify the approach to find the minimum number of parallel batches (semesters) needed to complete all tasks?
  • How would you produce the lexicographically smallest valid task ordering?
  • Given a dependency graph that contains exactly one cycle, how would you identify the single edge whose removal makes the graph a valid DAG?

“Kahn's algorithm, compute in-degrees, queue up the zeros, drain it.”

View Post

Snowflake·Backend Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at Snowflake for a backend role, focused entirely on building a cross-platform client logging library end to end. The interviewer kept drilling deeper on each sub-topic so it felt less like one question and more like six back-to-back. Solid round if you like infrastructure-heavy design problems.
  • How would you design the API surface for a client-side logging library, covering log levels, structured fields, and sampling?
  • Design the backend ingestion endpoint that receives log batches from clients.
  • How should the client library batch and flush logs without hurting foreground performance?
  • What happens when log volume is too high and the system can't keep up? How do you handle backpressure on both the client and server side?
  • How do you ensure that calling log() never blocks the caller, keeping it truly fire-and-forget?
  • Walk through the cross-cutting concerns for this system: schema evolution, PII scrubbing, authentication, offline behavior, and observability.

“Started with the obvious stuff, severity levels, key-value structured fields, and a trace ID.”

View Post