There were three interviews in total: two technical rounds and one final team-fit/behavioral round. The technical interviews were fairly demanding and covered both implementation and system design topics. The first focused on writing a Java in-memory load balancer with attention to validation, edge cases, and TDD. The second involved implementing a concurrent transaction operation between two bank accounts with an emphasis on avoiding deadlocks, followed by discussion of SQL locking strategies, parallel programming, distributed systems, CQRS, and DDD. The final interview was a team-fit round centered around behavioral questions and past experience. I was expected to explain projects in detail, including technical decisions, metrics, and outcomes. The biggest issue with the process was the communication. Response times were consistently slow, and I had to follow up after each stage to get updates. I communicated clearly that I was in the final stages with another company and later that I had received a competing offer, but this did not seem to meaningfully affect the pace of communication. After completing the final interview, I never received any update despite following up, which made the overall experience feel disrespectful to the time and preparation the process required.

The recruitment process looks like this: OA -> HR interview -> 2 tech interviews -> 1 interview with the manager -> you receive the offer. The process started with an OA, which had 2 coding challenges, theoretical questions and a DB problem(to write a SQL query). If you get a good score, you receive in a few minutes an invitation for the HR interview. This interview is really short, max 30 min, and you discuss with the recruiter the details of the position. After that, you receive an invitation for the first tech interview. In this interview, you will have to code the solution of a problem. The second interview has both theoretical question + code. Also, they are using Java, so it would be better for you to be familiar with this language.