WHOOP logo

WHOOP Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 21 interview experiences · FREE TO READ

2.3 Rounds average
Average Typical difficulty
66.7% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at WHOOP.

Showing 3 of 21
WHOOP logo
WHOOP

Software Engineer

Engineering · nearly a year ago

Entry Easy Positive experience No offer 1 round
Interview process
Recruiter call
Interview formats
Behavioral

HR reached out via email to schedule a call. They asked about my previous experience, my tech stack, whether I'm open to hybrid work, my visa status, and my desired salary. It was a pretty straightforward initial HR screening.

Confirmed questions6 questions
  • Could you describe your tech stack?
  • What kind of tech stack do you have?
  • Can you tell me about your past experience?
WHOOP logo
WHOOP

Software Engineer

Engineering

Senior Average Neutral experience No offer 4 rounds
Interview process
Technical screen Technical screen Technical screen Background check
Interview formats
Coding System Design Technical Behavioral

The interview process was mostly smooth with polite interviewers. There were four rounds: Coding/Pseudocode, System Design, Refactoring Legacy Code, and a Behavioral Interview. I felt the evaluation followed a strict pattern, negatively impacting candidates whose answers deviated. For instance, in system design, alternative valid solutions weren't well-received if they differed from the expected approach. Sometimes, junior engineers led discussions with senior candidates, making it feel less collaborative. There was a strong focus on minor details like datatype mismatches or missing validations, overshadowing problem-solving and modern practices. In today's AI era, more emphasis could be placed on architectural thinking, design trade-offs, and engineering judgment. The system design round, in particular, heavily favored one solution, limiting exploration of other reasonable designs. While organized and professional, the evaluation criteria seemed rigid and based on a predefined script rather than encouraging broad technical discussion. I hope they consider the overall picture and don't reject candidates for minor issues, as my recruiter feedback indicated rejection due to these minor things I didn't catch.

Confirmed questions3 questions
  • Tell me about your background and experience.
  • Can you discuss questions related to short URLs?
  • What are your thoughts on social media in relation to this role?
WHOOP logo
WHOOP

Software Engineer

Engineering

Mid Difficult Neutral experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Panel
Interview formats
Behavioral Technical Coding

I think there's a lot of good things here but some of the people just seem off. I really like that they don't rely on leetcode at all. In my initial screening with the recruiter, I asked her what her favorite aspect of working at WHOOP was, and she literally said "It's inclusive, it's mission driven, and easy to get involved." That's it....it sounds like she doesn't like it there haha. Literally reading off the website. After the screening I had an initial call with a hiring manager where I drew up a high level diagram of one of my work projects, and answered follow up questions. I enjoyed this round the most. After that there was a code session where I was given a lot of Python code, and worked with the interviewers to refactor it. One of the interviewers didn't even talk and seemed to be doing something else the whole hour. And the other interviewer was alright, not mean but not very nice either. I didn't make it past this round, but there was a 3 hour panel to be had after if I did. This seems like an interesting company to work for in terms of technical growth but I didn't get the vibe that they assessed for cultural fit at all.

Confirmed questions1 question
  • What would be the impact on the production application if this schema change was implemented?

WHOOP Software Engineer Interview Questions

Quoted word for word from WHOOP interview reports.

Could you provide a recursive solution for the Fibonacci sequence?

Read reports

What about a recursive solution for the Fibonacci sequence with a twist?

Read reports

What would be the impact on the production application if this schema change was implemented?

Read report

Could you create a basic React component that fetches and displays a list of items from an API?

Read report

Can you explain the differences between two-way and one-way data binding?

Read report

Could you design a Tiny URL service? You can use chapter 8 of the book System Design Interview as a reference.

Read report

Formats, difficulty and experience

Across all 21 WHOOP interview reports.

Interview formats

Technical 37.5%
Behavioral 31.2%
Coding 18.8%
System Design 12.5%

Interview difficulty

Easy 23.8%
Average 61.9%
Difficult 14.3%

Candidate experience

Neutral 19%
Positive 66.7%
Negative 14.3%