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

      6 feb 2015
      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 2 mesi. Ho sostenuto un colloquio presso Bloomberg (New York, NY) nel mese di feb 2015

      Colloquio

      The interview process is grueling and pointlessly long. A total waste of time. Two phone interviews (about half hour each) followed by essentially an entire day of round after round (I counted 7 rounds) of technical interviews. I was grilled at their headquarters for over seven hours only to get rejected the next day. Each round except for the final (senior manager) and HR rounds were two-on-one. There was a lunch break where two developers buy you lunch and it's supposed to be "the opportunity for you to ask questions", but basically it's just another interview round as they ask you the standard questions about what you worked on at previous jobs, and maybe even some light problem solving questions, but thankfully you don't have to write code over lunch.

      Domande di colloquio [1]

      Domanda 1

      1) Write a method to find the lowest common ancestor of a binary search tree. 2) Write a thread-safe singleton class. 3) Design a parking lot system that will return the number of the next open space. Consider how to optimize the solution if the parking lot was gigantic. 4) Design a history system for a web browser that allows the user to navigate forward, backward, and enter a new URL. 5) Write a method that takes a list of strings and returns a list of buckets of anagrams of those strings. 6) If you have a two-dimensional array representing a maze, return a solution for the path from the upper-left corner to the lower-right corner. You can only move down or right. ie: input: [1, 1, 0, 0] [1, 0, 0, 0] [1, 1. 0, 0] [0. 1, 1. 1] solution: [1, 0, 0, 0] [1, 0, 0, 0] [1, 1, 0, 0] [0, 1, 1, 1] 7) If you have an input character array, for example "_ _ _hello_ _ _ world _ _", write a method to return a character array with the leading and training spaces removed and only one space between each word, ie: "hello_world" 8) Describe how you might architect a system for searching across multiple data sets and returning the results to a client. If some data sets came from external sources, how could you mitigate the amount of code that you'd need to re-write? How can you ensure that all the results are returned to the client at the same time? 9) Describe how you might architect a system that receives a constant stream of data (such as stock ticker symbols and prices) and sends this data to multiple subscribers that only want to listen for certain tickers. Suppose there is a massive amount of data and you discover there is a long delay in the data reaching the consumers. How would you solve this?
      1 risposta
      16

      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