First I had a phone screen. They switched out the interviewer last minute but the engineer who interviewed me was very easy to talk so that made me comfortable during the interview. The question was string manipulation, pretty straight forward but required some thought about corner cases. I got to a working solution and was invited onsite. Onsite was an afternoon with 5 different interviews. The first one was a coding challenge. It started late, the interviewer was remote and that made it harder to communicate with him. He could only see part of the board and I wasn't even sure he could see the board that well. The question had a lot of overhead to it so I felt really rushed throughout the interview because we only had 25 minutes by that point. I discussed the solution with my interviewer on the partially visible white board first and then tried to code it as fast as I could. I think I got to an acceptable solution. The second interview was an API design. Again I think the interviewer and I spent too much time chit chatting before the question but besides that I think I didn't do a great job. I should have just laid out a very simple API first and then iterate from there depending on the interviewer's feedback. I got stuck trying to make the most perfect API calls right off the bat and that didn't help, I kept going back and forth. The third interview was mainly talking about my background. The interviewer had read my resume and just wanted me to explain different things I worked on. I thought it was enjoyable and I think I did pretty well there. The fourth interview was with the VP of engineering. We started talking a bit about my experience, I asked him some questions about his role and then he gave me the broadest question possible. He drew a client and a server on the white board, said 'imagine this is a user on a web browser talking to a server with a login page, describe what happens'. I asked him what aspect he wanted me to talk about, which layer I should delve into and he said 'pick one'. I started with the application layer, then talked a little bit about networking, talked about security ( symmetric and asymmetric encryption ) as well as the database schema. He never said anything, he would only nod and say "sounds good" or "okay". He asked me to describe a possible select query on the db, I did and that was it. It was hard to understand if I was being too broad, if he wanted more details, or if he wanted to see my understanding of the bigger picture. Coding questions can be done with an unresponsive interviewer but open ended questions need a back and forth. My last interview should have been with the CTO but the VP told me the CTO was busy and sent me home. I guess they had made up their minds by then. I felt like I had done okay but I guess I was mistaken. When the recruiter sent me an email telling me I was not getting an offer I asked for feedback to understand what I could have done better but never heard back.