A great experience, if you get the right team
A great experience, if you get the right team
If you get the right team, you'll be working with modern tools and encouraged to contribute to inner source.
A supportive environment. A lot of access to continuing education, volunteering, and benefits.
Clear boundaries and responsibilities, an energetic environment.
Very technically capable employees (collaborative growth).
Good pay.
Internal mobility is now encouraged.
If you get a bad team or a bad legacy project, it can be a horrible experience. I've seen several talented engineers get frustrated at the lack of impetus to improve existing systems.
Business often bleeds its responsibilities into engineering, leading to rushed projects or bad decisions because non-engineers are driving the conversation. A lot of internal forks of third-party projects or dated Bloomberg implementations of existing tech (related to the above, fortunately changing). Normal trappings of internal politics expected of large organizations.
Not much, a lot of these cons are slowly being addressed. Engineering heads are pushing for better practices. If anything, pinpoint bad engineering managers and reshuffle them. Emphasize that engineering is ultimately in charge of leading project implementation decisions, and they're encouraged to push back on business when demands are unreasonable.
Was this helpful?
Bloomberg LP Interview Questions
Bloomberg LP Interview Experiences
Software Engineering
It was a first round of a LeetCode problem, where we talked through our past experiences. After that, the next round consisted of three different interviews, each with one LeetCode problem.
Software Engineering
This was my first round. I was scheduled for this HackerRank live coding interview within two weeks of applying. The interviewer was not helpful at all with answering follow-up questions. He stated he was not allowed to do that.
Software Engineering
I really enjoyed the interview process. It was in-person, so it was less intimidating since I could actually collaborate with the interviewer. The questions were a bit challenging, but working with the engineers and getting hints made it manageable.
Software Engineering
United StatesMay 7, 2025It was a first round of a LeetCode problem, where we talked through our past experiences. After that, the next round consisted of three different interviews, each with one LeetCode problem.
Software Engineering
United StatesNovember 8, 2022This was my first round. I was scheduled for this HackerRank live coding interview within two weeks of applying. The interviewer was not helpful at all with answering follow-up questions. He stated he was not allowed to do that.
Software Engineering
Cambridge, Massachusetts, United StatesSeptember 1, 2022I really enjoyed the interview process. It was in-person, so it was less intimidating since I could actually collaborate with the interviewer. The questions were a bit challenging, but working with the engineers and getting hints made it manageable.
