← Back to Directory

Whatnot interview notes, page 2 of 4

Mid-sized

Most of these Whatnot write-ups come from Software Engineers (25), then Machine Learning Engineers (3) and Mobile Engineers (3). The most reported rounds are the technical phone screen (20), the system design round (7), the product sense round (3) and the hiring manager screen (1).

32 interview notes · updated Sep 2026

Whatnot·Software Engineer·Technical Phone Screen

May 2026
Whatnot software engineer interview with a trie/prefix-tree coding problem that looks straightforward until you actually read the edge cases. The problem is dressed up as a product analytics thing but it's really just careful tree construction plus sorting logic.
  • Given a list of user action logs as (user_id, timestamp, action) tuples, implement a function that builds a trie-like prefix tree of user journeys and returns it as a formatted multiline string. Each node should show the action and how many distinct users passed through that prefix. Children should be printed in insertion order, users processed in ascending ID order, and ties in timestamp should preserve original input order.

“Took me a bit to realize the ordering rules were doing a lot of work here.”

View Post

Whatnot·Software Engineer·Onsite - System Design / Architecture

May 2026
Did a system design round for a Software Engineer role at Whatnot and it did not go well. The question started broad enough that I felt okay, but then it got into territory I just wasn't ready for and I kind of fell apart.
  • Design a platform similar to LeetCode, including core features and a contest/competition mode.
  • How would you handle executing code submitted by users on your platform?
  • What database would you choose for this system and what factors influenced that decision?

“The high-level stuff was fine.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

May 2026
Did a coding round for a Software Engineer role at Whatnot. First question was a LeetCode problem involving encoded numbers, solved it pretty fast and moved on.
  • Solve a number encoding/decoding problem (standard LeetCode style).

“Recognized it immediately and just coded it up.”

View Post

Whatnot·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Whatnot for a software engineer role. The question centered on building a charity donation platform with third-party payment integration, and the interviewer kept steering the conversation back toward async processing and message queues specifically.
  • Design a charity donation website that integrates with a third-party payment vendor to process donations. Focus on how you'd handle asynchronous processing and message queues.

“I started with the usual stuff, API gateway, service breakdown, how you'd call out to the payment vendor.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

Jun 2026
Did a coding round for a Software Engineer role at Whatnot. Just the one question, stack-based string problem, nothing too wild but worth knowing cold.
  • Given a string, repeatedly remove adjacent duplicate characters until no more adjacent duplicates exist. Return the final string.

“Classic stack problem once you see it, but I fumbled around for a minute trying to think of a simulation approach before the stack click happened.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

Jun 2026
Whatnot software engineer interview had a follow-up coding question pulled from a LeetCode problem tagged to the company, though not a recent one. Lesson learned: cast a wider net when prepping, not just the last 90 days of company tags.
  • Solve a number encoding/decoding problem (a known LeetCode problem tagged to the company).

“It was a follow-up, so I was already a bit drained from whatever came before.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

Jun 2026
Whatnot software engineer screen, two-part coding problem on dot products. Part one was straightforward, part two pushed into sparse vector territory which is where things got more interesting. No behavioral stuff, just the problem.
  • Implement a function that computes the dot product of two equal-length integer arrays.
  • Now assume the vectors are very long but mostly zeros. Represent them as sorted lists of (index, value) pairs and compute the dot product efficiently without iterating over the full length.

“Pretty easy warmup.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

Jun 2026
Whatnot phone coding round for a software engineer role, 60 minutes, one problem the whole time. I understood the concept well enough but couldn't finish the implementation and got rejected.
  • Given a log of user actions with timestamps (user_id, time, action), build a summary of unique action paths and how many distinct users followed each path. Output as an indented tree. Logs may arrive out of order.

“I knew the shape of the solution pretty fast: group by user, sort by time, build a trie, DFS print with indentation.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

Jun 2026
Whatnot software engineering interview that was basically one meaty coding problem about tries and user journey reconstruction. The interviewer pushed for an optimized single-pass solution after I got the naive version working, which I did not fully see coming.
  • Given a list of log records in the form [user_id, timestamp, action], reconstruct each user's chronological action sequence and insert all sequences into a shared trie where each node's count reflects how many users passed through that prefix. Return the trie with counts.

“Got the basic approach pretty quick: group actions by user, sort by timestamp, walk each user's sequence and insert into a trie while incrementing counts.”

View Post

Whatnot·Mobile Engineer·Technical Phone Screen

Jun 2026
Screening round for a mobile engineer role at Whatnot. The recruiter sends a prep doc ahead of time that basically tells you to expect a small game app you can finish in 45 minutes, so there's not much mystery about what's coming.
  • Build a functional Tic Tac Toe game app within 45 minutes.

“The recruiter doc actually names the possible prompts, so you can prep specific games beforehand.”

View Post