It's a lengthy process, and I didn't go past the first coding interview.

First, you have a call with the recruiter. This call follows a script and involves a bunch of questions. Topics include:

• ACID
• HashMap time complexity
• Database indexes
• The difference between backwards and forwards compatibility
• The difference between sharding and partitioning

Lots of questions; I can't remember all of them.

If you get through that, it's the first coding interview. They tell you to set up a simple (no framework) Java project beforehand, and during the interview, you will receive some instructions.

I was asked to code a load balancer. The requirements will force you to make decisions about concurrency.

The interviewer was nice, but it's incredibly disappointing that their style of interviewing seems biased to make people fail. They will set traps and expect you to think of a solution in 10 seconds. If you don't, they will fail you.

It's not at all a representation of real-life work. No wonder you almost never see anyone getting an offer; they must enjoy spending money on recruitment.

In my view, I was able to find adequate solutions for all the problems they forced me into. They sometimes disregarded simpler solutions, like making the LoadBalancer class immutable.

Like many other companies, the recruitment process of Revolut is simply broken. I won't be applying again.

What's the difference between ArrayList and LinkedList?