- Career Opportunities. Now this depends on individuals' goals, but from coming from a small company in the financial industry, I've found that opportunities here are very limited. After you've worked in the industry for some time, projects complete, and they turn into maintenance mode (aka "keeping the lights on") in the company. This is very necessary evil since once functions complete, support needs to remain for the function, but this lowers the amount of meaningful work that can be done. Those that want to change things up will generally be pointed towards the direction of management.
- Challenges. This expands on the above point. Unfortunately, the amount of challenges in this company are very limited. The problems can be difficult, but with the wrong reasons. This includes challenges from compliance, poor design, and complex internal architecture. There's significantly less "fun" challenges in the work compared to a startup or smaller shop. This can lead to some days that feel terribly long due to working on mind-numbing tasks. All companies will have these tasks, but Bloomberg seems to have a lot more do to their extensive use of proprietary tools.
- Legacy technologies. Bloomberg is involved with "modern" technologies like Hadoop/HBase and Redis, but a very large portion of the foundation software is still C++98 (with a Bloomberg Standard Library to cover some of the C++11 features), but the technology lags behind significantly due to all the dependencies in the software.