There were 2 phone screens and a 9 am to 5pm onsite. Every round is a knockout round.

First phone screen is half manager's talk about the company and team and half coding exercise on an online code editor and compiler. Second screen again bunch of distributed system related questions and coding again on interviewer's choice of shared editor. This would seem like a question answer session. I think no of wrong answers would decide the result.

Onsite is initially very relaxing and picks up some speed in afternoon. Be careful to not make minor mistakes because those matter a lot. Non-coding interviews are more of a discussion but do require white-boarding but again beware of wrong answers in between the discussion. Even just one or two could cause rejection.

Coding interviews are not that hard in terms of difficulty (I found one of those difficult and had some hard time) but again try not to be in pressure and make minor mistakes. Code is compiled and run on a given dataset.

Won't be specific but related to data structures like linked list, tree and sub strings of a string.