I was briefly introduced to two interviewers. They wanted me to tell a little bit about my last job.
I told them some success stories. Then they moved into asking me to code. I successfully wrote and executed the code they wanted.
I have interviewed many engineers, and I did not feel the interview revealed much about me, other than that I can code. The conditions were unlike any real-world situation. In the real world, one is used to the style and requirements, and is warmed up. In this interview, a very uncertain situation was thrown upon me.
Even if the company operates in uncertain situations, there is no way that they are as unclear as given. I got warmed up and used to thinking in this uncertain way after about 20 minutes. But, in that time, I was programming slowly. I got good at thinking the way they expected at about the time the interview was over.
I do like programming under challenging conditions, so I would probably enjoy and be very good at this job, if I get the job. However, I don't see how the interviewers could discover this.
Both of them had far less experience than I did. For these reasons, I gave the interview a thumb down.
Simple C++ algorithm: returning a string of a number, inserting commas into the right places.
The following metrics were computed from 1 interview experience for the Bloomberg LP Senior Applications Developer Consultant role in New York, New York.
Bloomberg LP's interview process for their Senior Applications Developer Consultant roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Bloomberg LP's Senior Applications Developer Consultant interview process in New York, New York.