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

      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

      Xelix

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Xelix | Empleos en Xelix | Sueldos en Xelix | Prestaciones en Xelix
      Entrevistas en XelixEntrevistas para el cargo de Python Backend Developer en XelixEntrevista en Xelix


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Indeed, Inc. "Glassdoor", "Worklife Pro", "Bowls" y sus logotipos son marcas comerciales registradas de Indeed, Inc.

      Empresas seguidas

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

      Búsquedas de empleo

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

      Entrevista para Python Backend Developer

      2 jul 2026
      Candidato de entrevista anónimo
      Londres, Inglaterra
      Sin ofertas
      Experiencia neutra
      Entrevista promedio

      Solicitud

      Me postulé en línea. Acudí a una entrevista en Xelix (Londres, Inglaterra) en jun 2026

      Entrevista

      The interview is made up of 4 stages. First interview is a chat with someone from the talent team. Lasted around 15 minutes. Basic generic questions. Why do you want to work here? Tell me about yourself. What do you know about Xelix? What technologies have you used? I got an email saying the I've moved to the second stage. The email stated, it was going to be a 20 minute interview diving deeper into my experience. When I had the interview with the hiring manager, they didn't really asked about my previous experience, it was more about ways of working, culture. Some of the questions asked. What something you learnt new about Python and where have you implemented it (be it personal or work)? How do you approach learning new technologies? How do you make sure a pull request is ready to be merged? There were probably some other questions but I can't remember. I wanted to asked some questions at the end of the interview, but the hiring manager was like at this stage it's usually to check culture fit etc. The next stage is where you can ask questions. The hiring manager did allow me to still ask some questions but I felt a bit akward so I only ask 2 short questions. I then was moved onto the third stage, which was a 2.5 hour technical test. Essentially, this is broken down into couple segments. Before the actual interview (15 minutes to be exact), I got sent a zip file containing the test that I needed to set up before the actual interview. Then I was on the call with 2 engineers. The first 30 minutes, is just going over the test and making sure I understand the tasks. You then work on the task for an 1 hour alone, time flies real quick. (I didn't manage to complete all the tasks on time). After that, I jumped back on a call with the engineers and discuss my approach and what I did. Questions were based on the task. Why did you this? What's the time complexity on this? How would you improve it to be more performative? Why did you decide to use data type? Could there be a problem using such data type? The test was made up of 2 parts. The first part is just to check your python knowledge. The second part is more around checking your Django knowledge. This tasks involved, building a model based on some csv file. Then creating a managment command to populate the data model based on the data in the csv file. Then lastly to create an API endpoint, that returns that data. I didn't passed this stage, so I don't know what's the last stage is like.