Snowflake·Frontend Engineer·Technical Phone Screen
- Implement an EventEmitter class with on, off, emit, and once methods supporting a standard pub/sub interface.
“The basic structure came to me quickly.”
Large Enterprises
Most of these Snowflake write-ups come from Software Engineers (118), then Data Scientists (12) and Backend Engineers (2). The most reported rounds are the technical phone screen (91), the system design round (30), the behavioral / leadership round (5) and the online assessment (2).
135 interview notes · updated Oct 2026
“The basic structure came to me quickly.”
“This question is basically asking you to do a full systems design course in 45 minutes.”
“My first instinct was to sort by revenue and just pick the highest one, which is wrong.”
“My first instinct was to do a preorder traversal but then I realized I needed the subtree sums, which means you actually want to compute bottom-up, so postorder made more sense.”
“I jumped straight to DFS and felt pretty good about it, but then realized mid-explanation I wasn't handling the case where X is the root cleanly.”
“BFS was the right call and I knew it pretty quickly.”
“The promotion logic is where I got tangled.”
“Came up in the early screening rounds.”
“I got the basic traversal down fast enough, topological sort and merge sets as you go.”
“Started fine with the basic version, stack-based, push on open and pop and check on close.”