The interview process took pretty long, about 2 months since I interviewed during the summer when a lot of people went on vacation. After an initial phone call, I was given a 24 hr coding challenge to complete since I wasn't a computer science major. This was followed by a technical phone screen, and then an on-site. The on-site involved 3 technical questions, 1 product demo, and 1 fit/personality interview with the VP of engineering. A few weeks after the on-site I got a call from the CEO for another fit/personality type of talk and was given an offer. As this was a new-grad position, they were looking more for ability to think critically and to problem solve. Stuff like, have you thought about the limitations of the tools or technologies you're using? Are you a self-motivated learner?

Bit lengthy of a process, but I feel it's worth it for what you'll be working on, plus it's one position. First was the coding challenge, which should take 2-3 hours (use a trie). Then after I passed that, I was informed there would be 6-7 rounds till the end. The first 4 rounds, are the more technical, which because of covid, could not be onsite. Then the 5th round is more of a design question. If you get to, and pass the 5th round there's a pretty good chance you'll get an offer. The engineers who interviewed me for the first 4 rounds were talented and social enough where it felt collaborative. The questions are nothing like you'd find on leetcode verbatim except for one. It's more like things that relate to what they're doing, such as huge calculations in distributed systems, etc. They mainly want to know how you think/approach the problems. I'd describe it as a google style interview where the problems are a tad bit easier. After the 4th round, I was informed my skills did not align with them, but overall, it was a very human experience and I enjoyed it, bar not getting an offer. Just study your basic data structures, speak up and actually converse your thought process and you should get very far at least.