Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empresas

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Revolut

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Revolut | Ofertas de empleos en Revolut | Sueldos en Revolut | Beneficios en Revolut
      Entrevistas de RevolutEntrevistas para el puesto de Senior Software Engineer en RevolutEntrevista de Revolut


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

      • Ayuda
      • Normas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de consentimiento de cookies

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. «Glassdoor», «Worklife Pro», «Bowls» y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información de primera mano.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista de Senior Software Engineer

      18 jul 2024
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Revolut

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Create a load balancer with max 10 servers and without duplicated servers
      1 respuesta
      6

      Otras opiniones sobre las entrevistas para el puesto de Senior Software Engineer en Revolut

      Entrevista de Senior Software Engineer

      1 may 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. Acudí a una entrevista en Revolut

      Entrevista

      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

      Entrevista de Senior Software Engineer

      20 may 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista fácil

      Solicitud

      Envié una solicitud electrónica. El proceso duró 5 días. Acudí a una entrevista en Revolut en may 2026

      Entrevista

      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.

      Entrevista de Senior Software Engineer

      5 jun 2026
      Candidato de entrevista anónimo
      Dubai
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. Acudí a una entrevista en Revolut (Dubai) en may 2026

      Entrevista

      Interview begins with recruiter calling, explaining you the process - Coding round - System Design - Hiring Manager round - Bar raiser round Each rounds are qualifier to another round. I did the coding round and system design, and I was ruled out

      Preguntas de entrevista [2]

      Pregunta 1

      Coding round for the Matrix grid problem for 60 min coding round First Part of the problem - Randomly fills a matrix (a * b) with 5 'x' alphabet, reset would be 'o' alphabet Second part of the problem (minesweeper game on Windows OS) - Given a matrix fill with 'x', find number of minds adjacent to it You need to solve both problems in 40 mins to qualify (First 10 mins Introduction, last 10 minutes is follow-up question) Remember to ask follow-up questions else it mark as candidate isn't proactive in asking questions
      Responder pregunta

      Pregunta 2

      2. System Design Round (90 mins) They ask to design an internal developer portal that establishes a fully automated, version-control CI/CD pipeline at scale. It basically involves designing the Internal developer, I started with requirements, non-funtional requirements, entities in system, I started with API design but they said it's okay to skip, and high level design. I started with Component-Based Design where I drawn frontend, CLI, API Gateway, catalog services, ... and all other components of the developer portal But they were interested in detailed CI/CD pipeline steps. This is where I screwed up; I caught the hint much later in the interview when there were 10 mins left, and I quickly drawn CI pipeline and a CD pipeline, but wasn't able to explain each step in the CD pipeline in detail. They wanted a more comprehensive Workflow and Operational design of CI/CD pipeline instead of a component-based design of the internal developer portal. Since I didn't complete the design, I was ruled out of the interview
      Responder pregunta