I was first reached out to by a recruiter by email. They told me the process was to interview first and then get to know the teams. So I had no real insight as to what team/role I was interviewing for. I think this is the only real negative I felt with the interview process. It's a pretty typical interview process with an initial code screen and then a power day consisting of 4 rounds. The code screen was done through code signal. I took a week to familiarize myself with code signal and they have a new practice test you can do everyday for free. Power day was 4 rounds that are one hour each, you usually don't use the whole hour and are left with time for questions. The interview process is very blind, it's senior level managers interviewing you and they weren't in the same location or department I was interviewing for. So I really didn't get to meet my team or hiring manager until after I passed the interview. The rounds are system design, coding question, case interview, and behavioral. I think case is the only type of interview I haven't come across before. It's more about thinking from the business point of view. Like if we add xyz feature how does it help the company and the consumer? This was the hardest round for me. It was half business logic questions and half reading code and suggesting improvements. For the coding question they use hacker rank as an ide, so you're not going to have to pass test cases or anything. They gave me a hard coded input and told me to print the solution. They only asked me how I'd handle certain edge cases, but I didn't have to implement. I took 2 weeks to review common leet code questions. Overall I think it was a good interview process, but I just really wish I knew the role before interviewing. I was hoping for a full stack role, but they only had one backend role at my location. The recruiter made it sound like I would have a choice between what team I was part of, but I was only really given one team.