Taro Logo

Software Engineer Interview Experience - New York, New York

July 1, 2018
Positive ExperienceGot Offer

Process

My background:

  • 2018 new grad
  • Liberal arts college
  • CS Major

I applied online, and perhaps two weeks later, I was invited for a phone interview. This was a technical interview with an engineer. We briefly reviewed my resume and then worked through two problems. The first was a warm-up, and the second was a bit more involved. My solution resembled dynamic programming.

The interviewer was helpful, guiding me through the process with hints and evolving the problem as we went. Overall, it was pleasant.

A couple of days later, I received an email inviting me to an on-site interview. They provided four possible dates: two in June and two in July (it was May at the time). I chose the earlier July date.

I had about one full month to prepare. I completed a few LeetCode questions daily and reviewed algorithms and data structures.

They arranged travel. I booked flights to and from the location through an agency, and I was provided a hotel room. They also offered access to their black cab service, which was free. I was unsure if tipping the drivers was customary.

I was held up at check-in and missed the building tour, but my first interviewers met me in the waiting area.

The first two interviews were technical, each with two interviewers and two questions. Each session included brief questions about my resume and opportunities for me to ask them questions. My interviewers were pleasant and willing to help if I got stuck.

In each session, the first question was a warm-up, and the second was a little more involved.

Between the first and second interviews, I had lunch.

Apparently, if you don't perform well on the first two, the interview concludes. However, if you do alright, you proceed to a couple more interviews.

The third interview was with an HR representative who asked about my resume in depth and inquired about salary expectations. She also answered any questions I had. It included typical "why Bloomberg" questions.

The fourth interview was with a Senior Engineer/team lead, who attended alone. There was some resume discussion, followed by two questions. The first was a standard coding question that I completed on paper; I discussed it with him without writing any code. The second was a brain teaser that caught me off guard, but he guided me through it.

After that, I was shown out.

Questions

Mostly LeetCode Easy level questions.

Topics included:

  • Dynamic programming
  • Arrays
  • Object-oriented design
  • Graphs/trees (nothing like Dijkstra's)
  • Space-time trade-offs
  • Being conscious of allotted space
  • Some mathematical/statistical concepts (though they'll explain if you're unfamiliar)

Space and time complexity analyses seemed to be emphasized, so know how to do those. I provided multiple answers to all the questions, so maybe that helps.

Was this helpful?

Interview Statistics

The following metrics were computed from 470 interview experiences for the Bloomberg LP Software Engineer role in New York, New York.

Success Rate

12%
Pass Rate

Bloomberg LP's interview process for their Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive53%
Neutral28%
Negative19%

Candidates reported having very good feelings for Bloomberg LP's Software Engineer interview process in New York, New York.

Bloomberg LP Work Experiences