Software Engineering Interview Experience - New York, New York
Process
Applied online and sent my resume. I could have applied and interviewed on campus, which would have been much quicker.
I went through one screening phone interview and one on-site visit, which consisted of three technical and one HR interview.
Interestingly, two out of the three on-site interviews did not involve coding at all. Instead, they focused on broad design questions inspired by actual Bloomberg work. However, all the engineers were really nice and approachable. They made me feel comfortable expressing my thoughts, even if they weren't the best approaches.
Questions
Design questions about the best way to store the company's data in order to maximize efficiency for certain tasks, such as sorting by different indices and categorizing stock.
Was this helpful?
Interview Statistics
The following metrics were computed from 9 interview experiences for the Bloomberg LP Software Engineering role in New York, New York.
Success Rate
Bloomberg LP's interview process for their Software Engineering roles in New York, New York is fairly selective, failing a large portion of engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Bloomberg LP's Software Engineering interview process in New York, New York.
Bloomberg LP Work Experiences
- 5.0Great Balance, No DownsidesSoftware Engineering • Current EmployeeNew York, New York, United StatesDecember 10, 2023Pros: Nice company, good work-life balance.Cons: I don't see any downsides.
- 4.0A great experience, if you get the right teamSoftware Engineering • Current EmployeeAugust 19, 2018Pros: 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.Cons: 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.
- 5.0Great workplaceSoftware Engineering • Current EmployeeNovember 4, 2022Pros: Good pay. Nice work environment. Good benefits. Not sensitive to the market.Cons: Peer pressure: No free lunch
Bloomberg LP Interview Questions
