I started with a phone screen with a developer where I was asked some general interview questions. After that, I was passed to a multi-round interview.
From what I read, I believe the process would have been:
The first technical round was fairly easy, with some medium/easy LeetCode questions and questions to confirm my understanding of technical concepts on my resume.
I struggled in the second round. The problem itself was very easy, but unlike on LeetCode where you're given a clear input (e.g., an array of integers), I was asked to solve a problem to manage how many rooms I would need given a list of meeting times. I had a hard time imagining the list of times as an input I could use for a function. I offered a solution the developer thought was valid but not ideal. It was very clear he wanted me to come up with the solution he had in mind, but again, I was struggling with visualizing the input.
Overall, I would say the experience was a plus, since three of the four developers I talked to were polite and seemed interested in understanding my skills. But if you are stumbling on a question, try to ask the interviewer questions to see what they are trying to say, as I had a hard time with their wording.
Given a 2D array with some cells as pantries, find the steps to the nearest pantries.
You are given a list of meeting times with start and end times. Find the maximum number of rooms you need.
The following metrics were computed from 470 interview experiences for the Bloomberg LP Software Engineer role in New York, New York.
Bloomberg LP's interview process for their Software Engineer 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 interview process in New York, New York.