Applied online and received a response within a week with a request for an online coding problem, which can be solved in 20 minutes.

I passed it and had a phone interview within that month. This was also not that difficult, but it did go through some basic concepts such as OOP design and principles. The coding question was straightforward as well, as long as you know how to deal with I/O, strings, and basic programming. Then I received a phone call from the recruiter the other day, and I was told the phone interview went well and the next step was onsite.

Onsite interviews were cool. There were 4 rounds, and every round was interesting. We talked much about OOP design and explored potential issues that may occur if I chose a bad design. The programming problems were not that difficult if you have practiced with enough coding interview problems. I did a bad job in the last round, where I was asked to implement functions of a self-designed data structure. I was kind of tired and did not understand the functionality until I coded it through, and of course, I made several mistakes that made my interviewer believe I "catch" things slowly.

After 2 weeks, I received a notification phone call informing me that I was rejected, with a slight disadvantage.

OOP design issues, linked list, IO, recursion, DP, and a little bit of system design discussion. Very straightforward. Most discussions are open-ended.