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 Developer 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 Developer

      2 oct 2015
      Empleado anónimo
      Londres, Inglaterra
      Oferta aceptada
      Experiencia positiva
      Entrevista fácil

      Solicitud

      Solicité el puesto a través de una agencia de empleo. El proceso duró 3 meses. Acudí a una entrevista en Bloomberg (Londres, Inglaterra) en jun 2015

      Entrevista

      I applied for a C++ Software Developer position in May and successfully passed an interview process by the end of June. The process itself was pretty much generic: a technical phone interview, then 3 technical on sites, then, if you passed the previous steps, an HR interview. Really, you can read about it in every single review here, and the HR interview is pretty standard in all companies, so instead I'd like to focus on the technical questions they asked me. Please refer to the Interview Questions section to see the first 5. As glassdoor does not allow to add more there, I'll describe the subsequent questions below. First on site 3. Implement a thread-safe cache for objects which are expensive to copy, provide lookup, insert and delete operations. Here you basically have to combine std::unordered_map, std::mutex and std::shared_ptr into a single class. std::shared_ptr is used to make sure threads do not keep pointers to deleted objects. unordered_map and mutex should be obvious. I have also told it's possible to use read-write locks or atomic variables to synchronize access, depending on our usage patterns. Second on site 1. Two standard brain teasers: boxes with wrong labels and searching for a coin which is heavier than others. Easy. Second on site 2. How to find whether a singly linked list has a loop or not. A standard slow/fast runner problem, described in every book. Third on site. There were no questions at all, it was more like a conversation about the ways of profiling an application on UNIX systems to understand its memory allocation patterns, space-time trade-offs, overriding malloc/free, etc. I think they just did not want me to sit alone for 30 minutes waiting for an HR to come from a meeting, your mileage may vary. The day after I had a video conference with New York, which happened to be another friendly chat without any questions whatsoever, and I got an offer. Frankly speaking, I spent way more time waiting for a visa and background check results than preparing for and passing the interview itself. I suggest you using "Elements of Programming Interviews: The Insiders' Guide" as your preparation book and believe it covers all topics you need to answer their general coding question. Good luck :P

      Preguntas de entrevista [5]

      Pregunta 1

      Phone interview 1. Remove duplicates from an unsorted singly linked list.
      1 respuesta

      Pregunta 2

      Phone interview 2. Tell whether there is anything wrong with the code you see.
      1 respuesta

      Pregunta 3

      Phone interview 3. Tell what's the output of the program you see.
      1 respuesta

      Pregunta 4

      First on site 1. A question about C++ templates.
      1 respuesta

      Pregunta 5

      First on site 2. A question about bitwise operations.
      1 respuesta
      8

      Otras opiniones sobre las entrevistas para el puesto de Senior Software Developer 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