Bloomberg Software Developer interview questions

The interview process had 3 parts. The first part was a half hour screen with a Bloomberg recruiter with standard "why do you want to work here" and "tell me about your background" type questions. The recruiter scheduled me for a 45 min technical phone screen that used HackerRank for a code challenge. The code challenge came straight out of Cracking the Code Interview. I did very well during the phone screen so a different recruiter emailed me to schedule an onsite interview. The recruiter asked me if I would prefer to write code on a whiteboard, paper, or on a computer during my onsite, and that I could bring my own laptop. I chose to bring my own laptop, but during the onsite the interviewers had me use HackerRank on one of the Bloomberg computers. There was no terminal for me to run my code to see if it worked or test out ideas (just an FYI). Bloomberg arranged for me to fly to NYC for the interview and paid for the flight, one night of hotel, and transportation to and from the airport. The onsite interview consisted of a tour of Bloomberg, and two separate one hour technical interview panels with two engineers per panel. Each of the four engineers asked me to solve a technical question - three were classic computer science algorithms, one was more of a free flowing design/architectural question. Some of the interviewers were trying a little too hard to be helpful with steering me toward the algorithms' solutions and it really interrupted my thought process. One engineer took so long to explain what he wanted me to do that I had almost no time to solve the problem. I was genuinely disappointed that I did not at any point meet with anyone from management, and that all of my interviewers were engineers with a limited perspective on what makes a great employee. The focus of the interviews was incredibly one-dimensional. All my interviewers seemed to care about was algorithms and data structures. My suggestions to improve upon this process would be to swap at least one of the five technical interviewers for someone from management who has a different perspective on what makes a great engineer. Ultimately I did OK during the onsite interview, but did not get a job offer. If I could do it over again, I would spent a lot more time on problems from Cracking the Coding Interview and any other algorithms I could get my hands on.