Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Revolut (Barcellona) nel mese di nov 2024
Colloquio
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.
Domande di colloquio [1]
Domanda 1
Give me examples of concurrency problems.
Give me one example of algorithm to store data in a database.
What's the difference between sharding and replication?
Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso Revolut
Colloquio
The experience was disappointing and reflected a lack of professionalism.
The interaction gave the impression of a disorganised or potentially unhealthy work culture.
Answered most of the questions accurately and to the best of my ability.
The interview was initially scheduled for a short time slot. Toward the end, the interviewer asked for my availability and indicated that they would schedule a follow-up session to continue the discussion. However, no further communication or follow-up was received.
Ho presentato la mia candidatura online. La procedura ha richiesto 5 giorni. Ho sostenuto un colloquio presso Revolut nel mese di mag 2026
Colloquio
During the initial HR screening call, the recruiter explicitly stated that Revolut was not hiring for a specific team and that team fit would be determined only after the coding and system design stages.
However, after passing the screening, I received the following rejection message: “After carefully reviewing your experience, we've decided to move forward with candidates whose profiles more closely align with the specific requirements of the role. Please note that this decision is based on current team needs.”
This creates a clear inconsistency in the communication. If team allocation and specific requirements were to be evaluated only in later technical rounds, a rejection citing “current team needs” right after screening appears contradictory. Such practices can lead to candidates investing time in the interview process based on incomplete or misleading information at the early stage.
Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Revolut nel mese di apr 2026
Colloquio
I interviewed for a Senior Software Engineer (Java) role.
The process was structured and fairly fast-paced: recruiter/screening conversation, technical discussions (coding and system design) focused on backend engineering and distributed systems, and a final manager/team-fit stage. Communication from recruiting was clear, and timelines were shared proactively. Overall, the process felt rigorous but very professional