Embedded Firmware Engineer Automotive

Embedded Firmware Engineer — Automotive

What You'll Do

• Design, prototype, implement, and test production embedded firmware for automotive ECUs on 32-bit microcontrollers.

• Develop and optimize firmware in a real-time operating system (RTOS) environment, managing timing, concurrency, and resource constraints.

• Build diagnostic and self-test functionality, including power-on self-tests (POST), memory built-in self-tests (BIST), and controlled power-up / go-to-sleep shutdown sequences that meet quiescent-current targets.

• Implement fault-detection and safe-state handling — for example, monitoring incoming and internal supply voltages, raising diagnostic trouble codes (DTCs), and driving the ECU into a protective reduced-function state on limit violations.

• Develop CPU-, communication-, and memory-load generation and stress-test functions that can be triggered over CAN, Ethernet, or a diagnostic interface for validation and characterization.

• Implement and monitor communication interfaces — CAN and Ethernet channels — including link-error, cable-fault, and signal-integrity (CRC) detection, with error logging, reporting, and clear-on-reset behavior.

• Write firmware to interact with low-level peripherals and buses (SPI, UART, I2C, CAN) and higher-level networking (TCP/UDP) and diagnostics (UDS).

• Partner with test and platform engineers to build test frameworks and harnesses at unit, integration, and system levels.

• Debug at the hardware level using standard test equipment, and collaborate across software, hardware, and mechanical teams from bring-up through deployment.

• Apply functional-safety and security concepts relevant to automotive and autonomous systems throughout design and implementation.

What You'll Bring

• 3–8 years of hands-on embedded firmware development experience.

• Expert-level C or C++ for resource-constrained, real-time systems.

• Strong experience with 32-bit ARM Cortex-M class microcontrollers; familiarity with automotive processors such as the NXP S32G / S32K families.

• Practical experience with low-level RTOS development (for example, FreeRTOS).

• Solid grasp of communication protocols across the stack — SPI, UART, I2C, CAN at the low level, TCP/UDP at the high level, and UDS diagnostics.

• Working knowledge of Python for tooling, automation, and test.

• Hardware-debugging skills with standard bench equipment (oscilloscope, multimeter, power supply) and basic electrical-engineering fundamentals for low-level debugging.

• A structured, test-driven approach to firmware quality, and the ability to work effectively with hardware and test engineers.