





Metro location and mid-level role increase competition, but niche Autosar/embedded skills reduce applicant density.
Highly domain-specific automotive embedded and functional-safety requirements limit cross-industry transferability.
Explicit 6-8 years plus mandatory Autosar, device-driver, safety and protocol expertise enforces high filtering.
Login to See Your Match Score
Create a free account or log in to unlock your CV match score across:
Design and develop embedded software for automotive products focusing on Active Safety and User-Experience areas.
Develop device drivers and work on embedded software using C for 16/32-bit microcontrollers (e.g., Infineon, NXP).
Implement and verify software components using Autosar methodologies, communication protocols (CAN/LIN/Flexray/Ethernet), and automotive standard processes including ISO 26262 functional safety.
6-8 years of experience in embedded software development.
Proficient in embedded C programming for 16/32-bit microcontrollers.
Experience with Autosar workflows, device driver development, and communication protocols like CAN, LIN, Flexray, Ethernet.
Hands-on with debugging tools, verification tools (static analysis, unit testing), and knowledge of automotive standards (CMM/ASPICE, ISO 26262).
Experienced with multi-core and multi-domain embedded automotive systems.
Familiar with vehicle connectivity security aspects and tools such as CANalyzer/CANoe.
Previous exposure to automotive gateway, BCM, PEPS/PAKM, or V2X technologies is an advantage.