Compensation is decent. The company offers nice benefits. The building is impressive and great to show off to others. Free snacks are a great perk.
Terrible place to work if you're interested in good software. If you're fortunate enough not to be working on Fortran or some really old, crappy C code, you still have to put up with an infrastructure that is from the 90s and maintain some ugly patchwork code.
Everything is run based on unreasonable demands from business folks who don't understand software, and you are constantly writing band-aid solutions and patching code.
Your software engineering skills will suffer. Most of the management (on the tech side) doesn't know what it takes to be a good leader and is interested in hitting project deadlines dictated by the business at any cost, without any regard for employee development.
The only people who can be happy working there are people who started working there out of college, have only seen this culture, and are happy at being well-compensated.
You will not be happy if you've seen the world outside those glass walls.
Do NOT go there as a senior engineer.
Understand that Bloomberg is primarily a tech company, as your main offering is software. If you want to keep delivering good quality and innovative software, you need good Software Engineers, not programmers. You cannot keep those guys happy just by compensation.
A good career path and intellectually stimulating work is extremely important for employee satisfaction.
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.