J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez CSX
Entretien
typical OR problems from 9am to 4pm. meeting 10+ people one by one. was asked abouth salary at the end when talking to the director.
ATTENTION!!! I have NOT got the REIMBURSEMENT from CSX after TWO months!!!!!
Questions d'entretien [1]
Question 1
being asked some questions which are supposed for an interview in academia, not industry.
J'ai postulé en ligne. Le processus a pris 5 mois. J'ai passé un entretien chez CSX
Entretien
I applied online and got instructions to do initial assessment online a month later. This step comprised questions to determine the ability to read tables and do basic operations/inference and a lot of behavioral/ethics questions. About three months later I got a phone interview. They asked questions about my experience and other questions to check my knowledge.
About ten days later I made the on site interview. It took place in Jacksonville, FL. The office is not a pleasant place, it's rather depressing, with brownish walls, old desks and no windows. The team was courteous. I talked to every soul in that place, I got the same questions over and over. At some point I had to make an exam, what they call 'technical challenge'.
The exam was about OR and programming (LP, SQL, OOP, hypothesis test). For some reason they are obsessed with hypothesis test. The exam was rather a disappointing experience since I got criticisms for some of my answers and it turned out that the things they criticized were ok, it was them who were wrong.
Overall it seems that they are looking for someone who just received his PhD. In real life you can always open a book and freshen up your knowledge. Experience doesn't come from books.
Questions d'entretien [1]
Question 1
They asked me to write an OO program to sort a table with 3 rows and 4 columns. Nobody in his right mind will do such a thing. Anyways, I wrote two classes, one for the data type and another for sorting. I figured they wanted to know if I knew OOP so I separated sorting from data, as it happens in every OOP lib or system on planet Earth. The 'unexpected question' was 'why did I you write two classes?' I explained I had two conceptually different things. They didn't get it.
