AUTOSAR talent is one of the thinnest markets in embedded automotive — and the one where a wrong hire stalls an ECU programme for months. We keep an active base of 200+ AUTOSAR engineers across Classic Platform and Adaptive Platform, German-capable, available on the same team-leasing model as our SAP automotive delivery. This page says exactly what that means — and what it doesn't.
Most vendors dress a candidate database up as delivery history. We won't — so here is the claim, drawn precisely:
200+ engineers with AUTOSAR experience in our active, screened base — Classic and Adaptive, across modules — reachable through the same network that staffed our German automotive programme.
We don't claim completed AUTOSAR implementations under our own name. When a vendor's "experience" section can't tell those two apart, neither can their delivery.
For a staffing decision, bench reality beats project folklore: what you buy is the engineer who starts — screened, German-capable, contract-ready.
The two AUTOSAR platforms need different profiles — briefs that ignore the split produce shortlists that fail in the first interview:
| Classic Platform | Adaptive Platform | |
|---|---|---|
| Runs on | Deeply embedded ECUs — body, chassis, powertrain control | High-performance computers — ADAS, connectivity, service-oriented functions |
| Typical stack | C, RTE, OS/BSW configuration, hard real-time | C++14+, POSIX, SOME/IP, service-oriented architecture |
| Profile we screen for | BSW/RTE configuration depth, toolchain fluency (e.g. vector toolsets), safety context (ISO 26262) | Modern C++ engineering discipline, middleware and services thinking, CI-based delivery |
Briefs are matched at platform and module level — the same discipline our SAP staffing runs on.
The AUTOSAR bench plugs into a delivery model already proven in German automotive:
Language verified in live conversation, not from the CV — the screening bar our Mercedes-Benz engagement was built on.
Complementary roles, one synchronized start — the team-build method from One Rollout, Two Tracks.
First CVs in 48 hours, max five profiles per role, replacement from the bench at any point — the same commitments as everywhere on this site.
Classic or Adaptive, single seats or a synchronized team — first CVs land 48 hours after the briefing.
Get AUTOSAR CVs in 48hAUTOSAR (AUTomotive Open System ARchitecture) is the standardized software architecture the automotive industry uses so that ECU software from different suppliers works together — Classic Platform for deeply embedded real-time controllers, Adaptive Platform for the high-performance computers behind ADAS and connected functions.
Both — and we treat them as different hires. Classic profiles are screened for BSW/RTE configuration depth and hard real-time experience; Adaptive profiles for modern C++, POSIX and service-oriented middleware. The 200+ bench spans both.
Yes — the same team-leasing model as our SAP automotive delivery: complementary roles, one start date, contracts and replacements held by NDS. For German OEM and Tier-1 programmes, German is verified live during screening.
First anonymized profiles within 48 hours of the briefing. Genuinely rare combinations get an honest market read with a committed date instead of a guess — the same rule as every role we staff.
Put a slot in a calendar, or send the brief and we will come back to you. Either way you are talking to a partner, not a queue.
Thirty minutes, no deck. Whoever's calendar suits you — they take the call themselves.
Roles, platform, headcount, timeline. A link to a brief is even better.