The power day was 4 hours. Most of the interviewers were friendly except that last one. His connection would drop, so it was difficult to communicate. Not only that, I ask him questions, and was very passive aggressive with his answers. Did not help towards a solution or guidance, and was probably the reason I got rejected even though I passed previous 3 rounds. This was honestly a waste of my time if I knew it was unto one person to decide to pass or fail me. 4 hours wasted because of this person. Do not waste time interviewing at a bottom tier companies, they love wasting time. Use that time instead to study for interviewing at competent companies.

The interview was fairly straight forward. It started off with a recruiter screening making sure you're qualified for the position, and then they send you a 'codesignal' which is just a hackerrank that you need to record yourself taking. The codesignal was 1 easy and 3 mediums, but you don't need to pass every question to move on. I only fully passed 1 question, missed a single test case on another, type 1 line of code for the third, and passed the fourth question, but got time limit exceeded on some of the test cases. 1 easy and 3 mediums is a lot to do in an hour, so I think they use the test to gauge your overall competency rather than if you can find all the optimal solutions. Once you pass, you move onto their power day. It's two tech screenings(one systems design, one leetcode styled), a behavioral, and a case. Study up on high level systems design and topics like nosql, cloud hosting, caching, and creating scalable systems. If you know basics of systems design that interview shouldn't be a problem. For the leetcode portion, I got asked two easys. If you are able to pass the codesignal they send you, you should have no issues passing the tech screening. Make sure you do your research on how to approach whiteboading styled interviews though, as I think they are looking for communication rather than a good solution. The behavioral interview is incredible standard and there were no curve balls thrown. Just study up on common SWE behavioral questions and you'll be good to go. Be prepared to answer follow up questions on the answers you give, so if you're lying be sure you're a good liar as you might get caught in your lie. The final interview was the case. The case is a bit strange. It starts off by asking you about the use case of a feature they want to implement, and you spend 10 or so minutes going over the pros and the cons of the feature. Then you're given code and you need to figure out what the code is doing, then refactor it to make it work like how the interviewer wants it to work. This isn't really an interview you can study for, but if you have experience coding then you shouldn't struggle with this portion. I hit a bit of a snag because my interviewer wanted my code to look a certain way, and I couldn't see his vision, but I still had the proper solution. Be prepared with questions at the end of the interview as they usually leave 10-15 minutes after each interview for you to ask. Are they going to judge you if you don't ask any questions? Probably. Just be friendly, dress nice, and be confident and you shouldn't have any issues with the interview process.