Android Developer Job Description Template (2026)

Full JD (copy-ready)

Paste this into your ATS or careers page. Edit the company name and any bracketed placeholders.

# Android Developer — Job Description

## Role summary
An Android Developer owns the native Android application for our product: building and maintaining the Kotlin and Jetpack Compose app, shipping performant and stable features, structuring the code in MVVM or MVI, managing Play Store releases, and collaborating with designers and backend engineers to turn Figma and API contracts into production Android UI that holds its frame budget and crash-free rate.

## Responsibilities
- Build new features and full screen flows in Kotlin and Jetpack Compose against Figma specs, with unit and UI test coverage for each.
- Structure features in MVVM or MVI with ViewModel, unidirectional UiState, and clean module boundaries.
- Model async and reactive work with coroutines, Flow, and StateFlow, handling cancellation, configuration changes, and process death correctly.
- Persist data with Room and DataStore and build offline-first flows with proper cache invalidation.
- Integrate REST and GraphQL APIs through Retrofit, OkHttp, or Apollo with robust error, retry, and auth handling.
- Manage signed AAB builds, staged rollouts, and the internal, closed, and open testing tracks in Play Console.
- Profile and fix jank, cold start, and memory issues using the Android Studio profiler, Macrobenchmark, and Baseline Profiles.
- Triage crashes and ANRs in Firebase Crashlytics and drive the crash-free rate up release over release.
- Write JUnit and Turbine unit tests plus Espresso or Compose UI tests for critical user flows.
- Keep CI green on every PR with Gradle build caching and instrumented tests on emulators or a device farm.
- Migrate legacy XML View and Fragment screens to Compose incrementally without regressing existing behavior.
- Review peer pull requests with specific feedback on architecture, performance, lifecycle correctness, and test coverage.

## Must-have skills
- 3+ years shipping production Android apps in Kotlin, including coroutines and Flow.
- Hands-on Jetpack Compose experience, including state hoisting, recomposition, and Material 3 theming.
- Solid grasp of MVVM or MVI, ViewModel, and the Android lifecycle including configuration changes and process death.
- Experience with Room, Retrofit or Apollo, and dependency injection via Hilt or Koin.
- Comfortable writing JUnit unit tests and Espresso or Compose UI tests, and reading CI output.
- Has taken at least one app through the full Play Store release process, including signed AAB and staged rollout.
- Performance profiling with the Android Studio profiler — able to diagnose jank and cold start without hand-holding.
- Strong written English for async code review, Slack threads, and spec docs.

## Nice-to-have skills
- Kotlin Multiplatform experience for sharing business logic across Android and iOS.
- Baseline Profiles, Macrobenchmark, and R8 tuning for startup and size wins.
- Experience migrating a large XML View codebase to Jetpack Compose.
- Familiarity with Firebase (Crashlytics, Remote Config, Cloud Messaging) and A/B testing.
- Published an app to the Play Store as an individual or maintained one with real users.

## Tools and technology
- Kotlin
- Jetpack Compose
- Coroutines & Flow
- Hilt
- Room & DataStore
- Retrofit / OkHttp
- WorkManager
- Firebase Crashlytics
- Gradle
- Android Studio / Play Console

## Reporting structure
Reports to the Engineering Manager or Mobile Lead. Collaborates daily with product designers (Figma handoff), backend engineers (API contracts), QA, and the product manager for the feature area.

## Success metrics (KPIs)
- Weekly PR throughput and review turnaround on own and peer PRs.
- Crash-free user rate and ANR rate tracked per release with a hard floor that blocks rollout if breached.
- Cold start and key-screen frame time held inside budget, measured with Macrobenchmark.
- Test coverage on behavioral paths — not line count — maintained or improved each sprint.
- App size (AAB) held flat or reduced release over release via R8 and dependency hygiene.
- Staged rollouts completed without a halt or rollback for regressions.