Software Engineer applicants have rated the interview process at Bloomberg with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 52.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 5 days to get hired, when considering 1 user submitted interviews for this role. To compare, the hiring process at Bloomberg overall takes an average of 29 days.
Common stages of the interview process at Bloomberg as a Software Engineer according to 1 Glassdoor interviews include:
Phone interview: 50%
Background check: 50%
Here are the most commonly searched roles for interview reports -
One Phone Interview and one on-site interview.
The phone interview is about two weeks after I submitted the resume online. There was many basic questions about algorithm, data structure and design issue such as the difference between the implementation of hash-map and map. No coding is required.
After the phone interview, hr contacted me for on-site interview. But I haven't take that yet.
Interview questions [1]
Question 1
Design an data structure for several real applications
I applied through a recruiter. The process took 1 week. I interviewed at Bloomberg (New York, NY) in Jan 2013
Interview
Resume was submitted to Bloomberg One hour Phone Interview first with two engineers. Result was known same day after phone interview, then setup on site interview. On site interviews talking to two engineers. The phone interview questions are more about c++ plus some data structure and algorithm design; on site was all problem solving questions. Code writing with pencil and paper.
Interview questions [1]
Question 1
Given a binary tree of integer numbers, find the closest number to the given one.
I applied online. The process took 4 weeks. I interviewed at Bloomberg (New York, NY)
Interview
I submitted the application online, and they sent me an email asking my availability for a phone interview. The interviewer asked me about my past projects, etc. If I remember correctly, he asked me about multithreading vs multiprocessing and other related material. He asked me a dynamic programming question which wasn't very hard but I didn't get it nevertheless. The rest of the interview questions wasn't hard and was basically about simple sorting stuff and data structure. The onsite interview was held in their ny office. I was stuck on the first question which only required very basic math. It took me about 5 min just to understand what was going on because I couldn't picture the situation the interviewer described. After that, I don't remember much because I completely lost interest and just tried to get it done with.
Interview questions [1]
Question 1
how different processes communicate with each other
the advantages and disadvantages regarding multithreading vs multiprocessing
given an input of integers that represent stock prices, how to get the best buying and selling price (notice you can only sell after you have bought the stock)