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 through a staffing agency. The process took 1+ week. I interviewed at Bloomberg (Dublin, Dublin) in Dec 2015
Interview
3 round process for a Java development role. First one was a technical telephonic interview. I flew through it. 2nd was a technical test which I had to complete an assignment, which I completed in time and they called me for a face 2 face at their Dublin office. I had to travel to Dublin for about 2 hours from where I was located. They turned me down after three rounds. Reason given : "Technical assignment was not up to their expectations" which is BS because that shows they didn't even bother to review the assignment before calling a candidate for f2f round. The guy at the interview said he wasn't able to find the eap server which I have used in the assignment. Funny when you say that when the used eap is available open source. That shows they didn't try to run the assignment once in their system before calling for a f2f. No offence. But these are pretty basic things you can do when you interview people.
Interview questions [1]
Question 1
how will you find a circular link list which has a loop in it.
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.