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.

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