J'ai postulé via un recruteur. Le processus a pris 3 semaines. J'ai passé un entretien chez Stryker en août 2014
Entretien
I was contacted originally through a recruiting agency and worked with a very pleasant recruiter. He scheduled an HR screening a couple days out, which the HR person missed, and rescheduled after the fact. The screening went well, and I moved on to a technical interview with the hiring manager and a few members of the team. The content of the phone technical interview was trivial, almost to a surprising degree. (What is a class? What is a virtual method? Lots of focus on OO architecture for an embedded job). After that, the hiring manager was pleased and had me do the infamous Gallup interview (which was rescheduled with 20 minutes notice). You can read a lot about them online, but basically it's a personality test that is an hour worth of rapid-fire seemingly nonsensical questions that help Stryker decide if you are a good fit. I apparently was not.
Questions d'entretien [1]
Question 1
Gallup questions were often unexpected. The most "difficult" technical question involved describing the class hierarchy you would use to represent a standard set of 52 playing cards for use in a game.
J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 5 jours. J'ai passé un entretien chez Stryker en mars 2026
Entretien
good interview. 20 mins for all students. topics were rtos, kernel, gpu, and resume based questions. embedded c and also very imp where they asked pointers, volatile, cache memory, different types of pointers, layout of c program.
Very comfortable and professional between testing and embedded systems in had a really great experience interviewing with the company although I didn't get an offer but the interview process was smooth
J'ai postulé via un recruteur. J'ai passé un entretien chez Stryker
Entretien
First call was a behavioral review with the recruiter, then you take the Gallup test afterward, then you have a technical interview with the hiring team. The wait between interviews was about a week each.
Questions d'entretien [1]
Question 1
Computer architecture, C++ trivia, and low-level hardware concepts like interrupts