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

      15 févr. 2014
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Bloomberg (New York, NY) en févr. 2014

      Entretien

      Found posting on LinkedIn group. Contacted recruiter. Had a good 20-30 min. conversation with recruiter, who then scheduled a technical phone interview the next week. The position was for a C/C++ developer so (surprise surprise) C++ questions. Typical technical questions about C++. Nothing to easy, but nothing crazy obscure either. That went ok. Had a second technical phone interview. Similar questions. One design question. But as long as you understand data structures - and how and what to use them for, it shouldn't be too difficult. Got invited for an onsite interview(s) in NYC. These are done in stages, with little to no break. First interview @10am, was technical with 2-3 developers. Similar to the phone technical interviews. But this time you need to write code. Unfortunately, you have to write code on paper (tiny sheets of paper), with dull pencils. I should have brought my own. Not sure why they don't have whiteboards there. At the end of each interview, the team decides whether to have you continue interviewing. I got a second interview. Again a team of 2-3 developers, asking technical questions, nothing to crazy though. But for this second interview, I felt the team lead (I assume he was the lead, or at least a more senior developer) was trying to pressure me to write the code faster. Kept saying we're almost out of time, even though we weren't really). But it is a good technique. Seriously. As an experienced s/w developer, there are times when you will be in a high pressure situation, and it is important to see how people respond. This is where my onsite interview day ended. As I understand it, the normal plan is to have 2, technical interviews, then a manager interview, then an HR person comes in to wrap things up. You may get an offer right then and there, or you may get it within 24 hours, if they can't quite make up their minds then and there. But ... they will let you know either immediately, or within 24 hours at latest. Which is great, really. I knew that after the 2nd tech. team left, and the HR person came into the room that I was done for the day. I wasn't upset by it though. I enjoyed the experience. My suspicion is that I wasn't maybe as sharp, technically, in my responses. I didn't prep to much just before the interview. Mostly because I wasn't too sure if I really wanted to live and work in NYC, but also because I wasn't totally sure if this would be a good fit. My advice is to prep writing code before hand. There are lots of interview questions you can find, here and elsewhere. Practice them. And on the day of the interviews, practice them about an hour or two before the interview, just to get your brain warmed up for coding of the top of your head, on paper. If you get an onsite interview, eat a big breakfast before. They will keep you there until they are done with you. Of course you can get bathroom breaks. But you'll be there all morning, and possibly afternoon. But honestly, I find the time flies by. My interviews started at 10am. I had 2, but the second didn't end until 12:30, and I left by 1pm. There was a long wait between the end of the 2nd interview and the HR person telling we were done. Which is why I think I did OK, but just not 100% there for them, I guess.

      Questions d'entretien [1]

      Question 1

      Nothing to difficult, I guess. Design a system that keeps track of tickers (name and price) per exchange that: gives the top 20 most recently updated tickers - or something like that.
      1 réponse
      7

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

      Entretien pour Senior Software Engineer

      9 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Bloomberg

      Entretien

      Phone screen - LeetCode style (Medium problem) Onsite (SF) - 2 hours coding round - build inverted in-memory index search - Design round (Throw some random problem) - Behaviour round with senior leadership

      Questions d'entretien [1]

      Question 1

      - Leet code medium - In memory search system by reading their data set
      Répondre à cette question

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