Initial interview from recruiter to gauge interest, tell you more about the role, and to figure out if you are a potential fit. Then 4 part technical interview... First 2 parts were leet code style questions. Third part was a behavioral interview, but I was asked a leet code style question during it. Fourth was a system design interview. *For all the interviews you need to answer questions about your past experiences and ask questions about Qualtrics. Also Qualtrics gives good resources before the interview that you should fully look over.

There were 2 interviews, 2, 1:30 minute coding challenges, and one of the interviews was an "Architecture interview". The phone screening before the actual 1st interview and the 1st culture interview were a breeze. The coding problems were medium difficulty, but they wanted you to be able to write down the Time and Space Complexity of your solutions. The architecture interview was without a doubt, the worst interview I have ever done. My interview was being done by someone who was clearly inexperienced in people management and interviews, and was being shadowed by a more senior HR person in what they called 'Reverse shadowing.' The problem statement given was simple, architect a rate limiting system. This was the first time I had ever been interviewed in this matter, so I attempted to approach the problem by gaining as much insight into 'how' the system should work, what kind of scale should it have, is the system cost sensitive, and can I use existing tools, or do I need to be as agnostic as possible, giving Psudo Code answers. Well my attempt to understand what questions the junior interviewer was asking about were met with exasperation and frustration directed at me. My attempts to further clarify what the problem led too further enrage the junior interviewer while the senior interviewer sat in total silence, as I'm being borderline yelled at for not understanding how to give a different answer on how I would architect this silly little spur of the moment system... And attempting to draw diagrams with my mouse and speak at the same time only made the system worse. By 25 minutes in it was obvious I would not be getting the job given how frustrated the junior but lead interviewer was, so I thought about just calling it off. I persisted for the remainder of the hour, only managing to slightly understand the goal of the interview. I considered asking for another interview with someone more experienced, given how well the first few had went, but I decided against it if this was how potential talent was treated.