A recruiter from a partner company contacted me via LinkedIn. We had a brief call about my background and resume.
After exchanging a few emails, I was set up for a phone interview with a coding challenge on HackerRank.
The interviewer was extremely punctual and polite. He asked me about my background, resume, projects, and a few behavioral questions, like "Why Bloomberg?"
After that, we proceeded with the coding portion of the interview. I had some difficulty coming up with an efficient solution for the problem, but the interviewer walked me through it, and we collaboratively arrived at a solution.
Afterward, we had a brief Q&A session, and that was it.
No surprises; the next day, I received a rejection email.
I would describe the process up to that point as very pleasant. Make sure you practice as many problems as you can and know your data structures.
I have done better since, but oh well, it was very good practice for future interviews.
A meeting will be held at the New York and San Francisco offices. Participants will need to be flown to one of these two locations. Each office can accommodate half of the participants. The goal is to assign each participant to an office in a way that minimizes the total travel cost for the company. What is this minimal cost?
SF NY
A 500 700 B 200 600 C 400 500 D 600 200
Output: 1400 (A: 500 + B: 200 + C: 500 + D: 200)
The following metrics were computed from 157 interview experiences for the Bloomberg LP Senior Software Engineer role in United States.
Bloomberg LP's interview process for their Senior Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Bloomberg LP's Senior Software Engineer interview process in United States.