
Propulsion Base Software Low Level Driver Engineer
Stellantis
Job description
The PRS Base Software Low-Level Driver Engineer is responsible for the design, development, integration, and validation of low-level driver software for propulsion and electrified powertrain control modules.
Key responsibilities include:
-
Design, develop, and maintain embedded low-level driver software including requirements analysis, architecture, coding, integration, and verification.
-
Implement hardware interface drivers for peripherals and external devices including high-side and low-side drivers (HSD/LSD), SPI, I2C, H-Bridge interfaces, and motor control drivers (e.g., PWM, FOC, position/speed sensing interfaces).
-
Develop and integrate Microcontroller Abstraction Layer (MCAL) components, hardware interface drivers, and complex device drivers supporting propulsion applications.
-
Configure and integrate AUTOSAR Basic Software modules such as OS, IOHWAB, FEE, and WDG using Vector or ETAS toolchains.
-
Perform hardware-software integration by working with hardware schematics, device reference manuals, and microcontroller documentation.
-
Support ECU hardware bring-up and early software enablement activities on new controller platforms.
-
Debug and troubleshoot hardware/software integration issues using oscilloscopes, logic analyzers, JTAG debuggers, trace tools, and emulators (e.g., Lauterbach).
-
Optimize low-level driver implementations for deterministic real-time performance, efficient memory usage, and reliable peripheral operation on multicore microcontrollers.
-
Collaborate with hardware engineering, systems, controls, and supplier teams to ensure proper hardware interface functionality and alignment with propulsion system requirements.
-
Ensure alignment with AUTOSAR architecture, including RTE integration and system resource usage.
-
Conduct and participate in design reviews, code reviews, and technical inspections to ensure high-quality software deliverables.
-
Develop and maintain technical documentation including software design specifications, interface definitions, and test plans.
-
Perform software verification and validation activities including unit testing, integration testing, and validation on target hardware (white box, black box, and gray box testing).
-
Ensure compliance with automotive software standards and development processes including MISRA-C, ASPICE, and ISO 26262.
-
Contribute to continuous improvement of development processes, tools, and methodologies.
-
Support vehicle program milestones and production software releases with high-quality, validated deliverables.
Requirements:
Basic Qualifications:
-
Bachelor of Science degree in Electrical Engineering, Computer Engineering, Computer Science, or related field
-
5 years experience developing or integrating low-level drivers, MCAL, or complex device drivers.
-
Experience developing drivers or interfaces for hardware components such as SPI, I2C, HSD/LSD, H-Bridge circuits, timers, ADCs, communication peripherals, and motor control interfaces (PWM, current sensing, position/speed sensors).
-
Experience with AUTOSAR Basic Software configuration (e.g., OS, IOHWAB, FEE, WDG) using Vector or ETAS toolchains.
-
Experience with multicore automotive microcontrollers and hardware/software integration, including interpreting schematics and device reference manuals.
Preferred Qualifications:
-
Experience with embedded C/C++ development (hand coding) in real-time operating system environments.
-
Strong understanding of functional safety concepts and experience working within ISO 26262 frameworks.
-
Familiarity with automotive software standards such as MISRA-C and ASPICE.
-
Experience using embedded development tools including compilers, debuggers, emulators (e.g., Lauterbach), and automation scripting.
-
Experience using hardware debugging tools such as oscilloscopes and logic analyzers.
-
Experience in software verification and validation including white box, black box, and gray box testing.
-
Experience with data acquisition and calibration tools such as ETAS INCA, CANoe, and CANalyzer.