Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Bloomberg

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Bloomberg | Offres d’emploi chez Bloomberg | Salaires chez Bloomberg | Avantages sociaux chez Bloomberg
      Entretiens chez BloombergEntretiens d’embauche pour Financial Software Engineer chez BloombergEntretien chez Bloomberg


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Financial Software Engineer

      2 nov. 2011
      Employé (anonyme)
      New York, NY
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 3 jours. J'ai passé un entretien chez Bloomberg (New York, NY) en oct. 2011

      Entretien

      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.

      Questions d'entretien [2]

      Question 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 réponse

      Question 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 réponse
      2