I applied online. The process took 4 weeks. I interviewed at Bloomberg (New York, NY)
Interview
Phone call, then onsite. The onsite consisted of 4 sessions.
The phone call wasn't too difficult, typical leetcode question.
The onsite consisted of 2 parts with a HM interviewer in between.
The first part consisted of 2 coding sessions each with 2 questions. I didn't manage to code the second problem of the first session, only provided a summary of the solution I had in mind.
Then there was a HM interview. Had a couple questions like "Why Bloomberg?" and the such.
The last interview was with an EM. He asked a brainteaser question which I wasn't prepared for and asked a couple of behavioral questions.
Interview questions [1]
Question 1
Variant of remove adjacent duplicates in string ii
I applied online. The process took 2 months. I interviewed at Bloomberg (London, England) in Jul 2021
Interview
Telephonic Round: LC medium question.
Video Interview Round: LC-easy question with time complexity analysis and followup.
System Design: Easy design question.
HR and Manager round: Behavioural question.
I liked their interview process except the fact that they really stretched out the time in informing me that my application was a reject. I had another existing offer which I had to accept/reject within 3-4 days, and I asked my recruiter at Bloomberg to expedite the process and inform me about the final decision within a week. But they really didn't care, and even after the final interview round, they took a long time to get back to me. It seemed they had already rejected me a while ago but just didn't care to inform me immediately.
Interview questions [1]
Question 1
LC easy-medium in coding rounds, a system design question about designing alter system. HR round involving leadership questions and "What do you expect to get out of working at Bloomberg?"
I applied online. The process took 2 weeks. I interviewed at Bloomberg in Aug 2021
Interview
Phone screening from HR. Tech interview over phone/web coding portal the following week.
Was pretty clear the interviewer was new to interviewing and very much an engineer. Gave a brainteaser-style coding task which would have no use in the team/product I was applying for and at the start somewhat misrepresented what he was looking for, which resulted in me wasting time producing something that was performant to spec but not what he wanted.
Also a little disappointed that the interviewer's line of questioning wasn't more practical and relevant to the job role - the required skills for the product are "soft" as far as development style goes - but I guess tech-bro gatekeeping is more important.
Interview questions [1]
Question 1
Something you'll probably find if you Google "coding tech interview".