Android Automotive OS · Career
Android Automotive OS (AAOS) engineers are not a large job market — but the companies looking for them are looking hard. Android keeps moving into cars through 2026, and people who understand both Android and automotive quality culture remain scarce.
This page is a practical map for anyone who wants to work on AAOS: where the jobs are, what each layer expects you to know, what it pays, and where to look. The technology itself is covered separately in Android Automotive OS explained.
Every "car Android" posting is one of these. Identify which, and the conversation gets shorter.
| Position | What you do | Layers | Suits |
|---|---|---|---|
| OEM (car maker) | Specify AAOS per vehicle line, drive GAS certification, manage suppliers, plan the HMI | All — but more deciding than coding | People who want the whole product and do not mind coordination and documents |
| Tier 1 / head-unit maker | Board support, VHAL implementation, AOSP customisation, certification testing | HAL, framework, kernel | People comfortable with C++ and AOSP builds — the deepest work |
| Contract shops / staffing | Join OEM or Tier 1 programs for framework changes, apps and test automation | Depends on the program; app to framework | People who want experience fast and accept variable assignments |
| App publishers | Bring an existing app to cars via the Car App Library or Car Ready Mobile Apps | App layer only | Existing Android developers who want cars as one more distribution channel |
The best-paid work sits in Tier 1 framework and HAL roles and at global OEMs; the easiest entry is through contract shops and the app layer. What earns the "AAOS engineer" premium is usually one of two things: having worked below the VHAL, or having taken a product through GAS certification.
"I know Android" is not enough because automotive adds layers above and below it.
| Layer | Skills | How to prove it |
|---|---|---|
| App | Kotlin, Jetpack, androidx.car.app (Car App Library), large-screen support, the three Car app quality tiers | One templated Car App Library app running on the AAOS emulator, with notes |
| Framework | Building AOSP, Java/Kotlin system services, CarService, CarPropertyManager, SystemUI and launcher changes, SELinux | Having built AOSP yourself and booted sdk_car_x86_64; one applied patch counts for a lot |
| HAL / native | C++, AIDL (formerly HIDL), VHAL implementation, Audio HAL, CAN/Ethernet basics, Linux device drivers | Adding one property to the fake VHAL and reading it from an app |
| Quality / process | CTS/VTS, GAS certification requirements, Automotive SPICE, ISO 26262 fundamentals, requirements traceability | Experience running certification suites beats certificates; using the vocabulary correctly changes the tone of an interview |
| Common | Git, Gerrit, reading logcat and dumpsys, and — outside English-speaking teams — the ability to read English primary sources | Being able to explain AOSP documentation to colleagues in their own language is valued more than people expect |
A common mix-up
Android Auto experience is not AAOS experience. Android Auto is phone-side projection; it touches neither the car's hardware nor its vehicle data. Job postings sometimes blur the two, so asking "which one do you mean?" in an interview is not rude — it marks you as someone who understands the field.
Ranges observed in public listings and agency rate cards in September 2026. They vary widely by country, experience and language, and are not a promise.
| Segment | Range | Notes |
|---|---|---|
| Employee, embedded/automotive, Android experience but new to AAOS | US $95k–140k · EU €55k–80k · JP ¥4.5–7M | The usual entry point; where the first AAOS track record is built |
| Employee, AAOS / AOSP framework experience | US $140k–200k · EU €75k–110k · JP ¥6–10M | Tier 1s and large integrators; below-the-VHAL work sits at the top of the range |
| Global OEM / Tier 1, senior or staff | US $180k–260k+ · EU €95k–140k · JP ¥8–15M | Design reviews in English; equity is common at OEM software subsidiaries |
| Contract (hourly / monthly) | US $80–150/h · EU €70–120/h · JP ¥0.7–1.2M/month | Sits above generic Android rates, but the number of open contracts is small |
The structure matters more than the numbers: AAOS wants both Android app skills and embedded C++, so people who have both are typically paid 10–20% above those with one. Which also means that a developer with one side can move their rate by self-teaching the other.
Three channels, and AAOS looks different in each.
One sentence for a recruiter (copy it)
"N years of Android app development. Self-taught AAOS: built AOSP, booted the sdk_car emulator, and read vehicle properties through CarPropertyManager. One published Car App Library app. Looking for in-vehicle framework or HAL work." — If you can say that, you are treated as a candidate who speaks the language, even without a job title to show for it.
Everything runs on a laptop.
Car.createCar() → CarPropertyManager. This is the point where you can honestly say you have touched AAOSlunch sdk_car_x86_64-userdebug and make your own emulator image. It takes time, but it moves you into the framework-layer pool