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

      15 mars 2025
      Candidat à l'entretien anonyme
      New York, NY
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

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

      Entretien

      Matched with two teams and proceeded to the final on-site for both of them. The technical screening was similar to what others have described on here - one to two medium/medium-hard questions to complete. Team may ask some questions on your resume, or just jump right into the problem. There is a very clear disconnect between the recruiters and teams when it comes to the final round - I received a prep guide and had a prep call that very clearly indicated the system design round would be a High Level Design for a distributed system. Come the actual system design interview, the engineers spent about 30 minutes asking questions on my resume and teaching me about financial concepts, leaving me roughy 20 minutes to implement a low level class design for complex financial logic I just learned minutes before in the interview. Had I known the process would be like this, I could have tried to prepare better but I was blindsided due to the inaccuracy of the recruiter prep call and prep guide document. The engineers in my on-site were also completely uninterested in answering thoughtful questions I put together after reading articles and doing research on the company. By the end of the interview, I was no longer interested in working with the team.

      Questions d'entretien [1]

      Question 1

      Leetcode medium/medium hard questions, low level design question
      Répondre à cette question
      1

      Autres retours d’entretien d’embauche pour un poste comme Senior Software Engineer 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 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