Software Developer applicants have rated the interview process at Bloomberg with 3.1 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 53% positive. To compare, the company-average is 54.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Developer roles take an average of 22 days to get hired, when considering 1,459 user submitted interviews for this role. To compare, the hiring process at Bloomberg overall takes an average of 23 days.
Common stages of the interview process at Bloomberg as a Software Developer according to 1,459 Glassdoor interviews include:
Phone interview: 33%
One on one interview: 22%
Skills test: 17%
Group panel interview: 10%
Presentation: 9%
Background check: 3%
IQ intelligence test: 2%
Personality test: 2%
Other: 2%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1+ week. I interviewed at Bloomberg (London, England) in Nov 2015
Interview
Had a phone interview with a developer about a week after applying. The questions were pretty standard, mostly about very technical details of C++. After that I got two easy coding questions (1. what is the output of the following code, 2. implement an easy function).
The interviewer didn't give any signs of expecting other or more detailed answers and generally seemed to be satisfied. He told me I would get a feedback in a week.
Two days later I saw on Bloomberg's job site that the status of my application was changed to No Longer Being Considered but I didn't get any emails about this (not even an automated one).
I sent a polite email to the recruiter asking if she could share any information about why my application has been rejected and got no answers at all.
Not providing any details about the reasons of the rejection is something I don't like but I can accept.
But never contacting a candidate again after a phone interview just feels unprofessional.
Interview questions [1]
Question 1
Implement a function that counts the duplicates in an unordered array
Phone screen went very well, i passed to the onsites and they gave me the problem statement and i proposed a sub-optimal solution. They told to me come up with more optimal solution and didn't give me much time to think about it. They got impatient and gave me a hint. I figured it out and solved the problem, but apparently they thought I needed hints, which I didn't ask for.
15 minutes talking about resume, 45 minutes for 2 medium leetcode style coding questions (using code share), the interviewer was very friendly and communication is even more important than passing all test cases.
Overall, it was a positive and professional interview experience, though the interviewer was on the stricter side. Unfortunately, I was dealing with an illness and wasn't able to prepare as thoroughly as I wanted to, which left me feeling a bit off throughout the conversation. Despite not feeling my best and facing a tough interviewer, the process was well-structured.