I have to give thumbs down to their interview process. I went through initial interview with HR, then talk with Engineering manager about some system design questions, then I did 1hr online test with Karat (30 min leetcode + 30 min API design) and then finally had a call with staff engineer from the team I was supposed to join. Since I went through several technical rounds and felt pretty comfortable that I did really good in all of the them I specifically asked at the end of the call with staff engineer if it's a "yes" from his side (since it was a last technical round) and he said it's a yes from him. So naturally after passing all the rounds and getting a "yes" from staff engineer you'd highly expect to get an offer or a rejection with some feedback but no ... I got an e-mail that they chose another candidate and after asking for feedback I was informed that they don't provide it.

Overall I don't recommended it since the time commitment is too much. There are too many stages for what is being offered and don't be surprised if you are asked for extra stages. With the amount of stages, it's very likely that you will need take considerable amounts of time during your workday, or even take time off fully to interview with them. Like the other interviewees have said, it's not really worth it unless their interview process has changed. Otherwise, you are better off (in my opinion) spending your time doing the following: Interviewing elsewhere, working, doing your school work/independent study, or even spending time with family/friends. This is just my honest opinion. Here is a breakdown of the interview process: A multistage interview that follows this general guideline: first stages: consists of general knowledge, frameworks, java, kafka, maybe databases, and some architecture. They may ask you why you want to work with them. Nothing unexpected. Middle stages: Take home project and presentation about it. These should be among the last stages. Final stages: If all goes well, you should be extended an offer.