Android Developer

Job Description

Android Build & Integration

Deep knowledge of the Android build system (AOSP / AAOS):

Soong / Blueprint

Makefiles

Product configuration (device.mk, product.mk, Android.bp)

Experience with AOSP repo tool, manifest management, and branch merges.

Ability to perform codebase synchronization and resolve merge conflicts when integrating DPD changes.

Configuration Management

Understand Android product configurations, overlays, and resource management.

Experience managing:

system, vendor, and product partitions

Feature flags, system properties, and app permissions

Familiar with device tree structures, build variants, and flavor definitions.

DPD (Device / Platform Definition) Integration

Integrate DPD updates into Android build and app configuration:

Update configuration XMLs, manifests, or property files.

Merge changes to feature sets, hardware mappings, or resource definitions.

Validate that changes are correctly reflected in the physical app layer (HVAC, media, connectivity applets, etc.).

Coordinate with the DPD / platform team to understand what's changed (e.g., new hardware variant, feature toggle, or sensor addition).

System-Level Android & Applet Awareness

Understanding of how applets consume system configuration:

Resource overlays, system properties, or service APIs.

Ability to trace configuration → framework → applet flow.

Work closely with framework engineers to ensure new DPD features are exposed through the applet framework.

Validation & Testing

Perform smoke tests and integration validation after DPD updates:

Boot validation, system service initialization, applet startup.

Ensure no regression in functionality or performance.

Use ADB, logcat, and system tracing tools to debug integration issues.

Automate sanity checks and configuration validation (Python/Bash scripting).

Job Responsibilities

Integration engineer who acts as the bridge between platform configuration, applets, and Android system builds.

Manage updates from DPD (which likely defines hardware mappings, feature sets, or OEM configuration data) and ensure that the physical app layer (the in-vehicle applets and their framework) stays in sync with the latest platform versions.

Kind of continuous integration and configuration management for the in-vehicle Android environment.