I applied online and received an email to schedule a phone interview a few days later.
The phone screen went very well. The process was fairly conversational, and we solved an easy LeetCode problem together. The interviewer offered great insight into her experience as a software engineer at Bloomberg. I received an email to schedule the virtual onsite the day after.
The virtual onsite consisted of two hour-long interviews with two engineers each.
In my first interview, I was asked two LeetCode questions: one easy and one medium. One of the engineers was very off-putting and didn't seem all that interested in my character or my background. He asked vague questions, and when I asked clarifying questions as a follow-up, he seemed annoyed.
My second interview, in contrast, was pleasant. It was more conversational, with some space to convey my technical knowledge. I was asked an open-ended question regarding data structures, then a LeetCode easy problem at the end. I was told at the end of the interview that it would be my last for the day, which, based on my research, indicates a rejection.
Overall, my experience interviewing at Bloomberg was good. It seems that the interviewers and recruiters care about conveying a positive image of the company. I had a few takeaways coming out of the interview:
Best of luck to those who are interviewing. I would emphasize to you all to be collaborative and communicative.
Determine if a string has valid parentheses.
The following metrics were computed from 2 interview experiences for the Bloomberg LP Software Engineer Entry Level role in New York, New York.
Bloomberg LP's interview process for their Software Engineer Entry Level roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Bloomberg LP's Software Engineer Entry Level interview process in New York, New York.