Working with extremely intelligent, kind, and dedicated people.
Learning opportunities never cease in either financial or technical domains.
Salary and benefits are unbelievable.
The name is well-respected in the financial world.
Very tolerant and patient with new developers.
Offices throughout the world can make travel a lot of fun.
By virtue of being such a large company with thousands of developers, Bloomberg can't always offer interesting projects to everyone, so it takes a long time to make tangible impact on a product.
Development is very slow because the developer tools are either nonexistent or impossible to use.
There are many incomplete home-brew solutions.
With that said, there has been a lot of effort to correct these issues and retain talent over the years.
There is not a lot of interaction between the various divisions of the company.
The team leaders are some of the most hard-working people in the company, and it's rare to see support from their managers.
The process started with visiting the Bloomberg LP booth at my university. I gave them my resume, and we discussed a project or two. I then asked if they were conducting interviews on campus, and they confirmed they were. Before I could secure a cam
First contact was with HR, where we discussed few technical topics and more about the resume. The second technical interview lasted for an hour and included the following questions: 1. Merging linked lists. 2. Detecting cycles in linked lists. 3. P
The process begins with basic buddy coding on one of many sites, alongside an engineer. This is followed by some basic personal questions, and then an in-person interview. The process itself is straightforward and standard, but that's about the only
The process started with visiting the Bloomberg LP booth at my university. I gave them my resume, and we discussed a project or two. I then asked if they were conducting interviews on campus, and they confirmed they were. Before I could secure a cam
First contact was with HR, where we discussed few technical topics and more about the resume. The second technical interview lasted for an hour and included the following questions: 1. Merging linked lists. 2. Detecting cycles in linked lists. 3. P
The process begins with basic buddy coding on one of many sites, alongside an engineer. This is followed by some basic personal questions, and then an in-person interview. The process itself is straightforward and standard, but that's about the only