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 -
The process took 4 weeks. I interviewed at Bloomberg (Salt Lake City, UT) in Aug 2021
Interview
(Interviewed early August 2021)
Take this with a grain of salt because I'm sure other people have had positive experiences interviewing at Bloomberg. I did not at all.
Got a technical phone screen. Interview was cancelled multiple times and usually within minutes of the actual interview. Third time around, I get what I would describe as an intelligent person with 0 interviewing skills or etiquette. Talks to me about a simple easy/med LC problem, and I verbally gave my solution (he didn't want the implementation). Asked probably 12 follow up questions which I thought were pedantic at best. Asked me to implement a solution for a modified version of it (probably LC hard) with 20 mins left. I talked through two approaches and as I was heading one way, he pointed me in another - totally fine. I still had ~20 minutes left at this point considering the amount of follow up questions/discussion he gave but I felt confident in how I was going to implement it. I could not initialize a variable without him questioning the "Why?" Look I get it - you want to understand my thought process but if you give me twenty minutes to implement an fairly tough solution, limit your follow up questions to after I'm done typing a variable. I certainly had gaps in my knowledge (which I am focusing on improving as a 'positive' of this experience) but he talked about how it should be done as I was typing it, as if I were implementing it in a different way. Super bizarre. Walked out solving the problem but could tell he was not very pleased with the performance (he seemed apathetic to my follow up questions about the company). I think (and hope) my situation was a one-off case but my advice to HR: Have more robust training for your interviewers. I've had experiences where I've been rejected since I couldn't solve a problem but the interviewers were sincerely good at helping me approach it in the right direction and were clearly trained. I've also gotten acceptances without getting the exact best solution. But this... I won't forget this.
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.
Fairly simple. Phone call then onsite. For onsite it was 10 min office tour follow by 1 hr interview then 1 hours system design and 30 mins manager interview. Interviewers were nice and the recruiter was accommodating.
5 rounds first 3 being leetcode coding ones and the last 2 being behavioral. The first three are the hardest asking mainly taggeed questions and the rest are not that bad