It was a code problem for 45 minutes, followed by 4 45 minute interviews over 3 hours with various members of the team. I think there was a 3rd round with the CTO, but I didn't get that far. The code interview was only challenging because there was a lot to do, but it wasn't "tricky." The interviewer was nice and put me through to the next round. The first 2 parts of the 4 round interviews were fine. Recruiter and a developer on the team. The 3rd round was with a manager, and he was not a good interviewer. Very stiff, it felt like he was reading his questions from a "how to interview people" textbook. The final round was a design challenge. It was chaotic. The scope of the question was too big to have been completed in the allotted time, and I wasn't sure what they wanted, they kept going in different directions. I heard them say enough strange stuff during the interview process that I was questioning if I would accept an offer if I got one - luckily, they rejected me first. I think it could be a good fit for someone earlier in their career, just not for me. If you are looking to interview here, look through the glassdoor interviews page, a lot of the questions that they asked were literally right off of here. And, I guess, pray to make it through the design portion.

- Recruiter/HR prep talk - initial leetcode round - second round with 4-5 different people, mostly seeing if you're a good fit personality-wise. the last one would be dbms database design like others have mentioned. nothing special if you've done it often enough.

Three separate rounds, with a technical exercise as part of each of the first two rounds. After a single interview in round 1, you'll meet with multiple people (back to back) in rounds 2 and 3.