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 Financial Software Engineer 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 Financial Software Engineer

      2 nov 2011
      Empleado anónimo
      New York, NY
      Oferta aceptada
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Solicité el puesto a través de la escuela superior o la universidad. El proceso duró 3 días. Acudí a una entrevista en Bloomberg (New York, NY) en oct 2011

      Entrevista

      The process consisted of three separate interviews on subsequent days with three separate Software Developers and Team Leaders at Bloomberg. It primarily consisted of questions designed to ascertain my programming knowledge and ability to code on the fly. Questions varied from the specific, such as, how would you code a least common multiple algorithm, how would you detect a loop in a linked list. To the more general, such as given a very abstract high level diagram of the Bloomberg Terminal, and asked how you would setup and improve the communication between the Bloomberg and it's Clients. Since I primarily applied with a PhD in statistics, a few questions on financial mathematics were included, such as what is the Black-Scholes model, what are it's weaknesses, what models would you suggest, what do you mean by fat tails? However since it was obvious rather quickly my statistical knowledge was far fresher and more up to date then my coding ability, which had been dormant for around five years, they didn't spend too much time on the Statistics side of the questions. The interview ended with a brief one on one with a person from H:R that asked me some of the standard questions you see on "online interview aids". Like why do you want to work at Bloomberg, and I see you've got extensive teaching experience, do you plan to go into Academia. What other areas are you applying to other then Finance, etc. The bulk of the interview process, thus contained mainly knowledge based questions unrelated to what you find in most interview help books and resources.

      Preguntas de entrevista [2]

      Pregunta 1

      How would you detect a loop in a linked list? This was a technical question, finding the answer was difficult since I forgot how linked lists worked, but the interviewer didn't mind helping out with hints and guiding me along. They weren't, obviously interested in the exact answer, but how my thinking works
      1 respuesta

      Pregunta 2

      How would you find bugs in a very large program. This is one of the few questions I wasn't able to answer to my satisfaction at least, since I hadn't worked with large programs and were still limited to small simple debugging techniques
      1 respuesta
      2