Probably the most unprofessional interview I've experienced during my career. I didn't apply a recruiter reached out to me through LinkedIn, despite being bad reputation in glassdoor on reviews and interview experience I still gave benefit of the doubt due to the big brand value that Revolut has but it totally lives up to it's name I can see why people totally not enjoy working here. Recruiter screen - The person paid no attention at all, they barely spoke for 5 mins asked some basic questions and then simply ended with Good luck with the process ahead. Didn't even ask my name or resume never happened with me before Coding round - Load balancer question. Fairly straight forward to implement, basic concurrency related questions and some TDD. Again an extremely unfriendly interviewer but I managed to answer just about everything and solved all of his followups only to end up with a rejection. I wouldn't recommend interviewing here as the place definitely doesn't seem like a good work environment and I have plenty of folks who shared the same experience as me both inside the company and the interview process

First stage interview was a 30 min chat with a recruiter who asked me about my experience and then some technical questions around DB transactions, microservices patterns and java concurrency. The next stage was a 1-hour long live coding exercise (not leedcode or hackerrank type questions) but you have to be very fast. It is split around 15 min talk to make sure you understand the requirements and then 45 to code a service. The exercise is very easy in my opinion even for a non senior engineer. However, they sent you the requirements over the chat window and here is where the fun part begins... The text of the exercise comes deliberately confusing and talks about requirements that you will not need to implement so you have to spend time talking with interviewer about what you will need to include and what not. I was like ok do I need to implement feature A ? No you don't need that. Ok and what about feature B that is described in the text? No you can ignore that.. On top of that in whatever time you are left to go all guns blazing and start coding the interviewer interrupts you and questions your decisions, so you have to stop and justify them and by the end you need to have an pretty much exhaustive set of unit tests of a maintainable and extensible solution. All in all the exercise is pretty easy but it seems that they value a lot machine gun type of coders. The interviewer also told me they are dealing with a lot of concurrency issues which is no wonder if they expect you to code so fast... I'd have to say that interviewers are polite and but not very experienced for this type of coding exercises.

The interview process consisted of 2 stages for me: 1. Stage life coding interview with one developer, where you get small portion of the tasks and when you finish with first task you get new task. 2. This interview was more technical, with two engineers. In the beginning interview they gave simple task on concurrency, after that we discussed theory of DB, concurrency, software design. All interviewers were polite, on all my answers they said that I am right and I am sure on 100% that I was right, but I get response after one or two hours after interview : "Thank you for your time! Unfortunately we can't proceed to the next steps. From successful candidates we expect deeper understanding of databases and concurrency.". It was were strange because all questions regarding all topics I answered, but get such strange response. I tried to ask HR, but she did not reply me. I just read reviews on the company and see that not only me got into this situation. I do not know the reasons why they do like this, but suggest do not spend you time on this company. They do great product, but by some reason can do so bad stuff during looking for the new employees. Updated: HR response: "You are right, you were able to answer all questions correctly, but unfortunately we require more deep knowledge in the DB part and less mistakes at the coding part for offering more than Junior position." Regarding DB I do not know what to comment. In development part I did not remember API of the BigDecimal class. Maybe for someone this update will be helpful.