Process
I applied online and was then invited to a phone interview.
I scheduled the phone interview, but the interviewer never called me. I emailed the recruiter, and we rescheduled.
Although the problem wasn't very difficult, my interviewer was very blunt and condescending, leading to an overall terrible experience. He would question me in a very curt way whenever I said something, even if it was correct.
He also mumbled a lot, making it difficult to hear what he was saying.
They followed up with a rejection email a week later. Overall, an unpleasant experience.
Questions
Model returning the last X pages in a user's browser history.
Was this helpful?
Interview Statistics
The following metrics were computed from 51 interview experiences for the Bloomberg LP Software Engineering role in United States.
Success Rate
Bloomberg LP's interview process for their Software Engineering roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Bloomberg LP's Software Engineering interview process in United States.
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.
- 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
- 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.
Bloomberg LP Interview Questions
