Had four rounds of interviews; three rounds focused on design, and another round was on coding. For the design problems, it looks like they have a predefined set of problems and predefined solutions. These design questions are mostly open-ended, with huge scope, and you could be rejected for any corner cases not addressed (in fact, you would not know what corner cases they refer to in the feedback) or for not coming up with the number of microservices they have in mind. I feel such wide scope covering design questions could mislead the candidate's focus in many areas (and the interviewer should not have a fixed opinion on the best design).

The coding round was mostly on paper, looking for complete, working code on paper. I could not figure out the expectation from this round even after writing the code.

Design a recurring payment system used by vendors with flexible schedules. This is a one-page document with history, and you can design a whole multitenant system around this.

Design a phone contact system with web and app support for various use cases.

Java asynchronous message handling.

Design the Book My Show system. Note: here the panel is confused between authorization vs. communication protocols.