Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Bloomberg

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Bloomberg | Offerte di lavoro di Bloomberg | Stipendi di Bloomberg | Benefit di Bloomberg
      Colloqui di BloombergColloqui per Senior Software Engineer presso BloombergColloquio di Bloomberg


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Senior Software Engineer

      15 mar 2025
      Candidato anonimo a colloquio
      New York, NY
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 3 settimane. Ho sostenuto un colloquio presso Bloomberg (New York, NY) nel mese di mar 2025

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      Leetcode medium/medium hard questions, low level design question
      Rispondi alla domanda
      1

      Altre recensioni di colloqui per Senior Software Engineer presso Bloomberg

      Colloquio per Senior Software Engineer

      6 mag 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Bloomberg

      Colloquio

      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

      Colloquio per Sr. Software Engineer

      21 apr 2026
      Candidato anonimo a colloquio
      New York, NY
      Nessuna offerta
      Esperienza positiva
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso Bloomberg (New York, NY)

      Colloquio

      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

      Colloquio per Senior Software Engineer

      14 mag 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza negativa
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura tramite un'altra fonte. Ho sostenuto un colloquio presso Bloomberg nel mese di apr 2026

      Colloquio

      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.

      Domande di colloquio [1]

      Domanda 1

      Build whatsapp from a system design perspective.
      Rispondi alla domanda
      1