Many people have commented that there is a lot of legacy code and outdated practices. This is true. However, since upper management within R&D has been shaken up, a large amount of investment is being made in infrastructure and dev practices.
The talent level (at least within my team) is absolutely top-notch.
Difficult and interesting problems.
If you don't like your team, you can move every 18 months.
Very flat hierarchy.
BDE software development methodology.
Amazing guest sparkers.
Increasing its contributions to the open source world (see BDE on Github).
The compensation is good if you are seen as a top performer.
Great health care.
I'm very happy to work for an organization that cares as much about its employees as Bloomberg. I think the company is on a positive trajectory, and the best is yet to come.
Continue to invest in developer productivity and training.
At least within my team, there is always more work to be done than could ever get done. Our project management and bug tracking systems could really use some TLC. Also, we build software like complete amateurs; we should invest in better build management tools. We could also use better automated testing frameworks and facilities.
Improvements are being made; it would just be nice to have a greater emphasis placed on unit and acceptance testing.
I was given two LeetCode problems of medium difficulty. I was able to solve the first, and while in the process of solving the second, I was interrupted by the interviewer. He pushed on his solution, questioning if I was taking too long. In the midst
Email exchange to schedule a telephonic round. I needed a laptop to code in HackerRank. There was a guy called Alex, who worked in the MARS team. He explained to me that it was not a quant or maths-related role.
HackerRank + Phone Interview I had a HackerRank code pair which was shared with the interviewer. The interview was quite interactive and friendly.
I was given two LeetCode problems of medium difficulty. I was able to solve the first, and while in the process of solving the second, I was interrupted by the interviewer. He pushed on his solution, questioning if I was taking too long. In the midst
Email exchange to schedule a telephonic round. I needed a laptop to code in HackerRank. There was a guy called Alex, who worked in the MARS team. He explained to me that it was not a quant or maths-related role.
HackerRank + Phone Interview I had a HackerRank code pair which was shared with the interviewer. The interview was quite interactive and friendly.