Drawing points for Bloomberg:
At work, you'll be working with some very intelligent people, some known widely throughout the industry. It's also nice to work for a company that is the industry leader in financial data and news; it blows all competitors out of the window.
Depending on your personality, you may or may not like the fact that the pace at Bloomberg is very fast. Unlike traditional software companies, where time is spent on requirements gathering and design, Bloomberg emphasizes time to market and getting things out the door. Software moves once a week, not once a year like other companies.
The technology is ancient (the majority). A lot of programmers are simply maintaining legacy code (Fortran, C) that cannot be retired or converted.
The company also uses a ton of proprietary software, all developed in-house. For example, they've created their own Service-Oriented Architecture (ala WSDL), two homegrown databases, an entire UI framework, and other things.
It's very easy to get "stuck" at Bloomberg because you might be using proprietary tools 75-90% of your day. Also, there is an entire lack of structure when it comes to the software development cycle.
Projects are handed out with no formal written documentation; let me repeat, NO formal written specs! There is also NO official testing (no QA teams whatsoever!). The programmer is expected to perform the testing of their applications.
Put in some people that worry more about doing things right than bottom-line numbers.
Morale is somewhat low in certain groups.
Multiple rounds of technical interviews. Didn't get passed round one despite answering all the questions and any followups they had. It was two LeetCode questions, and you would write out your code on a HackerRank interface.
Had three rounds. Be sure to speak more! Communication matters. It's okay if you do not have clues at first, but you need to talk to them about how you think of the problem, and they will guide you through it.
It was a straightforward experience. I talked about my resume for around 10 minutes and then solved a LeetCode-style question. Afterwards, there was an opportunity to ask the interviewer questions about Bloomberg.
Multiple rounds of technical interviews. Didn't get passed round one despite answering all the questions and any followups they had. It was two LeetCode questions, and you would write out your code on a HackerRank interface.
Had three rounds. Be sure to speak more! Communication matters. It's okay if you do not have clues at first, but you need to talk to them about how you think of the problem, and they will guide you through it.
It was a straightforward experience. I talked about my resume for around 10 minutes and then solved a LeetCode-style question. Afterwards, there was an opportunity to ask the interviewer questions about Bloomberg.