Some time after applying for the job, I was sent an email saying I had been selected for an on-campus interview at my university.
Candidates were sent a mass email with a link where they could schedule their time online.
I went there and spent 45 minutes or so in a small room with two interviewers. They asked me about my projects, asked a few technical questions, then answered a few of my questions.
I wrote the code on a piece of paper. Since they were sitting across from me, they could not see me writing it, so it was a little inconvenient compared to whiteboarding/Google Docs/etc.
Both interviewers were nice and did a good job of explaining the company culture and answering questions.
It could have been better, but it was a positive experience overall.
It was my first in-person interview, and I did pretty awfully in terms of communication. I was not surprised I got rejected.
These were pretty standard tech interview questions. Mine was related to searching. I also had to explain the difference between the stack and the heap.
"Cracking the Coding Interview" would be good preparation. You can find practice problems on places like:
The following metrics were computed from 1 interview experience for the Bloomberg LP Software Engineer 2016 role in New York, New York.
Bloomberg LP's interview process for their Software Engineer 2016 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 Software Engineer 2016 interview process in New York, New York.