Skip to contentSkip to footer
  • Community
  • Jobs
  • Companies
  • Salaries
  • For employers
      Notifications

      Loading...

      Elevate your career

      Discover your earning potential, land dream jobs, and share work-life insights anonymously.

      employer cover photo
      employer logo
      employer logo

      Bloomberg

      Engaged employer

      About
      Reviews
      Pay and benefits
      Jobs
      Interviews
      Interviews
      Related searches: Bloomberg reviews | Bloomberg jobs | Bloomberg salaries | Bloomberg benefits | Bloomberg conversations
      Bloomberg interviewsBloomberg Senior Software Engineer interviewsBloomberg interview


      Glassdoor

      • About / Press
      • Awards
      • Blog
      • Research
      • Contact Us
      • Guides

      Employers

      • Free Employer Account
      • Employer Centre
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy and Ad Choices
      • Do Not Sell Or Share My Information
      • Cookie Consent Tool
      • Security

      Work With Us

      • Advertisers
      • Careers
      Download the App

      • Browse by:
      • Companies
      • Jobs
      • Locations
      • Communities
      • Recent posts

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" and logo are proprietary trademarks of Glassdoor LLC.

      Company Bowl sample

      Want the inside scoop on your own company?

      Check out your Company Bowl for anonymous work chats.

      Bowls

      Get actionable career advice tailored to you by joining more bowls.

      Followed companies

      Stay ahead in opportunities and insider tips by following your dream companies.

      Job searches

      Get personalised job recommendations and updates by starting your searches.

      Senior Software Engineer Interview

      14 Dec 2014
      Anonymous employee
      New York, NY
      Accepted offer
      Positive experience
      Difficult interview

      Application

      I applied through a recruiter. The process took 3 weeks. I interviewed at Bloomberg (New York, NY) in June 2014

      Interview

      Recruiter submitted my resume for two groups. There was one phone and two face to face interviews per group. In each round I was asked to write code. Concepts and questions asked were basic but they would mostly keep grilling on same question a lot changing the problem statement a little here and there. I would advise candidates to go through basic concepts of C++, and be prepared to write code which is almost accurate on syntax and logic, like implementing smart pointers. And be prepared on whatever is mentioned on resume, projects and specific technical challenges faced. A few times the challenges I mentioned were turned into coding questions too. All in all, I dont think Bloomberg C++ interview is too difficult to prepare for, I wasnt asked complex puzzles checking how out-of-the-box can i think, they seem to be concerned if u can code or not, not if u r a code guru.

      Interview questions [1]

      Question 1

      The one question i could not code properly: 'write a class for implementing big numbers, really big, which cant be stored in built in types, and all operations involving numbers.' I did write something but it did not look efficient enough.
      Answer question
      3

      Other Senior Software Engineer interview reviews for Bloomberg

      Senior Software Engineer Interview

      6 May 2026
      Anonymous interview candidate
      No offer
      Negative experience
      Difficult interview

      Application

      I interviewed at Bloomberg

      Interview

      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

      Sr. Software Engineer Interview

      21 Apr 2026
      Anonymous interview candidate
      New York, NY
      No offer
      Positive experience
      Average interview

      Application

      I interviewed at Bloomberg (New York, NY)

      Interview

      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

      Senior Software Engineer Interview

      14 May 2026
      Anonymous interview candidate
      No offer
      Negative experience
      Difficult interview

      Application

      I applied through other source. I interviewed at Bloomberg in Apr 2026

      Interview

      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.

      Interview questions [1]

      Question 1

      Build whatsapp from a system design perspective.
      Answer question
      1