2026 Whatnot SWE Interviews: 6 Experiences

Six public Whatnot interview reports from 2026, with new-grad, intern, and senior experiences kept separate.

Coverage: Three new-grad reports, one SWE intern report, and two senior reports published from March to October 2026. The senior roles were in Seattle and San Francisco. The October update concerns the 2027 new-grad intake.

This is a roundup of other candidates' accounts, not one person's interview story. Dates below are publication dates unless an interview month is stated. The October 2026 date on this post is the roundup's cutoff month, not the date of every interview.

The short version

The March posts give the clearest new-grad question details. October’s new-grad update is mainly about the next step.

1. Start with the new-grad reports. Two March candidates described a recorded video step followed by Karat. Their later progress differed.
2. The exact questions are a short list. The new-grad posts named text justification and a grid row-and-column check. They did not share full problem statements.
3. Leave room for follow-ups. One senior candidate reported three coding questions and three follow-ups in 50 minutes. That is one account, not a timing rule for every role.
4. Check which hiring track a report describes. One intern reached two rounds with Whatnot engineers after Karat.
5. A recent post may still be an early update. The October new-grad applicant had finished Hireflix and later received another interview invitation. They had not posted a full technical-loop recap.

A useful prep order: Get comfortable with live coding, practice the disclosed questions, then prepare for the rounds listed in your own invitation.

Recorded video and first screens

Screen 01: Getting through the first steps

The March new-grad candidates completed recorded interviews before Karat. One described basic behavioral questions. October’s applicant named Hireflix; the March posts used HireVue-style wording. Check the platform in your invitation.

Live interview question bank

These are the tasks the posts actually identify. The linked practice versions add input formats, examples, and rules where the original accounts were brief.

New-grad coding

1. Text justification. The March 23 candidate identified a task like Text Justification, but gave no formatting rules or sample input.
2. Check the rows and columns of an n × n grid. The March 1 report described a Sudoku-like validation task. It mentioned rows and columns, without stating a separate sub-box rule.

Senior fullstack coding and React

One Seattle candidate reported these three tasks:

1. A palindrome check with one deletion allowed.
2. Merging squared values from two sorted arrays.
3. Build a React page with two tabs and a list in each. Load both lists from a network request. Add follow and unfollow for each item. The post did not give the API format or persistence rules.

6 detailed candidate timelines, loops, and screens

01: New grad — stopped after Karat

Report date: March 1, 2026 · Role: Software Engineer, New Grad · Result: Rejected after Karat

After a recorded interview with basic behavioral questions, the candidate took Karat and was asked to check the rows and columns of an n × n grid. They thought the screen went fine, but were rejected. They never reached the Whatnot engineer rounds. The post gives no reason for the rejection.

02: New grad — text justification, with more rounds ahead

Report date: March 23, 2026 · Role: Software Engineer, New Grad · Status at posting: Still in the process

After the recorded video step, this candidate took Karat and described an easy question followed by a hard one. Text justification was the only task they identified.

Their next step was a 15-minute recruiter screen. They described a possible engineer interview after that, followed by another two problems and a behavioral round if they kept advancing. They did not know whether those later problems would be standard data-structure and algorithm questions.

03: Fall new-grad hiring — an early update for the 2027 intake

Report dates: October 2 and October 8, 2026 · Role: Software Engineer, 2027 New Grad · Status at posting: In process

By October 2, this applicant had finished Hireflix and was asking how long the next step might take. On October 8, the same person posted that they had received an interview invitation after Hireflix.

These are two updates from one application, so they count as one experience here. They confirm progress beyond the recorded interview, but do not reveal a completed coding round or any technical questions. There is no reliable full-loop timeline to take from these posts yet.

04: Intern — Karat, two engineer rounds, then an offer

Report date: May 6, 2026 · Interview month: April 2026 · Role: Software Engineer Intern · Result: Offer

The candidate described a four-week process. Karat served as the assessment round in place of a separate OA. Two data-structure and algorithm interviews with Whatnot engineers followed.

They also said the recruiters were open about what topics to study. That makes a simple question worth asking your own recruiter: what should you prepare for the next round?

The report did not name its coding problems. It helps with the sequence of rounds, not with building another question list.

05: Senior fullstack — coding, then a React build

Report date: April 8, 2026 · Role: Senior Fullstack Engineer · Location: Seattle · Result: No offer

They recommended preparing an answer to “Why Whatnot?” In coding, they were asked to check a palindrome with at most one deletion, then merge the squared values of two sorted arrays into sorted order, including negative inputs.

The candidate said the interviewer gave them a solution and stopped them trying their own approach. The React round came next. They did not receive an offer or know why.

06: Senior — a packed coding session

Report date: September 29, 2026 · Role: Senior Software Engineer · Location: San Francisco

This candidate reported three coding questions and three follow-ups in 50 minutes. They described the interviewer as nice, but felt there was too much to finish in the available time.

No question names or prompts were shared. The useful detail is the pace: in this session, the work kept going after the initial questions. It is not evidence that every Whatnot screen has six separate tasks or the same time limit.

What to prioritize from these reports

First: practice working through a live coding session

Live coding appears in the new-grad, intern, and senior accounts, although the formats differ. Practice explaining an approach, writing it, and checking it within a set time. Add a follow-up before calling the session finished.

Next: use the questions we can actually trace

The four coding tasks above are a small, useful practice set. They are not enough to predict an interview. If you are applying as a new grad, start with the two new-grad reports; the senior tasks are extra practice.

For frontend roles: include a small React build

For frontend roles, try the reported React task and ask whether a practical build is part of your loop.

Final checklist

Before the screen

☐ Read the invitation for the platform, length, and allowed setup.

☐ Prepare a clear answer to why you want the role.

☐ Ask which topics or round formats you should prepare for.

During practice

☐ Explain your plan before coding, then check it with examples.

☐ Leave time for a follow-up or a change to the requirements.

☐ Keep the role labels in mind when using someone else's experience.

Based on six independent public candidate accounts. Missing questions and outcomes have been left missing. If you interviewed recently and can add a detail or correct one, please share it.