One senior engineer and an engineering manger appeared for the interview. They shared me a link for a live codility question. The question was easy but the solution to it was complex especially when you have to implment it using Java technology alone.

The process consisted of 4 interviews First it was a screening with HR. Simple and classic questions. Where are you currently working ? Why do you want to join us ? Do you know the company ? What are you willing to do in your next job? And more. If you succeed, they'll send you a codility test with 3 exercises. One is easy and the other two are medium. Not too hard, but no too easy as well. After the codility test there's a call with two developers. They'll present you a simple exercise and start debating about it. There's not a right answer here. They're trying to test if you make questions, if you can assume other stuff. They'll ask questions about the exercise and about the code. Like, "What is the difference between Integer and int", "What are the different types of exceptions and subtypes?" (checked vs unchecked) "Would you prefer Optional values over exceptions for handling certain type of things?" The algorithm to design was "return the two biggest elements in an array" Finally there's a system design interview. They present you a solution and they expect you to discuss about it. They want you to talk if it's necessary to have a queue and which would fit if that's the case. Difference between commands and events. Sync and async. In my case the idea was a system that gave a flower to each new subscriptor because they wanted to promote the app. A simple design was presented to my and I had to talk about pros/cons and what would I do different if needed and why