A recruiter reached out to me and scheduled a live coding interview. The interview started with some behavioral questions, asking about a specific project and coding journey. The coding question was a string question, which was mentioned in several of the other reviews. They also don't require you to speak, which was different from other coding interviews I've participated in. I did make sure to add a lot of comments and outline my thinking. After passing the coding interview, I was moved on to the next round which consisted of four 30-minute sections (with 5 minutes in between) speaking with various organization members such as a recruiter, an engineer, and managers. These were primarily behavioral in nature, and the questions were straightforward and most interviews felt conversational. One of the 30-minute sections was a case study, where you design a website and illustrate what kinds of tables and schema you would implement for said website. Unfortunately, I did not move on to the final round which was mentioned to be with the executive team, but everyone was so kind and easygoing throughout the whole process.

The first step is to finish an OA that includes a mid coding about string and I use sliding window to solve, it may have something else but I can't remember. And a month later, there was a coding interview that has the same question as the other recent post. And the interview stated at first that you don't need to share your thought about the solution and just do the coding

While submitting an application, there is an option for you to 'speed' up the interview process by taking an OA on Codility lasting 70 minutes. The OA consists of 3 sections: multiple choice questions, an SQL query question, and a normal algo/ds style question. The OA overall wasn't difficult and was able to complete every question. It wasn't until a month later that I got an email to schedule an online interview. The interview consisted of some behavioral questions, followed by a 25 minute algo/ds question. Only difference is that you're coding in silence, as the interviewer doesn't expect you to communicate as you're coding. The question given was easy and straightforward in theory, but I just whiffed and was unable to get very far in solving it. I would like to believe that you're not meant to solve it within the given time, but as long as you're on the right track or just a genius it will probably be good.