Senior Android Developer

Responsibilities:

• Build and maintain integrations toward Managed Google Play, Omnissa Workspace ONE (WS1), Samsung Knox, and Zero Touch enrollment for Android device provisioning at scale.

• Build proof-of-concept apps to investigate new hardware and SDKs early, ahead of production teams needing to integrate against them, effectively derisking hardware adoption for the wider organization. This work requires moving fast and accepting rougher code quality than production work.

• Develop and maintain a set of production Android applications, including:

• a device enrollment app used when hardware (smartphones, Android POS, self-checkout units) arrives in store,

• a device info and factory reset utility protected by Entra ID login,

• an app for firmware updates and error analysis on portable RFID readers,

• a background/login-time app that starts required services and collects device telemetry.

• Gather and structure data about the device fleet and related systems in BigQuery, and make it available to the wider organization both through direct data sharing and through dashboards in Looker Studio.

• Maintain and extend "RFID playground," an internal app used to test new RFID tags and technology ahead of production use.

• Maintain a small web app used by third-party suppliers to enroll devices into the system.

• Provide developer support to other software teams building on top of this platform.

We think you'll recognize yourself in a lot of these:

• You've worked across multiple technology stacks or environments over your career, rather than staying deep in just one language or platform.

• You have strong Android development experience, whether that's Kotlin and Jetpack Compose, Java and XML views, or you've worked in another modern declarative UI framework like SwiftUI, React Native, or Flutter. If it's the latter, you should be comfortable picking up Compose quickly.

• You're comfortable with backend development in a language like Node.js, Python, or Java on a cloud platform (ideally GCP). The concepts transfer easily between these, so we care more about the underlying skill than the specific language.

• You've structured and exposed data through BigQuery, or a comparable data warehouse, and maybe built or maintained dashboards (Looker Studio or similar BI tools) for non-technical stakeholders.

• You can shift between two modes naturally: careful, secure, well-tested code for production systems, and fast, pragmatic, exploratory coding for proofs of concept and hardware investigation, and you have a good sense for which one a task calls for.