J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 1 jour. J'ai passé un entretien chez JetHead Development (Carlsbad, CA) en nov. 2016
Entretien
There were three interview candidates including myself, and we were invited into a large conference room where they held the interview. First they had the COO (our interviewer) give a presentation about the company, and the types of projects they were working on. Then they sat us down at laptops and had us complete a coding project (designed similar to a university lab course) that was meant to take 3 hours to complete. During this time, they also pulled us aside for 1:1 interviews where they asked me about my interest in the company, my career plans for the future, as well as quizzing me on some technical coding problems (which were the last few questions on the "lab" we were given).
Questions d'entretien [1]
Question 1
One problem we had to solve was modifying some server and client code they provided to us so that the client could send some character and a number, X, to the server who would then return that character X many times. (e.g. C: A 3, S: AAA)
J'ai postulé en ligne. Le processus a pris 1 jour. J'ai passé un entretien chez JetHead Development (Carlsbad, CA)
Entretien
I applied online through my university job site. I was invited for an interview at their office a few weeks after I applied. There was a Coding/Problem solving group session in one of their conference room. They provided laptops to work on. When you finish the exercises, it is followed by a technical interview of a few short questions by the CEO!
J'ai postulé via une agence de recrutement. Le processus a pris 2 mois. J'ai passé un entretien chez JetHead Development (None)
Entretien
They take a C++ test, 4-6 candidates in a room, the test starts with introduction of the company. They give the part of code on which they have worked in any project etc, and questions related to that code. They expect you to understand the code to an extent that you can make simple changes to the code, the changes are not in fundamental parts i.e. in classes but they are in functions. they check how good you can debug the code. then after the code three questions are written :
1) this question is about a function trace() which prints something at beginning and end of main(), how does trace works? (the constructor and destructor of trace object works at the start and end of main)
2) difference between string &address and const string address
3) class foo()
{
void do()
{
cout<<"foo \n";
}
}
class bar : public foo
{
void do()
{
cout<<"bar \n";
}
}
void dosomething(foo f)
{
f.do();
}
main()
{
bar b;
b.dosomething();
}
what does the following print: 1) f.do(); 2) b.do 3) b.dosomething(); (here they want to get bar printed instead of foo, the concept of object slicing is used)
1
Meilleures entreprises pour « Rémunération et avantages » près de chez vous