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

      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

      Empleador activo

      Información
      Evaluaciones
      Pago y prestaciones
      Empleos
      Entrevistas
      Entrevistas
      Búsquedas relacionadas: Evaluaciones de Bloomberg | Empleos en Bloomberg | Sueldos en Bloomberg | Prestaciones en Bloomberg
      Entrevistas en BloombergEntrevistas para el cargo de Senior Software Engineer en BloombergEntrevista en Bloomberg


      Glassdoor

      • Acerca de
      • Premios
      • Blog
      • Contacto

      Empleadores

      • Cuenta de empleador gratuita
      • Centro de empleador

      Información

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

      Trabaja con nosotros

      • Anunciantes
      • Oportunidades laborales
      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 desde adentro.

      Búsquedas de empleo

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

      Entrevista para Senior Software Engineer

      10 may 2026
      Candidato de entrevista anónimo
      Sin ofertas
      Experiencia neutra
      Entrevista difícil

      Solicitud

      Me postulé en línea. Acudí a una entrevista en Bloomberg en mar 2026

      Entrevista

      Applied online, then had usual HR screen screening and several remote interviews. I applied for 3 roles, but you can only interview for 2 simultaneously, which I did. First were two online coding rounds. Not too hard, roughly Leetcode medium, but be sure you can tell the big-O complexity of algorithms and containers you are using, they will ask. Then I had a system design interview with one of the teams which a failed. A typical system design problem, but I never had this kind of interview and was very rusty on db-centric apps. I asked for a couple of weeks to prepare before doing one for the second team. They agreed, but ran me through another live coding interview before the second system design one. The coding was another Leetcode medium which I think went OK-ish, but the system design was not what I expected. They presented a slide with their real system and asked questions around it. I think I gave OK-ish answers and the vibe was good, but still got a rejection email same day. What was disappointing is that someone with finance trading/experience would clearly have a significant advantage with such a design problem. Since they don't even mention finance experience in job ads, I felt it was unfair. So anyone interviewing should take time to learn about the team and system design problems relevant to their work. Recruiter communication could be improved also, they did not make it clear which interviews are scheduled on site, did not respond to my email feedback request.
      2

      Otras evaluaciones sobre las entrevistas para el cargo de Senior Software Engineer en Bloomberg

      Entrevista para Senior Software Engineer

      6 may 2026
      Candidato de entrevista anónimo
      Sin ofertas
      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 para Sr. Software Engineer

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

      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 para Senior Software Engineer

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

      Solicitud

      Me postulé a través de otra fuente. 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