Principal Embedded Software Engineer

• Design, implement, test, maintain, and document low-level drivers, board support packages, and MCU initialization software.
• Bring up new hardware and investigate issues involving peripheral configuration, signal timing, interrupts, DMA, memory, and hardware/software interactions.
• Develop reusable driver interfaces with defined timing behaviour, resource usage, error handling, and integration requirements.
• Own the requirements, design, implementation, and unit verification of assigned software components; contribute to software integration and verification activities across SWE.1–SWE.6.
• Develop and execute tests covering normal operation, boundary conditions, timeouts, and fault handling, using automated tests and target hardware as appropriate.
• Implement allocated software safety requirements and relevant MCU safety mechanisms in accordance with project ISO 26262 processes.
• Collaborate with hardware engineers, software architects, test engineers, customers, and product teams to resolve technical issues and deliver production-quality software.
  *

• Bachelor’s degree in Electrical Engineering, Electronics Engineering, Computer Engineering, Computer Science, or an equivalent technical qualification.
• Typically 5–7 years of embedded software development experience, with substantial hands-on experience developing and debugging low-level drivers and microcontroller firmware; automotive experience preferred.
• Strong proficiency in Embedded C, including pointers, bitwise operations, memory-mapped registers, memory layout, and safe access to shared data. Ability to read assembly and disassembly when debugging.
• Proven experience in bare-metal development, including MCU initialization, interrupt handling, timing constraints, critical sections, and robust error handling.
• Experience developing, adapting, and validating peripheral drivers, covering several of the following: GPIO, timers/PWM, ADC, SPI, I²C, UART, CAN/CAN FD, LIN, DMA, watchdogs, and flash memory.
• Ability to interpret datasheets, technical reference manuals, register descriptions, hardware schematics, and silicon errata.
• Practical experience with board bring-up and hardware/software debugging using an oscilloscope, logic analyzer, and an appropriate debug interface such as JTAG or SWD.
• Understanding of startup code, linker configuration, clock trees, reset behavior, and memory organization.
• Experience with version control, code reviews, static analysis, unit testing, and verification on target hardware; familiarity with MISRA C guidelines.
• Working knowledge of requirements analysis, software architecture, detailed design, and requirements traceability. Familiarity with Automotive SPICE and ISO 26262 development practices.

Nice to have:

• Hands-on experience with Infineon PSoC, TRAVEO, or AURIX microcontrollers, and a sound understanding of the relevant Arm Cortex-M or TriCore architecture.
• Experience with additional Infineon MCU families and relevant software ecosystems, such as ModusToolbox, PSoC Creator, TRAVEO driver libraries, or AURIX iLLD.
• Experience with AUTOSAR MCAL driver configuration, integration, or development.
• Experience integrating drivers with an RTOS, including synchronization and interrupt-to-task communication.
• Experience with bootloaders, firmware updates, flash programming, EEPROM emulation, or secure boot.
• Experience with multicore firmware, inter-core communication, memory protection, and cache/DMA interactions.
• Experience with automated hardware testing, Python scripting, and continuous integration.
• Experience implementing safety mechanisms and producing verification evidence for ISO 26262 projects.