Le processus a pris 1 jour. J'ai passé un entretien chez Continental (Auburn Hills, MI) en août 2010
Entretien
I was contacted by an internal HR representative after a former colleague had forwarded my information to the employee. PLEASE NOTE: the company was Siemens at the time, Continental has since bought them out. During initial phone conversation, I was told that Siemens had the distinct technological advantage regarding the same product that I was working on in my current job. I decided to take the interview just to see if the engineers would divulge any information regarding this technical advantage. Sure enough, they spilled the beans and I walked away with a head full of proprietary information that they probably shouldn't have told me about. It was my decision to decline any further requests for interviews, but was shocked when I got a rather healthy offer letter the following day. Wow, that was quick. I took it to my current boos and said: "I have great information about our competitor, but it;s going to cost you 'this' much..."
J'ai passé un entretien chez Continental (Bengaluru)
Entretien
2 Rounds of Interview.
Technical round ,
Managerial round
HR Round
Salary negotiation
The interview process is more straight. They look for more technical especially in the embedded SW domain.
J'ai passé un entretien chez Continental (Guadalajara, Jalisco)
Entretien
First part of the interviews was very focused on my technical skills, especially on C language, bit manipulation and code efficiency. The second part of the interviews was more about soft skills and my previous experience and achievements. I should mention that I was moving from one BA to another inside Continental.
Questions d'entretien [1]
Question 1
Implement a program to swap two variables without using an intermediate variable.
J'ai postulé en ligne. Le processus a pris 5 jours. J'ai passé un entretien chez Continental (Novi Sad)
Entretien
The interview process began with an online Teams call with HR, covering topics like professional background, career goals, and role expectations. This was followed by a comprehensive technical interview, delving into technical expertise, problem-solving abilities, project experience, and domain-specific knowledge. The technical discussion included practical scenarios, testing coding skills, system design understanding, and approaches to debugging or optimizing workflows. Both sessions provided opportunities for questions, ensuring alignment between my skill set and the role’s requirements.
Questions d'entretien [1]
Question 1
Questions regarding embedded systems realtime aspects