19 Nov
|
Interface Microsystems
|
Pune
19 Nov
Interface Microsystems
Pune
Domain / Vertical: Cross-vertical (horizontal team, serves all product lines) Experience Band: 2-5 years Role Summary Writes optimized, reusable embedded C/C++ firmware (Rust a plus) for automotive ECUs, covering MCU bring-up, AUTOSAR BSW integration, bootloader/secure boot, and multicore platforms, following ASPICE/ISO 26262/ISO 21434-aligned practices.
Key Responsibilities
• Design, develop, and optimize embedded C/C++ firmware for automotive-grade MCUs
• Write reusable, MISRA-C compliant, portable code across ECU variants and platforms
• Develop and integrate AUTOSAR BSW modules (MCAL, Diagnostics, Communication stack — CAN/CAN-FD/Ethernet, NVRAM)
• Implement and maintain bootloader and secure boot flows (secure flash, HSM-based key management)
• Work on multicore MCU architectures — task partitioning, core-to-core communication, timing
• Debug using tools such as Lauterbach/TRACE32, CANoe/CANalyzer, and hardware bring-up equipment
• Support functional safety (ISO 26262 ASIL-B/C) and cybersecurity (ISO 21434 SecOC, secure boot) implementation and evidence
• Participate in code reviews, unit/integration testing, and configuration management (Git)
• Explore Rust for select new modules where ecosystem and tooling allow — not mandated, but tracked as an emerging option A Typical Day
• Morning: stand-up with the Firmware Lead — task allocation, defect triage, build status
• Morning: firmware development in C/C++ — MCU-level modules, AUTOSAR BSW/MCAL configuration, communication stack (CAN/CAN-FD/Ethernet) work
• Mid-day:
hardware bench time — bring-up, flashing, debugging with Lauterbach/TRACE32 and CANoe/CANalyzer
• Afternoon: bootloader / secure boot work (secure flash, HSM key handling) and multicore task partitioning/timing analysis
• Afternoon: code review against MISRA-C, unit/integration test execution, defect fixes with the systems team
• Late day: Git commits and configuration management; document safety/cybersecurity evidence for ISO 26262 / ISO 21434
• Weekly rhythm: platform standards and reuse review, HW-SW integration sync, occasional Rust/tooling exploration spike Required Skills
• 2-5 years embedded firmware development in C/C++ for automotive or safety-critical systems
• Strong understanding of microcontroller architecture, memory layout, compilers, and debuggers
• Experience with AUTOSAR Classic (BSW modules, MCAL, Diagnostics, Communication stack)
• Bootloader and flashing experience
• Git and configuration/change management Positive-to-Have Skills
• Rust exposure for embedded/automotive contexts (ecosystem still maturing — AUTOSAR Rust Working Group and tooling-vendor activity)
• Secure boot / HSM / SecOC hands-on experience (ISO 21434)
• Multicore AUTOSAR software architecture experience
• ASPICE-driven development background Standards & Compliance Exposure: AUTOSAR Classic, MISRA-C, ASPICE, ISO 26262 (ASIL-B/C awareness), ISO 21434 (SecOC, secure boot)
Education:
Bachelor's/Master's in Electronics, Computer Engineering, or Embedded Systems
📌 Embedded System Software Engineer (Pune)
🏢 Interface Microsystems
📍 Pune