Software Engineer 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.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer 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 Engineer 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 5 weeks. I interviewed at Bloomberg (New York, NY) in Mar 2017
Interview
This is for the 2017 Software Engineer position. 45 minutes technical phone interview and then an in-person interview. Interviewer failed to call me twice which caused the process to take longer. Recruiter did everything via email which was bad. I wish I had an initial call to understand what the job entails and how the program is setup and ask question before the technical phone screen. Wouldn't interview with this company again because the entire interview process was messy and I was disappointed because I like the company. I found out that the first 3 months of the job is all training(getting to know the company, learning some languages and technologies), then there's a presentation from different teams, you later have to select one which you'd like to join after training.
Interview questions [1]
Question 1
Why Bloomberg? Tell me about yourself and what you do? Given 11000111, output how far each 0 is from the current index. So output should be 21000123
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.