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

      Chi siamo
      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 Software Developer 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 Software Developer

      26 mag 2017
      Candidato anonimo a colloquio
      Londra, Inghilterra
      Nessuna offerta
      Esperienza negativa
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 5 giorni. Ho sostenuto un colloquio presso Bloomberg (Londra, Inghilterra) nel mese di mag 2017

      Colloquio

      I was initially contacted by a recruiter. We arranged a first technical call via phone. The interview starts with general information about the company and position. Later you walk through your CV highlighting any achievements. Everything went pretty smooth at this stage. I seemed to have impressed the interviewer with some good optimizations in the past. There were generally two or three things that some will see as red flags that occured during the interview: 1) The interviewer was mentioning languages and implementation details when referring to giving a high level view of the infrastructure. 2) The interviewer was very pushy into forcing the coding solution as to his mind - instead of respecting the interviewee's approach. 3) The interviewer didn't seem to understand that O(n3), O(n2) and O(n1) are the same thing and insisted in providing the most optimized solution from the beginning. The wost part was the technical part. I was asked to solve a technical problem (in Python for the role I applied). The problem itself is not that hard but personally I got a bit mixed in the problem and then the interviewer made it harder for me instead of helping me with hints for the existing code. The interviewer asked me about what I had in mind and its complexity. I said O(n3) and the reason behind it. He mentioned there is a better way so I managed to think of a better way giving O(n2). He insisted on an O(n1) approach and I got a rough idea about the implementation he meant. The problem was that I still didn't manage to get the first approach to a workable solution and I was in some way forced to start again from the optimized solution. This just made it worse. After getting even more stuck, instead for the interviewer giving me some hints, he started micro-managing my approach which didn't actually affect the part where I got stuck at the first place. This totally broke my thinking (and even moral) since the implementation became something that the interviewer understood but was totally different from how I would do it. Needless to say, I didn't go further. I think the specific interviewer was quite narrow-minded and I hope he doesn't represent the average personal at Bloomberg.

      Domande di colloquio [2]

      Domanda 1

      Walk me through your CV
      Rispondi alla domanda

      Domanda 2

      Find the maximum sequence of the same letters
      1 risposta

      Altre recensioni di colloqui per Software Developer presso Bloomberg

      Colloquio per Software Engineer

      1 giu 2026
      Candidato anonimo a colloquio
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho sostenuto un colloquio presso Bloomberg

      Colloquio

      Overall, it was a positive and professional interview experience, though the interviewer was on the stricter side. Unfortunately, I was dealing with an illness and wasn't able to prepare as thoroughly as I wanted to, which left me feeling a bit off throughout the conversation. Despite not feeling my best and facing a tough interviewer, the process was well-structured.

      Domande di colloquio [1]

      Domanda 1

      How to add two big numbers
      Rispondi alla domanda

      Colloquio per Software Engineer

      26 mag 2026
      Candidato anonimo a colloquio
      New York, NY
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

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

      Colloquio

      Fairly simple. Phone call then onsite. For onsite it was 10 min office tour follow by 1 hr interview then 1 hours system design and 30 mins manager interview. Interviewers were nice and the recruiter was accommodating.

      Domande di colloquio [1]

      Domanda 1

      How do you handle request to large dataset?
      Rispondi alla domanda

      Colloquio per Software Engineer

      20 mag 2026
      Candidato anonimo a colloquio
      New York, NY
      Nessuna offerta
      Esperienza neutra
      Colloquio difficile

      Candidatura

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

      Colloquio

      5 rounds first 3 being leetcode coding ones and the last 2 being behavioral. The first three are the hardest asking mainly taggeed questions and the rest are not that bad

      Domande di colloquio [1]

      Domanda 1

      Solve a coding question leetcode medium
      Rispondi alla domanda