Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Revolut

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Revolut | Offres d’emploi chez Revolut | Salaires chez Revolut | Avantages sociaux chez Revolut
      Entretiens chez RevolutEntretiens d’embauche pour Senior Software Engineer chez RevolutEntretien chez Revolut


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Senior Software Engineer

      18 juill. 2024
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Revolut

      Entretien

      First interview with HR. Second interview was a live coding challenge, that was really disappointing. Some considerations here: - They ask you to build a load balancer, and I was aware of it in advance, so I was able to properly prepare for the interview, even I coded it before interview to practice. - You have around 40 minutes of effective time for coding. - I had issues with my IDE as I installed it from scratch (IntelliJ) and by default there's some AI for autocomplete that the guy asked me to remove. After removing the plugins (there are a couple), the IntelliJ was crashing and 5-10 minutes were gone. - I approached the solution with TDD in a simple and elegant way. They ask as a first task to create a load balancer with a limit of 10 servers and not allowing creating duplicates. All good until here. Second task is to assign randomly one of the servers from the list. And here they expect to use the random (in that case Random from Kotlin) that I barely used it in the past and wasn't able to remember how it worked. As you're not allowed to use any autocomplete or search on the internet, you need to know and remember how Random works. Also to be able to test properly the server assigned, you need to mock the random behaviour (in Kotlin Random is an abstract class). I told to the guy that this wasn't a good approach, as I need to manually inject the random in production sources just because of the test. Also I'm heavily against using mocks and so on. But looks like they are from that old-school style of SOLID everywhere, so they expect you to create your own implementation of Random and inject it to be able to test it. - Because of this back and forth about the Random stuff, I ran out of time (and they expect to finish this second step to be able to move forward to the next stage). - The guy of the interview was rude and 0 emphatic, he was just a guy there on the background barely speaking and 10 minutes before ending the interview he said "You ran out of time already" - My feedback is totally aligned with lots of other feedbacks I read in Glassdoor about Revolut interview, so I have the feeling that I'm one more who threw away his time. I ended up with a really bad impression about their interviewing process. I have to say that HR interview was really good and the guy was really kind.

      Questions d'entretien [1]

      Question 1

      Create a load balancer with max 10 servers and without duplicated servers
      1 réponse
      6

      Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer chez Revolut

      Entretien pour Senior Software Engineer

      1 mai 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Revolut

      Entretien

      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.
      1

      Entretien pour Senior Software Engineer

      20 mai 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien facile

      Candidature

      J'ai postulé en ligne. Le processus a pris 5 jours. J'ai passé un entretien chez Revolut en mai 2026

      Entretien

      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.

      Entretien pour Senior Software Engineer

      17 avr. 2026
      Employé (anonyme)
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 4 semaines. J'ai passé un entretien chez Revolut en avr. 2026

      Entretien

      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