The quality of questions you get asked in an interview are good indicators of the quality of work you'll end up doing in that company. Of course, there will be false positives, but never false negatives.
I had a phone interview today and have to say the questions were quite lame. The interviewers seemed inexperienced and had their priorities misplaced. The fact that I missed an "int" before an "i" (making it "int i") seemed more important to them than the work having a big flaw (which I had to tell them).
Besides, they were pestering me to dictate the code as I write it. (No, taking 1 minute to write that down and dictation after that is not okay. No, that's not how they do at Bloomberg.)
Either they are interviewing for the first time, or Bloomberg L.P. gets heaps of fake resumes that they need to clear out with mediocre questions. They mostly asked some silly C, C++, and Unix questions, testing your memory more than your intelligence.
What are virtual functions?
How are they implemented?
The following metrics were computed from 4 interview experiences for the Bloomberg LP C++ Developer role in New York, New York.
Bloomberg LP's interview process for their C++ Developer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Bloomberg LP's C++ Developer interview process in New York, New York.