← Back to Directory

Whatnot

Mid-sized

Screna has 19 Whatnot interview write-ups. The most reported round is the technical phone screen (12).

19 interview notes · updated Jun 2026

Whatnot·Mobile Engineer·Onsite - Product Sense / Strategy

Jun 2026
Product sense round for a Mobile Engineer role at Whatnot. The interviewer pushed hard on every idea you floated, wanting to know how you'd actually build it, how you'd measure success, and whether it'd break anything for other users. More of a live product debate than a standard interview.
  • How would you improve the Whatnot app?

“Seemed like a soft opener but it really wasn't.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

Jun 2026
Whatnot software engineer interview with four coding questions, each requiring a discussion of approach before writing any code. The pace was brutal and I finished with bugs in my output and no time to fix them.
  • Solve the core coding problem presented at the start of the interview.
  • Extend your solution to handle negative numbers in the input data.
  • Third coding question in the sequence.
  • Fourth and final coding question in the sequence.

“Had to walk through my approach out loud before touching the keyboard, which I wasn't expecting.”

View Post

Whatnot·Machine Learning Engineer·Hiring Manager Screen

Jun 2026
Thirty-minute behavioral chat with the hiring manager, pretty conversational. Two main topics: your background and why this team, plus a product improvement question about Whatnot specifically. Nothing too wild but the product question caught me a little flat-footed.
  • Walk me through your background and what draws you to this team and product.
  • What specific improvement would you suggest for Whatnot? Describe the user pain, your proposed change, and how you'd measure whether it worked.

“I had a version of this answer ready but it felt a bit rehearsed coming out.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

Jun 2026
Whatnot phone coding round for a Software Engineer role. One problem, 60 minutes, and I didn't finish. Got rejected.
  • Given a log of user actions with timestamps (user_id, time, action), build a summary of unique action paths across users. Output should be an indented tree where each node shows the action name and the count of distinct users who followed that path up to that point. Logs may arrive out of order.

“I knew immediately it was a Trie problem.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

Jun 2026
Whatnot software engineer interview with a trie-based log processing problem. The interviewer pushed toward an optimized single-pass solution after I got the naive version working, which I wasn't fully expecting.
  • Given a list of log records in the form [user_id, timestamp, action], reconstruct each user's chronological action sequence, then aggregate all users' 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 first version working fine.”

View Post

Whatnot·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at Whatnot for a software engineer role. Pretty standard stuff, though the follow-ups pushed a bit deeper than I expected.
  • Design a platform similar to LeetCode, including its core features and architecture.
  • How do signed URLs work, and when would you use them?
  • How would you scale the platform to support live competitions with many concurrent users?

“Classic question and I knew it going in.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

May 2026
Whatnot SWE technical screen, one question the whole time, pretty focused on string/text processing with a trie twist. Not the hardest thing I've done but the complexity discussion at the end caught me a little off guard.
  • Given an array of messages and a list of multi-word unsafe phrases, filter out any message whose text contains one of those phrases as a contiguous word sequence. Tokenize the text first so punctuation doesn't break matching, then use a Trie built from the phrase tokens to scan each message. Walk through the implementation and discuss time and space complexity.

“The trie part I had down, built it from each phrase's token list no problem.”

View Post

Whatnot·Software Engineer·Technical Phone Screen

May 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 remain. Return the final string.

“Classic stack problem.”

View Post

Whatnot·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Whatnot for a software engineer role. Just one question, but it was a meaty one.
  • Design a platform like LeetCode from scratch.

“This is one of those questions that sounds scoped but really isn't.”

View Post

Whatnot·Mobile Engineer·Technical Phone Screen

May 2026
Screening round for a mobile engineer role at Whatnot. The recruiter sent a prep doc ahead of time saying to expect a small game app buildable in 45 minutes, so at least there were no surprises on format.
  • Build a small game app (such as Tic Tac Toe) within 45 minutes.

“They told you upfront it would be something like this, so you really have no excuse not to prep a few of these.”

View Post

Whatnot interview guides by role

14 notes

Whatnot Software Engineer interview questions