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 & benefits
      Jobs
      Interviews
      Interviews
      Related searches: Bloomberg reviews | Bloomberg jobs | Bloomberg salaries | Bloomberg benefits | Bloomberg conversations
      Bloomberg interviewsBloomberg Financial Software Engineer interviewsBloomberg interview


      Glassdoor

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

      Employers

      • Free Employer Account
      • Employer Center
      • Employers Blog

      Information

      • Help
      • Guidelines
      • Terms of Use
      • Privacy & 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 personalized job recommendations and updates by starting your searches.

      Financial Software Engineer Interview

      Nov 2, 2011
      Anonymous employee
      New York, NY
      Accepted offer
      Positive experience
      Easy interview

      Application

      I applied through college or university. The process took 3 days. I interviewed at Bloomberg (New York, NY) in Oct 2011

      Interview

      The process consisted of three separate interviews on subsequent days with three separate Software Developers and Team Leaders at Bloomberg. It primarily consisted of questions designed to ascertain my programming knowledge and ability to code on the fly. Questions varied from the specific, such as, how would you code a least common multiple algorithm, how would you detect a loop in a linked list. To the more general, such as given a very abstract high level diagram of the Bloomberg Terminal, and asked how you would setup and improve the communication between the Bloomberg and it's Clients. Since I primarily applied with a PhD in statistics, a few questions on financial mathematics were included, such as what is the Black-Scholes model, what are it's weaknesses, what models would you suggest, what do you mean by fat tails? However since it was obvious rather quickly my statistical knowledge was far fresher and more up to date then my coding ability, which had been dormant for around five years, they didn't spend too much time on the Statistics side of the questions. The interview ended with a brief one on one with a person from H:R that asked me some of the standard questions you see on "online interview aids". Like why do you want to work at Bloomberg, and I see you've got extensive teaching experience, do you plan to go into Academia. What other areas are you applying to other then Finance, etc. The bulk of the interview process, thus contained mainly knowledge based questions unrelated to what you find in most interview help books and resources.

      Interview questions [2]

      Question 1

      How would you detect a loop in a linked list? This was a technical question, finding the answer was difficult since I forgot how linked lists worked, but the interviewer didn't mind helping out with hints and guiding me along. They weren't, obviously interested in the exact answer, but how my thinking works
      1 Answer

      Question 2

      How would you find bugs in a very large program. This is one of the few questions I wasn't able to answer to my satisfaction at least, since I hadn't worked with large programs and were still limited to small simple debugging techniques
      1 Answer
      2