WHOOP Interview Questions
& Process

So I had this HR call first, and they went through my resume, asked about my background and why I wanted to join WHOOP. Then I talked to the hiring manager, which was a more in-depth resume review. Luckily, my past work fit really well with what they do, so they invited me for an onsite. The onsite had three parts. First was with a senior embedded engineer, and it was all about system design and hypothetical scenarios, no coding. They hit me with a question about managing data on a wearable if a user is offline for a week - storage and timestamp syncing were key. Next up was an electrical engineer who focused on communication protocols. The last round was with a manager, and it was purely behavioral. Didn't make it past that point, unfortunately, because my experience wasn't quite cutting it for some of the technical stuff they asked.

This was a multi-stage interview process that felt pretty standard. The team was nice, but I didn't end up getting an offer. They mentioned a Security Engineering position that might be a better fit. About three months later, a senior recruiter reached out about that specific role. Since it was a different recruiter, I let them know about our prior conversation and asked if this was a follow-up. They never responded, which was disappointing. It's basic courtesy to reply when someone engages with you about a job, even if they aren't the right candidate.

The first round was a mix of behavioral and technical questions with a manager, and it felt really well-structured. After that, I had to do a take-home assignment, which isn't my favorite, but I put a lot of effort into it because Whoop was a top choice. I explained everything clearly in my code, even though the problems were new to me. I guess they got a good sense of my skills from that. The final round was with the hiring manager. I was expecting more behavioral and advanced signal processing questions, but instead, they asked really basic technical questions, like defining an eigenvalue. It was confusing and disappointing because I thought the questions should align more with my resume and PhD work. I was expecting questions about different filters or the DFT/DTFT, not their definitions. I ended up getting rejected a day later. While I don't feel disrespected, it felt like a waste of my time.

So, I interviewed with Whoop and it was a long and tough process. I put a lot of effort into showing them I was a good fit, but I never got any feedback. It's really important to get feedback to grow, and it helps you know what to work on. Not getting any feedback makes it hard to know where you stand. I get that they have to make decisions, but not giving feedback after someone puts in so much time just doesn't seem right, especially when they talk about being transparent and helping people grow. Companies should help candidates, not just find the right person. I think Whoop should start giving feedback to everyone, no matter what. It helps people grow and shows the company cares about talent and making people feel good about interviewing there.