Ir al contenidoIr al pie de página
  • Empleos
  • Empresas
  • Sueldos
  • Para empresas

      Impulsa tu carrera profesional

      Averigua cuánto podrías ganar, encuentra el empleo perfecto y comparte información sobre tu vida laboral y personal de forma anónima.

      employer cover photo
      employer logo
      employer logo

      Bloomberg

      Empresa activa

      Información
      Opiniones
      Sueldos y beneficios
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Opiniones sobre Bloomberg | Ofertas de empleos en Bloomberg | Sueldos en Bloomberg | Beneficios en Bloomberg
      Entrevistas de BloombergEntrevistas para el puesto de Senior Software Engineer en BloombergEntrevista de Bloomberg


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empresas

      • Cuenta gratuita de empresa
      • Centro de empresas

      Información

      • Ayuda
      • Normas
      • Condiciones de uso
      • Privacidad y opciones de anuncios
      • No vender ni compartir mi información
      • Herramienta de consentimiento de cookies

      Trabaja con nosotros

      • Anunciantes
      • Empleo
      Descargar aplicación

      • Buscar por:
      • Empresas
      • Empleos
      • Ubicaciones

      Copyright © 2008-2026. Glassdoor LLC. «Glassdoor», «Worklife Pro», «Bowls» y sus logotipos son marcas comerciales registradas de Glassdoor LLC.

      Empresas seguidas

      Sigue a tus empresas favoritas para estar al tanto de las últimas oportunidades y disponer de información de primera mano.

      Búsquedas de empleo

      Recibe recomendaciones y actualizaciones personalizadas al iniciar tu búsqueda.

      Entrevista de Senior Software Engineer

      15 mar 2025
      Candidato de entrevista anónimo
      New York, NY
      Sin oferta
      Experiencia negativa
      Entrevista difícil

      Solicitud

      Solicité el puesto a través de un captador. El proceso duró 3 semanas. Acudí a una entrevista en Bloomberg (New York, NY) en mar 2025

      Entrevista

      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.

      Preguntas de entrevista [1]

      Pregunta 1

      Leetcode medium/medium hard questions, low level design question
      Responder pregunta
      1

      Otras opiniones sobre las entrevistas para el puesto de Senior Software Engineer en Bloomberg

      Entrevista de Senior Software Engineer

      6 may 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista difícil

      Solicitud

      Acudí a una entrevista en 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 de Sr. Software Engineer

      21 abr 2026
      Candidato de entrevista anónimo
      New York, NY
      Sin oferta
      Experiencia positiva
      Entrevista normal

      Solicitud

      Acudí a una entrevista en 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 de Senior Software Engineer

      14 may 2026
      Candidato de entrevista anónimo
      Sin oferta
      Experiencia negativa
      Entrevista difícil

      Solicitud

      Solicité el puesto por otro medio. Acudí a una entrevista en Bloomberg en abr 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.

      Preguntas de entrevista [1]

      Pregunta 1

      Build whatsapp from a system design perspective.
      Responder pregunta
      1