I started with a DSA-style pre-screen that felt very structured, similar to a HireVue/Karat flow. I answered a set of coding prompts, then I had a recruiter call right after. That recruiter conversation set the stage for what came next, and it led into two more technical DSA rounds with engineers from Whatnot. Each of those technical sessions had just a couple of problems, and the interviewers dug into how I was thinking rather than only whether I got to the right output.
The overall process felt pretty smooth and communicative. People were willing to be flexible with scheduling across the multiple rounds, and the vibe was professional and organized. I also remember that the process gave me a clear sense of what topics to focus on ahead of time.
5 months ago
Average Positive United States
I had a LeetCode-style round with an engineer that lasted an hour. The interviewer was present but very quiet while I was solving, which changed the whole feel of the session—there wasn’t much back-and-forth or verbal guidance.
It made the time feel more isolated than I expected, and I ended up not moving forward. The biggest thing I remember was the unusual silence, which put more pressure on me to drive the problem-solving process on my own.
5 months ago
Easy Positive United States
I got pulled into a pretty short, one-way video interview format. The setup was straightforward: there were a handful of questions, and I had to answe…
5 months ago
Difficult Positive United States
My timeline started with a HireVue-style interview, and after that I moved into a Karat technical interview. The technical portion had a sweep from ea…
6 months ago
Average Positive Dublin, Dublin
My interview loop had four rounds, and the structure stayed pretty standard from start to finish. I had a technical screen where the focus was on core…
Unlock every Software Engineer interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
What to expect
Distilled from the reports
Interview Structure & Timeline
The interview process typically starts with a recruiter screen, followed by a series of technical interviews, including coding, system design, and product sense discussions. Candidates noted that the timeline was often clear and organized, though some experienced a lack of communication about next steps.
Candidates faced multiple coding rounds, often structured around LeetCode-style problems, with a focus on both problem-solving and communication. Interviewers sometimes varied in their engagement level, affecting the overall experience and pressure felt by candidates.
LeetCodeProblem-solvingEngagement
System Design & Product Sense
System design interviews were a significant component, requiring candidates to articulate functional and non-functional requirements, while product sense discussions emphasized collaborative dialogue. Some candidates found these rounds challenging due to unclear expectations or feedback.
System designProduct senseCollaboration
Behavioral & Values Assessment
Initial stages often included behavioral interviews focusing on candidates' experiences and motivations, with some candidates feeling these rounds were less structured and lacked depth. The emphasis on company fit was notable, particularly in discussions about Why Whatnot.
BehavioralCompany fitMotivation
Interview Difficulty & Pressure
Candidates reported a high level of difficulty across rounds, with some feeling intense pressure due to the structured format and time constraints, particularly in one-way video interviews. This pressure sometimes affected performance and overall confidence.
High difficultyPressureTime constraints
Feedback & Outcome Clarity
Many candidates expressed frustration over a lack of clear feedback regarding their performance and the reasons for rejection, especially after seemingly positive interactions. This ambiguity contributed to a sense of unfairness in the evaluation process.