Pay is good. Business is slowing down now, but even during the financial crisis, I got pretty good pay and bonuses. A lot of my coworkers quit and work for Google, and they're getting less vacation and about the same salary.
Good benefits. Four weeks vacation, good medical and dental insurance (used to be free, but now it's $400 a year or so), and other perks like free entrance to museums and occasional tickets to high-society type events through the company's philanthropy.
Nice office in a nice location, with beautiful tropical fish and free snacks.
The technologies they are using are outdated and mostly proprietary. You can become an expert in those technologies, and it will make you more valuable to Bloomberg, but not to anyone else. Perhaps not if you work in a few groups (mobile, bloomberg.com, Bloomberg Government) which use mainstream technologies, but the vast majority of programmers are working on the Bloomberg Terminal, which doesn't really use any modern, marketable technology.
Good job security has a price: there are a lot of really bad programmers who break things or never get any work done, and they never get fired. Depending on your team, you could work with smart people, but you might also work with a lot of dumb people.
Hours can be long, and you're pretty much expected to be on-call 24/7, ready to log in and debug issues at 4 AM when the London market opens. It's a global business, but most software teams are only in New York, and in some teams, you can get woken up very frequently to fix overseas issues.
The biggest thing is to upgrade the technology so developers don't feel like they're wasting their lives becoming experts in all this proprietary stuff. I know Bloomberg was way ahead of its time, but the Internet has caught up and surpassed us, and there's a lot of good technology we could be using and building our value as programmers at the same time.
The phone interview was mundane and consisted of typical Data Structures and "tell me about your projects" type of questions. One good question was: When does the compiler necessarily not make a function marked `inline` actually inline? I was also a
The first round interview was 2:1 where they asked a few data structures, algorithms, and a bunch of standard brain teasers. The second round interview was with a senior developer where he asked more programming-based questions, asked to write Java c
Initially, there was a C++ skills test. I had completed enough free Brainbench C/C++ tests, which really helped me a lot. In fact, I noticed some of the questions were identical to those from the Brainbench tests, and I even remembered some of the an
The phone interview was mundane and consisted of typical Data Structures and "tell me about your projects" type of questions. One good question was: When does the compiler necessarily not make a function marked `inline` actually inline? I was also a
The first round interview was 2:1 where they asked a few data structures, algorithms, and a bunch of standard brain teasers. The second round interview was with a senior developer where he asked more programming-based questions, asked to write Java c
Initially, there was a C++ skills test. I had completed enough free Brainbench C/C++ tests, which really helped me a lot. In fact, I noticed some of the questions were identical to those from the Brainbench tests, and I even remembered some of the an