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 online. The process took 4 weeks. I interviewed at Bloomberg in Oct 2016
Interview
As a new grad with offers from Google, Facebook, Goldman Sachs and their ilk (as well as a previous offer from Bloomberg which I turned down), I can say with complete confidence that this was the most incompetent interviewer I've ever encountered.
Even the logistics were embarrassing. He called me more than twenty minutes late, completely unapologetically. And that was only because I emailed HR asking if the interview was still on. Unlike most, this interview's coding section went flawlessly. The question was trivial and its implementation was too. The interviewer seemed constantly confused by design choices (and generally unlikeable, although that may not be relevant). He then proceeded to ask me questions about topics which were not on my resume, some of which I had (by chance) happened to take classes on, and some of which I knew almost nothing about. The experience left me with only two words to say: good riddance.
The technical interview questions to come in a separate post.
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.