Propellence places the engineers and architects who make software-defined vehicles possible — from MCAL and BSW integration to Adaptive AUTOSAR platform leadership. Deep domain fluency, not keyword-matched resumes.
Generalist recruiters flatten AUTOSAR roles into one bucket. We source and evaluate against the specific layer, tool chain, and safety context each mandate actually requires.
Owns BSW configuration strategy, ECU extract definition, and supplier tool alignment (Vector DaVinci, EB tresos) across platform programs.
Integrates COM, DIAG, OS, and MCAL modules to silicon; owns startup, NVM, and communication stack bring-up.
Drives ara::com service design, POSIX-based ECU architecture, and SOA transition strategy for next-gen SDV platforms.
Owns safety case development, ASIL decomposition, and safety argumentation across the AUTOSAR software stack.
Coordinates cross-supplier integration, calibration, and release management across multi-ECU vehicle programs.
Sets the Classic-to-Adaptive roadmap and owns the make-vs-buy and supplier strategy for the software platform org.
AUTOSAR hiring fails most often not from a thin candidate pool, but from a search partner who can't tell a BSW integration engineer from an application-layer developer.
Our consultants come from technical backgrounds and evaluate AUTOSAR candidates the way your own architects would — by layer, tool chain, and program history.
We track candidates across the full transition — from legacy Classic BSW specialists to engineers building Adaptive, service-oriented platforms for SDVs.
Most senior AUTOSAR talent isn't on job boards. Our search is direct, discreet, and built on a decade of relationships across OEMs and Tier-1 suppliers.
Active search coverage across India, Germany, the USA, Japan, and APAC — where AUTOSAR engineering talent actually concentrates.
Straight answers to what clients ask before starting a search.
It's the search for engineers and architects who build and integrate the AUTOSAR software stack — the layered standard (Application, RTE, Basic Software, MCAL) used across most automotive ECUs. Roles range from BSW integration engineers to Adaptive Platform architects.
Classic AUTOSAR roles center on statically configured BSW/MCAL work for traditional ECUs. Adaptive AUTOSAR roles need service-oriented architecture and POSIX-based platform experience for software-defined vehicles. We source separately for each, since the skill sets rarely overlap.
Yes — from BSW/MCAL integration engineers up to Head of Vehicle Software Platform. Our search covers the full band of AUTOSAR-related technical and leadership roles.
India, Germany, the USA, Japan, and APAC — the primary hubs for AUTOSAR engineering talent and automotive ER&D centers.
Tell us the layer, the platform, and the timeline — we'll bring you candidates who actually fit the architecture.