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

      10 juin 2015
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre

      Autres retours d’entretien d’embauche pour un poste comme Senior Software Developer chez Bloomberg

      Entretien pour Senior Software Engineer

      6 mai 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Bloomberg

      Entretien

      Terrible communication. Got passed between 3 different recruiters all of whom gave specific dates for updates and blew past them. Descriptions of what would be covered in the interviews are wholly inaccurate (don’t bother reading the PDF they sent to “prep” you, almost none of it came up in any of the 3 interviews I did with them.) Interviewers themselves were decent but clearly had exact “right” answers they were looking for. What’s the point of a leetcode question where there’s only one way to implement it? What’s the point of a system design interview where you’re having a candidate parse through a complex system that they clearly already know everything about and are just looking for 1-2 EXACT modifications to check off their boxes? Was there even a right answer? I genuinely don’t know what this company was looking for. Waste of time, waste of effort, waste of resources. Avoid, avoid, avoid
      Entretien moyen

      Candidature

      J'ai postulé via une agence de recrutement. Le processus a pris 2 semaines. J'ai passé un entretien chez Bloomberg en juin 2015

      Entretien

      Recruiter contacted me. Had a phone interview set up. First phone interview went well. So, they set up another phone interview since I am not local. The position was in NY. 2nd interviewer wasn't too bad, but he really pushed me to code in Java, while I don't have that expertise over the language. I had to kind of force him to write code in c++. I guess he wasn't an expert in c++. He asked me to write thread safe singleton pattern class. I wrote one in c++ (with static Singleton object with lazy initialization). I informed him why I selected static and explained about c++11 guarantees. He then asked me why is c++11 guaranteeing that (Really? I think he probably didn't get much of c++). He asked me two questions. I cracked the first one and kind of slipped bad on 2nd one, because I couldn't recall the syntax for win32 multi-threading APIs (CreateThread, WaitforMultipleObjects, etc..). Interviewer tried to help me, but wasn't enough. In short, first interview was about c++ and algorithms. While 2nd interview was supposed to be more about Java, which is kind of weird. Also, everything in 2nd interview was about multi-threading. See in questions section for the questions asked. 2nd interview sounded like a nice guy, but I think he didn't have enough experience conducting phone interviews because 1) he wasn't open to hearing my ideas about the solution (may be because he didn't know much c++). 2) he wanted me to code in java. I switched the language on hackerrank to c++, he switched it back to java. I then switched it back to c++ and just informed him that Java won't work. lol. That's when I figured out I won't get a recommendation for on-site round. He didn't even let me ask any questions at the end, how immature. If I would have gotten a call further, I would probably have passed the opportunity, because after a few years of experience, one thing I have realized is that business is just people. If you can't work with them or if it is hard to work with them, you probably don't want to do business with them. Its that simple. Good luck Bloomberg!

      Questions d'entretien [1]

      Question 1

      Interview 1: 1. virtual functions, inheritance, etc..easy to answer c++ questions. Conversation was for about 20-25 minutes 2. Can't exactly recall, but it was about Binary Search Tree, pretty easy to find on the web. I think it was to do with levels in BST, I used recursion in the solution. Interviewer was happy with the solution. Overall call lasted for about 1 hour and 5 minutes including some questions I asked him. Interview 2: 1. What is mutex, semaphore? 2. What is a singleton pattern and can you write one that is thread-safe 3. Write a consumer producer problem. Producer produces 1000 objects and there are five consumers that consume 10 objects at a time in round robin fashion until all of them are consumed. This means that if consumer 1 consumes 10 objects, it has to wait for consumer 2, 3, 4, 5 to consume 10 objects each before it can consume other 10.
      2 réponse(s)

      Entretien pour Sr. Software Engineer

      21 avr. 2026
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Bloomberg (New York, NY)

      Entretien

      Interviewed with two separate teams. Coding rounds. Leet code style question. The interview went on for 1 hr. Waiting for the next steps. The seem to like link lists and arrays

      Entretien pour Senior Software Engineer

      14 mai 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé via une autre source. J'ai passé un entretien chez Bloomberg en avr. 2026

      Entretien

      Drawn out / repetitive / redundant, overly focused on algorithms you won't use, matches candidates with teams that don't need them. I started interviewing with 2 teams per their process, passed one and failed the other. The team I passed with then filled their role, so they had me interview with a 3rd team but had me start over from first round. I pass this AGAIN (so, to be clear, I've passed 2 out of 3 first rounds with 3 different teams), and then they have me do 2 second round interviews. I made clear I had a lot of client-side experience with a high degree of skill in interface engineering and client architecture. The system design interview asked me basically to "build whatsapp," which is a backend distributed architecture problem. They weren't checking that I knew how a REST api works - they wanted to know about database redundancy with sharding and partitioning and so on, interservice data format pros and cons, message broker queue latency, scaling all these backend things....like, it was not basic stuff. They clearly wanted a distributed systems expert, and of course declined to move forward with my candidacy. With this being the final result of 5 interviews, I expressed that I felt I was matched with the wrong team and received no reply. Kind of feel like my time was wasted. Also, a portion of people I spoke with had no personality or warmth whatsoever.

      Questions d'entretien [1]

      Question 1

      Build whatsapp from a system design perspective.
      Répondre à cette question
      1