Software Engineer applicants have rated the interview process at Continental with 2.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 69% positive. To compare, the company-average is 68.1% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 20 days to get hired, when considering 94 user submitted interviews for this role. To compare, the hiring process at Continental overall takes an average of 26 days.
Common stages of the interview process at Continental as a Software Engineer according to 94 Glassdoor interviews include:
One on one interview: 17%
Phone interview: 15%
Skills test: 13%
Presentation: 13%
IQ intelligence test: 11%
Group panel interview: 8%
Personality test: 8%
Background check: 7%
Drug test: 6%
Other: 2%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 6 weeks. I interviewed at Continental (Guadalajara, Jalisco) in Jul 2015
Interview
Got the interview via an old friend who currently works in there. I never really got a message on which position was applying to. Technical questions were considerably easy, and a couple of weeks later i received a request to present a medical test. It took almost a month more to hear from them again, and after i pinged my friend on some news on what might be going on. Once i got 'the call', i was able to choose my entering date, and it was a simple process.
Interview questions [1]
Question 1
As most of the techinal side of the interview is made in an exam, interview was more focused on previous work experience, why to choose Continental, and sort of the same questions.
It was an easy to medium interview process.
As entry level it was quite smooth, mostly basic python questions and clarity in algorithm and approach to a problem was interviewed.
One Technical round followed by managerial round and finally hr round happened.
Interview questions [1]
Question 1
RADAR concepts and Python basics, as the role was for Testing Radar
Talk about process, behavior and code test some times, not every time, depends on management and scope of the project, technical questions are about scope, embedded C, AUTOSAR, embedded Linux, ask recruiter if needed for more info.
It was on campus one day total 4 rounds.
1st round mcq/ system test
In single day took all these below round
2nd technical interview
3rd technical interview
4th managerial round