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

      Skyscanner

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Skyscanner | Ofertas de empleos en Skyscanner | Sueldos en Skyscanner | Beneficios en Skyscanner
      Entrevistas de SkyscannerEntrevistas para el puesto de Software Engineer en SkyscannerEntrevista de Skyscanner


      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. 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 de primera mano.

      Búsquedas de empleo

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

      Entrevista de Software Engineer

      29 nov 2018
      Candidato de entrevista anónimo
      Edimburgo, Escocia
      Sin oferta
      Experiencia neutra
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. El proceso duró 2 semanas. Acudí a una entrevista en Skyscanner (Edimburgo, Escocia) en oct 2015

      Entrevista

      Online test with HackerRank. This was quite easy and I passed. This was followed by an interview day. There were interviews with 5 people. Three formal-ish. One technical. One presentation-style interview where I had to explain something I had done. The office was really nice and the people were professional, although it felt like a couple of the interviewers thought interviewing me was beneath them and would obviously rather have been somewhere else. I thought I did well. I didn't manage to answer everything and probably made a few slips due to nerves, but overall I think I gave a fair impression. One thing that was strange is that I felt like I was being interviewed for a different job than the one I applied for. They asked me all sorts of high-level architecture questions, but I was interviewing for a developer position. Maybe they wanted to know if I was suitable for such a role in the future, but surely I would grow into that type of role through experience and training? I also felt that the technical questions put me on the spot and I'm not sure how useful that was. I had to answer them fast - I think I did OK. I understand the need to assess critical-thinking ability, but in this day and age I think it's more important to know how to research a problem and plan a technical approach, rather than having an encyclopaedic knowledge of computer science theory and being able to give the right answer instantly. I got the impression that the interviewer was more interested that my answer was instant and should match his, than listening to my analysis of the problem. If they keep interviewing this way they are going to end up with developers who are smooth talkers but not so hot technically. In the end I didn't get an offer. They told me that I had the wrong experience / not enough experience. This is a bit puzzling, since their job ads say that they are looking for people who are willing to learn, rather than having experience in specific technologies that they use. I believe that development skills are technology-agnostic, so it was a bit disappointing and I wish they had just told me what they were looking for up front. It seems their recruitment and engineering teams are not on the same page.

      Preguntas de entrevista [1]

      Pregunta 1

      How I would implement a url shortening service.
      1 respuesta
      3

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

      Entrevista de Software Engineer

      6 jul 2026
      Empleado anónimo
      London, AR
      Oferta aceptada
      Experiencia positiva
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Skyscanner (London, AR)

      Entrevista

      For software engineer role it was very detailed interview process at multiple stages, including coding test, and multiple system design interview. I must say it was a great experience and learning.

      Preguntas de entrevista [1]

      Pregunta 1

      Design a system such as; Twitter
      Responder pregunta

      Entrevista de Software Developer

      15 may 2026
      Empleado anónimo
      Shenzhen, Guangdong
      Oferta aceptada
      Experiencia positiva
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Skyscanner (Shenzhen, Guangdong)

      Entrevista

      Wonderful experience, I can tell them what I truly want. Hope to join the team and do what I want to do. The interviewer is so kind, allows me to think longer when I don’t know how to answer questions.

      Preguntas de entrevista [1]

      Pregunta 1

      Why do you want to join us.
      Responder pregunta

      Entrevista de Software Engineer

      30 abr 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Skyscanner en abr 2026

      Entrevista

      I interviewed with Skyscanner. The HR process was professional and well-organized. Communication was clear, and I appreciated that they offered to provide feedback afterward. The technical interview, however, was disappointing. The interviewer was not very communicative and didn’t provide much clarification when I asked questions about the task, which made the process feel less collaborative than expected. I implemented a working solution during the interview, focusing on correctness and efficiency. While it may have had minor syntax issues or missed some edge cases due to time pressure, it addressed the problem. At the end, I was surprised when the interviewer suggested that I might have copied the solution. This felt unexpected and unfair, especially in a live coding setting where the thought process is visible.

      Preguntas de entrevista [1]

      Pregunta 1

      There were two coding problems: the first was easy, and the second was a graph problem.
      Responder pregunta