I was interviewed for a Senior Software Engineer position at Revolut and was rejected after the second step.

The first interview was with a recruiter. The communication was not great, as the recruiter's accent made it very difficult to follow. I was asked some technical questions by the recruiter, who clearly didn't understand if my answers were correct.

The second stage was with a Senior Engineer. I did what was asked, and even performed some improvements requested by the engineer. In the end, I was rejected with no proper feedback, just the ordinary email rejection template.

Honestly, I feel that the engineer didn't want to hire me for some other reason, as every time the engineer identified a limitation, I was able to solve it. I think maybe at Revolut, people are just expected to know the interview in advance and prepare for it like a robot, instead of doing it in an iterative way. Still, I think the questions were interesting, and the problem was interesting.

Concurrency issues, sharding, replication, CQRS, event sourcing, SOLID principles, ACID database characteristics, or even transaction isolation levels. Write a thread-safe load balancer API using a TDD approach.