Android Software Engineer — Agentic AI Platform

Awear is hiring an Android Software Engineer to build its Android mobile experience and wearable Agentic OS platform. The role spans AOSP-based wearable software, agent interaction design, platform architecture for a future RTOS transition, firmware integration, and on-device processing.

Responsibilities:

• This is not a standard Android engineering role. You will be working across two surfaces simultaneously — a standard Android mobile app that mirrors an iOS experience, and an Android Open Source Project (AOSP)-based custom Android build running on wearable hardware. You will be making foundational decisions about how an agentic AI platform feels and behaves in a wearable form factor — a problem that has no established conventions and very few reference points
• You should also know that the wearable platform will expand from AOSP to RTOS asap. The right candidate for this role is excited by that transition rather than daunted by it — someone who thinks about platform architecture and is comfortable moving between layers of the stack as the hardware evolves
• You will work directly with the CEO and a small, high-trust engineering team across Silicon Valley, Paris, including close collaboration with a China-based firmware team who own the hardware bring-up
• We actively use AI development tools across our engineering team — Cursor, Claude, Copilot — and expect engineers who use them seriously as a core part of their workflow
• A standard Android mobile app at feature parity with our existing iOS experience — bringing the Agentic OS to Android users with the same interaction quality and design integrity
• An AOSP-based client for wearable hardware — building the application layer on top of a custom Android stack running on a constrained wearable form factor
• The agent interaction surface for wearables — defining what it means to interact with an always-on AI when there is no touchscreen, no keyboard, and no conventional UI paradigm to fall back on
• A platform architecture that is designed to survive the transition from AOSP to RTOS — thinking ahead so that the work done today does not need to be discarded when the platform evolves
• Close integration with the firmware team — bridging the application layer and the hardware bring-up work happening in Shenzhen
• On-device processing integrations — working to minimize cloud dependency and maximize what runs locally on constrained hardware

Requirements:

• 4+ years of Android engineering experience with strong Kotlin skills
• Solid understanding of Android platform internals — not just application-layer Android but a genuine understanding of how the platform works beneath the surface
• AOSP experience — having worked with or built on top of the Android Open Source Project is a meaningful advantage for this role and the nature of the wearable work makes it highly desirable
• Experience with constrained or non-standard hardware environments — wearables, embedded Android, custom form factors, or similar
• Comfort working at the intersection of application software and hardware — you will be collaborating closely with firmware engineers and need to understand their world well enough to have productive conversations across the boundary
• Strong written English and proven ability to work effectively in a remote and distributed team
• Familiarity with RTOS concepts is a plus given the platform transition planned for later this year
• Active user of AI-assisted development tools with a genuine point of view on how to use them well
• experience with voice or audio-first interfaces, always-on background processing, custom input methods or non-touch interaction paradigms, wearable or AR platform development