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

      Bloomberg

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Bloomberg | Ofertas de empleos en Bloomberg | Sueldos en Bloomberg | Beneficios en Bloomberg
      Entrevistas de BloombergEntrevistas para el puesto de Software Developer en BloombergEntrevista de Bloomberg


      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

      26 may 2017
      Candidato de entrevista anónimo
      Londres, Inglaterra
      Sin oferta
      Experiencia negativa
      Entrevista normal

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 5 días. Acudí a una entrevista en Bloomberg (Londres, Inglaterra) en may 2017

      Entrevista

      I was initially contacted by a recruiter. We arranged a first technical call via phone. The interview starts with general information about the company and position. Later you walk through your CV highlighting any achievements. Everything went pretty smooth at this stage. I seemed to have impressed the interviewer with some good optimizations in the past. There were generally two or three things that some will see as red flags that occured during the interview: 1) The interviewer was mentioning languages and implementation details when referring to giving a high level view of the infrastructure. 2) The interviewer was very pushy into forcing the coding solution as to his mind - instead of respecting the interviewee's approach. 3) The interviewer didn't seem to understand that O(n3), O(n2) and O(n1) are the same thing and insisted in providing the most optimized solution from the beginning. The wost part was the technical part. I was asked to solve a technical problem (in Python for the role I applied). The problem itself is not that hard but personally I got a bit mixed in the problem and then the interviewer made it harder for me instead of helping me with hints for the existing code. The interviewer asked me about what I had in mind and its complexity. I said O(n3) and the reason behind it. He mentioned there is a better way so I managed to think of a better way giving O(n2). He insisted on an O(n1) approach and I got a rough idea about the implementation he meant. The problem was that I still didn't manage to get the first approach to a workable solution and I was in some way forced to start again from the optimized solution. This just made it worse. After getting even more stuck, instead for the interviewer giving me some hints, he started micro-managing my approach which didn't actually affect the part where I got stuck at the first place. This totally broke my thinking (and even moral) since the implementation became something that the interviewer understood but was totally different from how I would do it. Needless to say, I didn't go further. I think the specific interviewer was quite narrow-minded and I hope he doesn't represent the average personal at Bloomberg.

      Preguntas de entrevista [2]

      Pregunta 1

      Walk me through your CV
      Responder pregunta

      Pregunta 2

      Find the maximum sequence of the same letters
      1 respuesta

      Otras opiniones sobre las entrevistas para el puesto de Software Developer en Bloomberg

      Entrevista de Software Engineer

      1 jun 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia neutra
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Bloomberg

      Entrevista

      Overall, it was a positive and professional interview experience, though the interviewer was on the stricter side. Unfortunately, I was dealing with an illness and wasn't able to prepare as thoroughly as I wanted to, which left me feeling a bit off throughout the conversation. Despite not feeling my best and facing a tough interviewer, the process was well-structured.

      Preguntas de entrevista [1]

      Pregunta 1

      How to add two big numbers
      Responder pregunta

      Entrevista de Software Engineer

      26 may 2026
      Candidato de entrevista anónimo
      New York, NY
      Sin oferta
      Experiencia neutra
      Entrevista normal

      Solicitud

      Acudí a una entrevista en Bloomberg (New York, NY)

      Entrevista

      Fairly simple. Phone call then onsite. For onsite it was 10 min office tour follow by 1 hr interview then 1 hours system design and 30 mins manager interview. Interviewers were nice and the recruiter was accommodating.

      Preguntas de entrevista [1]

      Pregunta 1

      How do you handle request to large dataset?
      Responder pregunta

      Entrevista de Software Engineer

      20 may 2026
      Candidato de entrevista anónimo
      New York, NY
      Sin oferta
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en Bloomberg (New York, NY)

      Entrevista

      5 rounds first 3 being leetcode coding ones and the last 2 being behavioral. The first three are the hardest asking mainly taggeed questions and the rest are not that bad

      Preguntas de entrevista [1]

      Pregunta 1

      Solve a coding question leetcode medium
      Responder pregunta