Le processus a pris 3 jours. J'ai passé un entretien chez Bloomberg en mars 2012
Entretien
I applied online in Bloomberg. I got automated reply after few weeks that your resume is selected, please take assessment test from the link below within three days starting from today(sharp deadline). I didn't find any information about this test not even its type(technical or quantitative) online. I gave the test. It had all technical questions based on java especially RMI related and few jsp based. Every questions must be attempted in 3 min and once moved to next question answer can't be changed of previous ones. Questions were interesting few on basics and few based on programming in RMI related stuff. Overall it was okay. Waiting for the result of next now. :)
Questions d'entretien [1]
Question 1
Question on ObjectOutputStream, jsp tags, some logic based, difference between string & string buffer, ...!!!
J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Bloomberg (New York, NY) en janv. 2022
Entretien
Interview got pushed back twice because the interviewer forgot to show up at the assigned time. Didn't make it past the first interview. I was a little nervous, but the coding question was pretty open-ended and the interviewer wanted it done in a specific way. A little disappointed by the lack of professionalism compared to other similar companies.
J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Bloomberg (Londres, Angleterre) en oct. 2018
Entretien
Two days after the application I got an email with instructions to schedule a 60' phone technical interview. Set the interview for the following day and I received an email with a HackerRank link where I selected my preferred programming language.
J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Bloomberg (New York, NY) en mars 2018
Entretien
Recruiter connected me and scheduled a technical interview. Recruiter sent a lot of useful information about the interview process ad how to prepare.
Developer who interviewed me asked me to solve a problem, but, obviously, knew how to solve it and didn't pay attention to my approach, which was different from the one shown in a book. (Though my approach would definitely be less effective.) As we were not on the same wave, ended up taking too much time for just one problem.