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

      Booking.com

      Parte de Booking Holdings

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Booking.com | Ofertas de empleos en Booking.com | Sueldos en Booking.com | Beneficios en Booking.com
      Entrevistas de Booking.comEntrevistas para el puesto de Software Developer en Booking.comEntrevista de Booking.com


      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 Software Developer

      5 ene 2017
      Candidato de entrevista anónimo
      Ámsterdam
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. El proceso duró 3 semanas. Acudí a una entrevista en Booking.com (Ámsterdam) en ago 2016

      Entrevista

      Was approached by one of their in-house recruiters on LinkedIn. The recruiters were very, very competent and made the whole process as clear and straightforward as possible. It was very enjoyable, and also quick. First was a quick phone call with the recruiter. I was asked about salary. It was refreshing to have a frank and honest conversation without the negotiation. But be prepared for this question early on. Apparently salary is also dependant on interview performance. Second was an online test. Four questions on Hackerrank with a 90 minute limit. The questions tested basic CS knowledge like algorithms and data structures. It was very fair. The questions weren't equally difficult, so spending 1/4 of the time on each is a mistake. Luckily, I'd practised Hackerrank before, otherwise I would have bombed due to the weird standard in/out unit test thing Hackerrank uses. One annoying thing was that one or two of the test cases timed out for me. I was using Python, so I don't know if the timeout was set for C or something. Maybe I just used a sub-optimal algorithm, but I managed to talk to somebody else who ran into the same issue. On-sight was also great. They arranged for flights and a hotel. Plenty of drink and snacks. There were three interviews, each an hour. The technical interview was tricky but fair with two lovely interviewers. I had to write out an algorithm/pseudo-code on paper. This is harder than it sounds, and also worth practising. The system design/architecture was also with two interviewers, and largely good. My only criticism is given that they ask questions with potentially very broad and deep answers, adding an additional constraint after 30 minutes isn't great and messes with your time planning. Maybe it's a strategy? But they were supportive. The "fit" or "culture" interview was however terrible. It wasn't at all as advised. We barely talked about the company or their culture. Instead, a single developer who had apparently never worked with clients or outside web development interrogated me. It seemed like he was just looking for a weakness and focussed almost half the interview on something he perceived as that. He seemed friendly superficially, but unlike the other interviewers it seemed to not want me to succeed. It was almost hostile. I think he was inexperienced in people management and more of a developer than a manager. So the lack of broad experience and hostility made it very difficult to communicate well. Very surprising given that you would send such a person, especially to the only interview with one interviewer. Ultimately, I was informed that although the technical interviewers were in favour, the fit interviewer wasn't and so I didn't get an offer. Except for the fit interview, I'd do it again.

      Preguntas de entrevista [1]

      Pregunta 1

      The questions were mostly applications of basic CS stuff (algos and data structs). The hardest was the system design/architecture interview question. Frankly, if you don't have web dev experience, especially with large scale apps this is tricky to even revise for. The task/question I got was to design a critical component to interact with another service. The hard part was error handling/failover and maintaining consistency.
      Responder pregunta
      18

      Otras opiniones sobre las entrevistas para el puesto de Software Developer en Booking.com

      Entrevista de Software Engineer

      23 may 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia positiva
      Entrevista difícil

      Solicitud

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

      Entrevista

      I recently interviewed with Booking.com for a software engineer role. The process was well-organized and took about 3–4 weeks. It started with an online assessment on HackerRank with a couple of LeetCode medium problems. That was followed by a technical screen where I did live coding and discussed basic algorithms. The final round was a full day of back-to-back sessions: algorithmic coding, system design (something like designing a hotel availability checker), a behavioral round using STAR questions, and a chat with a manager about company values. The interviewers were professional and friendly, and the problems felt relevant to Booking's actual business. On the downside, some coding rounds felt repetitive, and I didn't get much feedback after being rejected. Overall, it was a fair but challenging process. My advice: practice medium-level array and hash map problems, review basic system design, and have solid STAR stories ready. I'd rate it 4 out of 5 stars and would recommend it to other engineers.

      Preguntas de entrevista [1]

      Pregunta 1

      Design a hotel search and availability system that returns available rooms for a given date range and can handle high traffic.
      Responder pregunta

      Entrevista de Software Engineer

      23 abr 2026
      Candidato de entrevista anónimo
      Ámsterdam
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Envié una solicitud electrónica. Acudí a una entrevista en Booking.com (Ámsterdam)

      Entrevista

      The whole process is composed of about 5 stages. Initial interview, then technical interview, followed by a “ownership” interview, then by a team-fit check interview. The initial interview is done by recruiters not based in the Netherlands (at least my experience) and felt as if the role had already been filled by the time I took it. Was answered with a “I’m doing good, hope you are doing good too. So this interview…” to “Hi, nice to meet you! How are you?”. It simply felt as if they didn’t want to be there and there was 0 engagement.

      Entrevista de Software Engineer

      22 abr 2026
      Empleado anónimo
      Oferta aceptada
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Acudí a una entrevista en Booking.com

      Entrevista

      Screener with a Director, coding round with TDD where you pair with an engineer and have an engineering manager present, behavioural with a senior engineering manager and an apprentice who was sitting it