Revolut Sr. Software Engineer interview questions

Be prepared to go through a 5 stage interview process..yes you read that right, 5. I started out our initial call with an internal recruiter and the experience quickly turned sour. The recruiter's lack of technical knowledge was evident, and they seemed more interested in testing my ability to recall specific terminology rather than assessing my actual skills. Any answer that wasn't word-for-word accurate was met with condescending tone which was frustrating. To my surprise, the recruiter told me I had moved on to the next stage, which was supposed to be a technical round. However, I soon realized that this was actually the first stage, and I was expected to proceed with the live coding round. The live coding round was a disaster. The interviewer was late, showed little interest in our interaction, and provided a vague problem description for a URL shortener challenge. I had to spend 15 minutes clarifying the requirements, which was unacceptable. I was expecting a more structured approach like a GitHub repository or a hackerrank interface. After completing the challenge, I received a passive-aggressive email stating that they were looking for specific skill sets. In reality, it seemed they were looking for someone who could memorize a vast amount of technical terminology, rather than a developer with actual skills and experience. Overall, I was disappointed and frustrated with the interview process. It was a waste of my time and energy, and I would not recommend this company to others.

Recruiter approached with a questions regarding database, data structures, java and concurrency. After answer it they scheduled a first interview with HR. More of the same. In the living code interview, interviewer gave some load balance tasks like register an unique load balancer and to implement a random algorithm to get a load balancer instance. While applying clean code practices and strict TDD from scratch - no engagement from the interviewer side at all. Although I was talking through my mental process all the time, little interactions were made. At the end, Interviewer only made one question in 45 minutes: how should you make a test if you want to be certain if the random algorithm was working? As I already implemented the test using a simple logic of getting at least one of several instances, he said that a way of doing it is trying thousands of times (exponentially speaking). It striked me as a surprise once tests should be deterministic and the given solution is not deterministic at all. Not taking into consideration the CPU and memory wasted. I mean, it's a random algorithm. After 1 day they vaguely replied that "after much consideration, we have decided not to proceed further with your application, as we require more specific knowledge to be successful in our recruitment process". That's it. I have no idea what this means. No feedback. No explanation after surviving 1 hour of me trying to read interviewer's reaction. The only "humane" part was the contact by the recruiter. All the rest was a set of trap questions that you must answer what they want to hear. This was my second and last attempt to enter in this company and after giving them some credit, process is flawed. They're looking at someone that would answer exactly what they wanna hear.