Bloomberg Onsite - New Grad NYC (Reject)
Anonymous User
4857

Posting one of these because these types of posts helped me and I am just paying it forward even though I probably got rejected.

All Questions are Bloomberg Tagged (Don't ask me to tell you exactly what question, I gave a high level idea of each question which should be enough)

Phone Interview: Simple LL Traversal question and another LL question Delete Nth node from end of the list, this was my only question because I described multiple approaches and he had some follow ups.

Onsite:
Interview 1: Deep Copy stuff and pretty challenging follow ups, it isn't enough to go thru the tagged questions and know one solution, make sure you know all solutions as well as think about follow ups they may ask such as how a change in the input data structure could affect your solution.

Interview 2: Simpler questions but still had to dicuss multiple approaches. Simple question involving creating a graph and then seeing if there was a path from A -> B. Second question was a dp problem involving coins.

I feel like at another company I would have passed, but Bloomberg is a different beast because most people can solve the technical questions. It's more about deep understanding.

Notes on Bloomberg:

  • Make sure you actually understand implementations when you are preparing and think about follow ups
  • I provided solutions to all my problems and worked through them methodically, but could've done better on the follow ups
  • Make sure you are comfortable finding Big O before coding your solution
  • You have to understand you are trying to make an impression to be selected out of a group of over 10+ people on any particular day, speak with a smile.
  • The behavioral part is important just make sure you know why Bloomberg and really can explain every little detail on your resume
  • I didn't get asked to a HR interview and this usually means you get rejected
  • Good luck and don't try to memorize solutions because the interviewer really digs to check if you know what you are doing.
Comments (6)