Roles we place
BSW and MCAL engineers
Configure MCAL, OS, memory stack and vendor BSW on Infineon AURIX, NXP S32 or Renesas RH850 microcontrollers.
ComStack and Ethernet engineers
CAN, CAN FD, LIN, FlexRay and automotive Ethernet stacks, PduR, SoAd and SOME/IP configuration and debug.
SWC and RTE developers
Application SWCs, runnables and port interfaces, hand-coded or generated from Simulink, with MISRA C compliance.
AUTOSAR Adaptive developers
C++14/17 applications using ara::com, execution management and SOME/IP for software-defined vehicle platforms.
Integration engineers
Bring BSW, RTE and SWCs together, resolve configuration conflicts, own builds and debug on target with Lauterbach.
Diagnostics engineers
UDS (ISO 14229) services, DoIP, DEM and DCM configuration, ODX and DTC handling, tested in CANoe.
AUTOSAR roles, skills and tools
| Role | Core skills | Typical tools and standards |
|---|---|---|
| BSW / MCAL engineer | MCAL, OS, NvM and memory stack, vendor BSW integration | Vector DaVinci Configurator, EB tresos, ETAS ISOLAR, AUTOSAR Classic |
| ComStack engineer | CAN/CAN FD/LIN/FlexRay, automotive Ethernet, PduR, SoAd | DaVinci Configurator, Vector CANoe, AUTOSAR Classic |
| SWC / RTE developer | Embedded C, RTE interfaces, model-based development | Vector DaVinci Developer, MATLAB/Simulink, MISRA C |
| Adaptive developer | C++14/17, ara::com, SOME/IP, POSIX, OTA update flows | Vector MICROSAR Adaptive, Linux or QNX, AUTOSAR Adaptive, UNECE R156 |
| Integration engineer | RTE generation, build systems, memory mapping, target debug | Lauterbach TRACE32, Jenkins, ASPICE |
| Diagnostics engineer | UDS (ISO 14229), DoIP, DEM/DCM, ODX | Vector CANoe, CANdelaStudio, CANape |
How hiring works
01
Role brief
We confirm Classic or Adaptive, BSW vendor and version, microcontroller family, communication buses, ASIL and ASPICE context, location and the engagement model.
02
Technical screening by practising engineers
Practising AUTOSAR engineers interview on configuration, integration and debug problems such as a ComStack routing fault or an MCAL clock set-up, matched to your stack. The method is set out on how we vet engineers.
03
Shortlist with written assessment
The shortlist includes a written assessment per candidate: stacks used in production, modules owned, ASIL exposure, notice period and joining date.
04
Your interviews
You interview the shortlisted engineers and choose. We coordinate schedules and feedback.
05
Onboarding and follow-up
We handle contracts and onboarding, then hold regular check-ins with you and the engineer after the start.
Engagement options
- Staff augmentation: AUTOSAR engineers on contract inside your team and toolchain
- Contract-to-hire: convert to your payroll on terms agreed in the contract
- Permanent recruitment: AUTOSAR architects and leads you employ directly
- Dedicated engineering teams: a BSW or integration pod across several ECUs
- Managed AUTOSAR projects or a Build-Operate-Transfer team
AUTOSAR hiring market and buyer risks
McKinsey projects the automotive software and electronics market will reach about $519 bn by 2035, with the work moving to zonal and central compute and over-the-air updates. That shift keeps Classic engineers busy on zone controllers and pulls Adaptive developers onto central compute. Current Bengaluru AUTOSAR postings from large Tier-1s ask for MCAL, BSW and ComStack, RTE, OS, AUTOSAR Ethernet, CAN and LIN, Vector DaVinci and CANoe and Lauterbach, across 3 to 15 years' experience. We use the same vocabulary when screening.
Many buyers compete for the same engineers. nasscom–Zinnov count 2,117 GCCs in India in FY26, and Zinnov puts GCC attrition at about 16%. Senior AUTOSAR engineers commonly serve 60 to 90 days' notice, and counter-offers cause late drop-outs. Contract-to-hire is the practical bridge: an available engineer starts on contract and converts later, or covers the gap while a permanent hire serves notice. See automotive engineering staffing for related roles.
Need testing as well as engineers?
- Regress AUTOSAR builds through automotive testing
- Run benches with HIL and SIL testing or automate them with test automation
- Read the AUTOSAR glossary entry
Frequently asked questions
Do you place AUTOSAR Classic or Adaptive engineers?
Both. Classic Platform engineers configure and integrate BSW, MCAL and RTE on microcontrollers; Adaptive Platform engineers write C++ applications on POSIX operating systems using ara::com and SOME/IP. The skill sets overlap less than the shared name suggests, so we screen for the platform your project uses.
Can you find engineers with experience on our BSW vendor's stack?
Usually. Most AUTOSAR engineers in Bengaluru have worked with Vector MICROSAR, EB tresos or ETAS stacks, and the written assessment states which ones each candidate has used in production. Engineers who know one stack generally adapt to another, and we tell you when that ramp-up applies.
What notice periods should we expect for AUTOSAR engineers in India?
Notice periods of 30 to 90 days are common, and experienced AUTOSAR engineers are often at the longer end; many GCCs enforce 90 days. We share each candidate's notice period and joining date on the shortlist. If you need someone sooner, an engineer available on contract can start while a permanent hire serves notice.
How do you reduce offer drop-outs?
We ask about competing offers and counter-offer risk at screening, keep contact with the candidate through the notice period, and flag concerns to you early. Contract-to-hire reduces exposure because work starts with an available engineer. Drop-out risk cannot be removed, only planned for.
Can a contract AUTOSAR engineer convert to permanent?
Yes. Under contract-to-hire you can move the engineer to your own payroll after working together. Conversion timing and any fee are agreed in the contract at the start of the engagement.
What if the engineer is not the right fit?
Replacement terms are agreed in the contract before the engagement starts. We hold regular check-ins to catch issues early, and if a replacement is needed we restart the search with a sharper brief.
Who owns the code and configuration our contract engineers create?
IP ownership and confidentiality are written into the contract before work starts, normally assigning work product to you. Engineers sign your NDAs and work in your repositories and licensed tools, onsite, remote or hybrid as agreed per role.
Tell us the roles, seniority and start date. A practice lead replies with matched profiles.