Continental embedded interview prep

Roles they hire for

• ECU software engineer (body, chassis, ADAS)
• Software integration and HIL test engineer

What they emphasise

• AUTOSAR Classic and Adaptive ECUs
• HIL and system validation
• Vehicle networks and diagnostics

Brush up on

AUTOSAR Classic and AdaptiveHIL testingCAN and automotive EthernetISO 26262

How the rounds usually run

A typical automotive supplier loop for embedded roles. Companies vary by team and seniority.

Written or online test

• Aptitude and logical reasoning
• C programming and core electronics
• Sometimes basic networking and OS

Example: What is the output of a signed and unsigned comparison in C, and why?

Technical 1: Embedded C and MCU basics

• Embedded C, pointers and memory
• Microcontroller peripherals and interrupts
• CAN fundamentals and your final-year or work project

Example: How does CAN arbitration work, and what happens on a bit error?

Technical 2: Automotive domain

• AUTOSAR layers, RTE and BSW
• UDS diagnostics and ISO-TP
• ISO 26262, MISRA and ASPICE awareness

Example: Where does a diagnostic request travel through the AUTOSAR stack, from CAN to the application?

Managerial or process round

• V-model and ASPICE work products
• Estimation, customer communication and reviews

Example: How do you handle a customer requirement that conflicts with a safety requirement?

HR

• Motivation, mobility and compensation

Example: Why automotive software?

Practice questions

Original questions written for Continental's focus areas, not leaked ones.

1. Compare AUTOSAR Classic and Adaptive. When does a project need Adaptive?
2. Design a HIL test for a door-module ECU's anti-pinch feature.
3. How do you diagnose intermittent CAN bus-off errors in a vehicle?
4. What changes when an ECU moves from CAN to automotive Ethernet?
5. How do you prove a software change didn't break timing on an ECU?

Your prep playlist

Design rounds to practise

Themes are inferred from Continental's public product lines.