Ir para o conteúdoIr para a pasta
  • Vagas
  • Empresas
  • Salários
  • Para empresas

      Avance em sua carreira

      Descubra qual pode ser seu salário, conquiste a vaga dos seus sonhos e compartilhe insights de qualidade de vida com sigilo.

      employer cover photo
      employer logo
      employer logo

      Bloomberg

      Empresa engajada

      Sobre
      Avaliações
      Remuneração e benefícios
      Vagas
      Entrevistas
      Entrevistas
      Buscas relacionadas: Avaliações da empresa Bloomberg | Vagas da empresa Bloomberg | Salários da empresa Bloomberg | Benefícios da empresa Bloomberg
      Entrevistas da empresa BloombergEntrevistas do cargo de Senior Software Engineer da empresa BloombergEntrevista da empresa Bloomberg


      Glassdoor

      • Sobre
      • Prêmios
      • Blog
      • Fale conosco

      Empresas

      • Conta gratuita de empresa
      • Área da empresa
      • Blog para empresas

      Informações

      • Ajuda
      • Regras da Comunidade
      • Termos de Uso
      • Privacidade e opções de anúncios
      • Não venda nem compartilhe minhas informações
      • Ferramenta de consentimento de uso de cookies

      Trabalhe conosco

      • Anunciantes
      • Carreiras
      Baixe o aplicativo:

      • Busque por:
      • Empresas
      • Vagas
      • Localizações

      Copyright © 2008-2026. Glassdoor LLC. “Glassdoor”, “Worklife Pro”, “Bowls” e o logotipo do Glassdoor são marcas comerciais pertencentes à Glassdoor LLC.

      Empresas seguidas

      Fique por dentro de todas as oportunidades e dicas internas seguindo as empresas de seus sonhos.

      Buscas de vagas

      Comece a buscar vagas para receber atualizações e recomendações personalizadas.

      Entrevista para Senior Software Engineer

      16 de abr. de 2022
      Candidato(a) sigiloso(a) à entrevista
      New York, NY
      Nenhuma oferta
      Experiência negativa
      Entrevista difícil

      Candidatura

      Candidatei-me por meio de recrutador(a). O processo levou 4 semanas. Fui entrevistado pela Bloomberg (New York, NY) em fev. de 2022

      Entrevista

      Recruiter reached out from Gambit Technologies and helped facilitate/schedule the initial phone screen. This was for a Trade Order Management System (TOMS) contract position. There was one interviewer on the call, and he asked me to solve a medium leetcode (LC) question (#133). Next was the virtual onsite interview, which consisted of four, back-to-back 30 minute sessions with two interviewers each. I was asked to solve LC questions (#1, #139, and #1396) in the first hour and a half. During the last 30-minute session, I was given an object-oriented design (OOD) problem involving a vending machine. The OOD problem caught me off guard, and I didn't do very well on it. I verbally acknowledged to the interviewers that I felt I didn't do very well. The next day I found out that I was allowed to move forward to what was supposed to be the "final" round with the hiring manager (HM). During the final moment of that interview, the HM brought up the fact that I had made that remark and asked me if I'd "like" to have another shot at an OOD problem. I reluctantly agreed, but felt I should've been given an up or down vote without putting me through further rounds of interviews. Early the next week, I had one more round with what was supposed to be an OOD problem - but it wasn't. There was a miscommunication of some sort, but it was instead a pure refactoring problem. I couldn't understand what either interviewer was asking me because they were both simultaneously barking at me, and their instructions weren't clear at all. Not to mention that I had a very hard time understanding them in general. As if that wasn't enough, my internet connection went down for 10 minutes, which exacerbated an already bad situation. I personally feel like the hiring manager was going to keep putting me through additional interviews until I "failed" at some point, since I believe they had already made up their minds and were looking to justify the pre-determined decision. My advice to you is that if they ask you to do additional rounds, you should put your foot down and say "either hire me or don't". It's comical because one of the recruiters kept trying to calm my anxiety by incessantly repeating that Bloomberg "really, really wants to hire you!". Yeah buddy, sure. Lol. To whomever at Bloomberg that cares to listen - 30 minutes per problem is really not enough unless a candidate spends significant amounts of time memorizing and working LC problems, and perhaps you should limit each 30-minute round to one-on-one panels (ONE interviewer and ONE interviewee). It's very stressful to have two interviewers talking over each other (particularly if you can't understand them) and issuing contradictory statements. Also, there really should be more time to allow the candidate to ask questions and perform some fact-finding. My experience was that the interview process was 90-95% leetcode and "problem-solving" challenges. Doesn't give the candidate much time to figure out if the role is even worth their pursuit.

      Perguntas de entrevista [1]

      Pergunta 1

      LC #1, #133, #139, #1396, Vending Machine Object Oriented Design, and a question involving some unintelligible, vague instructions for refactoring an "AppStoreEntry" class.
      1 resposta
      2

      Outras avaliações de entrevista de vagas de Senior Software Engineer da empresa Bloomberg

      Entrevista para Senior Software Engineer

      6 de mai. de 2026
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência negativa
      Entrevista difícil

      Candidatura

      Fiz uma entrevista na empresa Bloomberg.

      Entrevista

      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

      Entrevista para Sr. Software Engineer

      21 de abr. de 2026
      Candidato(a) sigiloso(a) à entrevista
      New York, NY
      Nenhuma oferta
      Experiência positiva
      Entrevista com nível médio de dificuldade

      Candidatura

      Fiz uma entrevista na empresa Bloomberg (New York, NY).

      Entrevista

      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

      Entrevista para Senior Software Engineer

      14 de mai. de 2026
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência negativa
      Entrevista difícil

      Candidatura

      Candidatei-me de outra forma. Fui entrevistado pela Bloomberg em abr. de 2026

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 1

      Build whatsapp from a system design perspective.
      Responder à pergunta
      1