Senior AOSP Platform Engineer

If you build Android itself — not just apps that run on Android — this role is for you.

At L4B Software, we are looking for a Senior AOSP Platform Engineer who enjoys working deep inside Android: understanding how the OS boots, how services communicate, how hardware meets the Android framework, how the platform is secured, and how difficult system-level problems are traced across multiple layers.

This is an opportunity to work on real embedded Android platforms, where engineering decisions directly affect security, reliability, performance, maintainability, and long-term product life.

Before You Apply

This is a low-level Android/AOSP platform engineering role — NOT an Android application-development position.

We are specifically looking for engineers with hands-on experience working inside the Android OS/AOSP platform and close to the BSP/hardware layer.

Your experience should include several of these areas:

AOSP Platform Development HAL/BSP Integration Binder/AIDL Native/System Services SoC/Vendor Integration SELinux Android Boot Linux/Kernel Interaction Device Tree Secure Boot AVB/dm-verity Encryption TEE/TrustZone Platform Security

If your experience is primarily Kotlin/Java + Android SDK application development, without hands-on AOSP/platform-level engineering, this position will not be the right match.

Working Model

Hybrid | Not fully remote

Candidates must be comfortable working within L4B's hybrid working model.

Immediate and short-notice joiners will be preferred, although strong candidates with highly relevant AOSP experience are still encouraged to apply.

Why L4B?

L4B Software engineers work where operating systems meet real products.

We develop secure and reliable operating-system platforms for embedded, regulated, security-sensitive, and long-lifecycle products.

Our engineering work spans:

Embedded Linux | Android/AOSP | BSP Integration | Platform Security | DevOps | System Validation

This means you won't be limited to one small part of the Android stack.

You'll work on complex platform problems where understanding how the complete system behaves matters.

The Role

As a Senior AOSP Platform Engineer, you will develop, customize, integrate, secure, debug, and maintain Android-based operating-system platforms for embedded products.

You will work across:

Android Framework Native/System Services Binder/AIDL HAL Vendor Components BSP Kernel/Firmware Hardware

You should be the kind of engineer who, when something breaks, wants to understand:

Where in the stack is this actually failing — and why?

You are not expected to spend your entire role developing Linux device drivers. However, you should be technically comfortable moving across Android, BSP, kernel, firmware, and hardware boundaries when debugging requires it.

What You'll Work On

• Build, customize, integrate, and maintain production AOSP platforms.
• Develop and modify Android framework, native, and system components.
• Develop and integrate Android system services and Binder/AIDL interfaces.
• Integrate and debug HAL and vendor platform components.
• Integrate SoC vendor software and BSP components into Android platforms.
• Debug complex issues spanning Android framework, native services, HAL, vendor, BSP, kernel, firmware, and hardware.
• Develop and troubleshoot SELinux policies.
• Work with Android boot flow, init, permissions, VINTF, and Project Treble.
• Integrate and maintain Android platform-security mechanisms.
• Support Secure Boot, Android Verified Boot, and verified platform configurations.
• Support CTS, VTS, and related Android platform-validation activities.
• Work with OTA and platform-update mechanisms.
• Investigate boot, networking, performance, stability, and system-reliability issues.
• Improve AOSP build, integration, automation, and CI/CD workflows.
• Collaborate with Embedded Linux, BSP, security, validation, firmware, and DevOps engineers.
• Create maintainable technical documentation for platform changes and integrations.

What We're Looking For

You should bring strong hands-on experience with AOSP at source/platform level — beyond Android SDK application development.

We'd expect you to be comfortable with:

• Android system architecture and the AOSP source tree
• Android framework, native services, and/or system services
• Strong C/C++ development
• Binder and AIDL
• HAL and vendor-component integration
• Android BSP and SoC vendor integration
• SELinux policy development and debugging
• Android boot flow, init, permissions, and platform configuration
• Linux and Android system-level debugging
• Diagnosing issues across multiple layers of the platform
• AOSP build systems such as Soong
• Git and structured software-development practices

Java/Kotlin experience at the Android platform level is valuable.

Java/Kotlin application-development experience alone is not sufficient for this role.

Extra Depth We'd Value

You don't need everything below, but deeper experience in these areas will make your profile particularly relevant:

• Qualcomm Android platforms and BSP/vendor integration
• Android Verified Boot (AVB)
• dm-verity
• FBE, dm-crypt, and Android encryption
• Android Keystore and KeyMint
• Hardware-backed keys / StrongBox
• Secure Boot and chain of trust
• ARM TrustZone / Trusted Execution Environments
• Hardware-backed attestation
• Secure key provisioning
• Anti-rollback mechanisms
• Secure platform updates
• Android A/B and Virtual A/B OTA
• CTS / VTS / GTS
• Android security-patch integration
• Vulnerability remediation
• VINTF / Project Treble
• Linux kernel and Device Tree
• Bootloader and firmware integration
• Android performance analysis and optimization
• Embedded, regulated, security-sensitive, or long-lifecycle products

You Might Be a Great Fit If...

You enjoy problems that don't have an obvious answer.

A bug appears in Android framework, but the real cause could be inside the HAL.

A service fails, but the issue originates in SELinux.

The device boots incorrectly, and you need to trace what happened across bootloader, kernel, init, vendor components, and Android.

A security requirement touches several layers of the platform rather than a single application.

That kind of cross-layer investigation is central to this role.

We want engineers who can go beyond fixing the visible symptom and understand what is actually happening inside the system.

What This Role Is NOT

Not Android App Development

If your core experience is:

Kotlin / Java / Android SDK / Jetpack / Compose / UI / Mobile Application Development

without substantial AOSP/platform-level experience, this role is not the right fit.

Not Pure Linux Driver Development

This is also not a position focused exclusively on writing Linux kernel drivers.

This IS Android Platform Engineering

We are looking for engineers who can:

Build it. Integrate it. Secure it. Debug it. Maintain it.

And understand how Android interacts with the layers underneath it.

What Success Looks Like

Over time, you become a technical owner of significant parts of the Android platform.

You can take an ambiguous system-level problem and:

Investigate isolate identify the responsible layer solve validate document

You help L4B deliver Android platforms that aren't simply functional builds, but are:

Secure Stable Maintainable Testable Reproducible Built for long-term product use

Interested?

If you have spent your career inside AOSP rather than only building applications on top of Android, we'd like to hear from you.

We hire for technical depth, relevant hands-on experience, and demonstrated engineering capability.

Equivalent practical experience is welcome where a formal degree isn't essential to the work.

Hybrid role | Fast joiners preferred

If this sounds like the kind of engineering you enjoy, apply and let's talk.