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.8% 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,458 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,458 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 college or university. I interviewed at Bloomberg (New York, NY)
Interview
Turned in resume at Career fair and filled out online application. Was contacted about the phone interview a few months later. On site interview was scheduled awhile after that. Only one interviewer for phone interviewer, but onsite had 2 rounds with 2 interviewers each.
Talking with some other candidates I probably should have been given another question during round 2, but I (presumably) ran out of time. We were also given a tour of the building prior to starting the 2 interview rounds.
Overall process took many months, with the career fair/application being in September, phone interview in early November, and on site being in mid January.
Interview questions [5]
Question 1
(Phone Interview)
Given a binary tree (showed an example of said binary tree), and a specific node, find the next larger node in the tree
(On Site)
Given a single linked list with both a next pointer pointing to the next node, and a "random" pointer pointing to a random node in the single linked list (including itself as an option), perform a deep copy of said linked list.
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.