I had a first interview with the engineering lead, followed by a technical interview where they essentially repeated the same questions about who I am and discussed trivial things, only to give me the last 15 minutes to solve a Java exercise. The exercises were easy LeetCode-level problems, but 15 minutes is not enough time to finish. I managed to come up with a partial solution and explain the Big O N complexity, and they allowed me to move on to the next round. the next round is aanother 4 interviews : 2 technical, one with the manager and other cultural fit (so like 6 interviews in total for the full process).
The interview with the manager went well. He asked questions related to my current job, the technologies I use, how I approach problems, and solutions I've implemented (the kinds of questions that should be asked to an engineer). Then, the second coding interview was almost exactly the same as the first one. The first half hour was spent asking the usual questions that don’t really add much value, leaving only about 20 minutes to solve a problem in Java. The task was to create a simple LinkedList class and merge two sorted lists in order. I went with recursion, and in the end, there was a small error, so the solution wasn’t perfect, but the approach was right. That small mistake led to me being immediately rejected, and I wasn’t able to proceed with the remaining interviews.
Overall, they are looking for programmers who can do LeetCode exercises rather than software engineers,