The work environment is reasonably pleasant, although it does feel like a corporate job. You get a desk in an open floor space, but there's plenty of places to find a little "retreat" to think or relax during the day. Flowers and an aquarium contribute to making the very glass-like structure more "organic". The kitchen is always stocked with drinks and snacks, including late nights and weekends if you really have to stay and finish a project.
The Bloomberg annual parties are legendary and really fun (although if they gave us the money they spend on those, I'm sure I'd have been happier - they must be very, very expensive!). There are a few perks working for a large employer, like a savings program.
My boss gave us plenty of latitude to get the work done, and apart from the occasional crunch time, work was not overly stressful. This varies widely by department, though. My co-workers were top-rate. Again, this varies widely depending on what team you're with.
This was my first job out of academia (I used to teach before), and although I was an accomplished programmer, I still learned a lot about software and engineering.
The software environment is both challenging and very peculiar to the company, though. A lot of it is legacy, which means having to work within a set of constraints (binary compatibility with 1990s Fortran code, code relocatibility, proprietary routines) which I can pretty much guarantee you will not find anywhere else. Because of those constraints, moving code through to production is a major pain. On some particularly central class I was tasked to optimize, my changes took 6 months to percolate through to the production environment.
The bureaucracy is also sclerotic. Having to document your working hours and bill them to various tickets (development, bug fixes, etc.) gets quickly tiring and meaningless, as the fudge factor for accounting for 8 hours a day makes charging completely arbitrary. Getting a TREQ (technical request for new projects) can be a pain. All this is done through the Bloomberg terminal, which means there is nowhere to hide: your boss (but also pretty much anyone in the company) can find out about all the commands you typed during the day. The terminal has quirks too, and I can't count how many times I lost a long typed message because of a wrong keystroke.
But the reason I eventually left is that once you're in, the possibilities for raising your salary are limited. You will do well to negotiate the highest you can on entry; it's unlikely to rise significantly after that. Your first-year bonus is invested/managed by the company into internal stock (BB is private), and you only see it in your bank account after the end of the second year (with moderate interest). The value of the internal stock can be tracked using another Bloomberg terminal function, so at least it's transparent. That means, of course, when you leave, they get to keep your current-year bonus – the one they are still "managing" for you. This is described by the employer as an incentive for you to invest in the company. The longer you stay, the better. Unfortunately, it makes leaving that much more painful.
Until recently, there was an unwritten policy that they would not rehire previous employees. I hear that's been rescinded. Having left all that behind, though, I can't really think of why I'd want to go back.
The first conversation was with an internal recruiter. The next one was a coding interview. The coding exercise involved one of the team members. They presented the first exercise, and after it was completed, the second exercise was presented. You h
Good interview process. Interview questions are very relevant to the role. Coding is a very big part of the interview, irrespective of the team. System design questions are more relevant and team-based.
The interview was pretty straightforward, but they demanded more accurate answers. I was contacted by a recruiter and opted for an interview two months later in order to prepare. I bombed the online assessment.
The first conversation was with an internal recruiter. The next one was a coding interview. The coding exercise involved one of the team members. They presented the first exercise, and after it was completed, the second exercise was presented. You h
Good interview process. Interview questions are very relevant to the role. Coding is a very big part of the interview, irrespective of the team. System design questions are more relevant and team-based.
The interview was pretty straightforward, but they demanded more accurate answers. I was contacted by a recruiter and opted for an interview two months later in order to prepare. I bombed the online assessment.