Android AOSP Engineer

About the Role

We’re looking for an experienced AOSP Engineer to work on deep Android system-level modifications and customizations.

We’ve built a product-focused GovTech platform that removes the gap between virtual and physical phones, and this role is critical in pushing Android beyond standard device behavior.

You will work directly with AOSP internals, modifying core system components, services, and hardware abstractions to achieve production-grade behavior under non-standard environments.

Responsibilities

• Customize and extend AOSP for specific product requirements
• Modify and debug Android system services (framework + native layers)
• Work with HALs, Binder IPC, and low-level system components
• Implement and adjust behavior related to:
  • Device identity & system properties
  • Networking, telephony, sensors, and system state
  • Power, battery, and lifecycle behavior
• Integrate and adapt Android builds for virtualized / emulated environments
• Debug complex issues across Java/Kotlin and native C++ layers
• Analyze system logs, traces, and crashes (logcat, tombstones, systrace, etc.)
• Collaborate with reverse engineers and backend teams on system behavior

Requirements

Core Skills

• Strong experience with AOSP (building, modifying, debugging)
• Solid knowledge of:
  • Android architecture (Framework, System Services, HAL)
  • Binder IPC and Android service model
• Proficiency in:
  • C++ (NDK / native layer)
  • Java / Kotlin (framework layer)

System-Level Understanding

• Experience with:
  • SELinux policies and system permissions
  • Android boot process (init, Zygote, system_server)
  • System properties and device configuration
• Ability to debug across layers (kernel ↔ HAL ↔ framework)

Tools

• adb, fastboot, logcat, systrace
• Debugging tools (gdb/lldb, ndk-stack)
• Build system (Soong / Make)

Who This Is For

This role is for engineers who:

• Enjoy working below the app layer
• Are comfortable breaking and rebuilding Android internals
• Prefer solving real system problems over building UI