Android Engineer
The Android app mirrors the iOS structure closely, deliberately: the same features, the same shared backend, the same release cadence. It is not a port that arrives late, and keeping that true is most of the job.
Parity does not mean copying. Each platform should feel like it belongs there, which means knowing when the iOS answer is the wrong one for Android and saying so.
What you would do
- Build in Kotlin and Jetpack Compose across chat, media, notes, tasks, and health
- Keep feature parity with iOS while letting the app feel native to Android
- Work on on-device processing, including stripping identifying detail before anything is sent
- Own the Play Store release path end to end
What we are looking for
- Strong Kotlin, and Compose experience beyond a side project
- Coroutines and Flow used in anger — streaming, cancellation, lifecycle
- Familiarity with the parts of Android that are genuinely hard: background work, permissions, fragmentation
- An eye for design, because you will often be implementing without a spec
How to apply
Email us with something you have built. A repo, an app, a write-up of a problem you solved — anything that shows how you think is worth more here than a CV.
Apply for Android Engineer