How to hire Android developers who ship on real devices

Kotlin is the entry ticket. What you pay for is someone who has handled cheap phones, battery limits and Play policy deadlines before.

Android is the platform where an app can work perfectly on the developer's phone and fall apart on your users'. Thousands of device models, manufacturer skins that kill background work, screens from small budget phones to foldables, and a Google Play policy calendar that changes every year. So when you hire Android developers, Kotlin skill is the entry ticket. What you are really paying for is someone who has dealt with all of that before.

This guide covers the Kotlin and Jetpack Compose skills to look for, how to check device testing and Google Play policy knowledge, interview questions, a test task and typical rates. If you want developers who already work this way, see our Android developers for hire.

The core skills: Kotlin, Compose and modern Android

Modern Android development has settled on a fairly standard toolkit. A strong Kotlin developer should be fluent in most of it:

• Kotlin, properly. Null safety, data and sealed classes, extension functions, and above all coroutines and Flow for asynchronous work. Ask how they cancel work when a screen closes.
• Jetpack Compose. The default way to build Android UI today. Look for an understanding of state hoisting, recomposition and how to keep lists smooth. Older apps still contain XML views, so comfort with both is a plus.
• Architecture components. ViewModel, a clear UI / domain / data split and dependency injection, usually with Hilt.
• Persistence and background work. Room for local data, DataStore for settings and WorkManager for jobs that must survive the app being closed.
• Networking. Retrofit or Ktor with sensible timeouts, retries and token refresh.
• Testing and tooling. Unit tests with coroutine test tools, Compose UI tests, Gradle build variants for staging and production, and Android Studio's profilers for memory and startup time.

Ask about the libraries your app actually needs too: Google Play Billing for subscriptions, Firebase Cloud Messaging for push, CameraX, Maps or Bluetooth.

If you plan an iOS app later, ask about Kotlin Multiplatform too. Some teams use it to share networking and business logic between Android and iOS while keeping each platform's UI native. You don't need it on day one, but a developer who structures the data layer cleanly makes that option cheaper later.

Device testing: the skill most candidates oversell

"I test on emulators" is not an Android testing strategy. Ask candidates to describe their device matrix. A reasonable one for a consumer app looks something like this:

A good developer pairs a few real devices with a cloud device lab and watches crash and ANR (app not responding) reports in Play Console after release. Ask what their last app's crash-free rate looked like and what they did to improve it.

Google Play policy knowledge to check

Play rules change on a schedule, and a developer who doesn't follow them can stall your launch or block an update. Three things worth asking about:

• Target API level. According to Android's target API level requirements, from August 31, 2026 new apps and app updates must target Android 16 (API level 36) or higher, with an extension available on request to November 1, 2026. Ask what changed for them when they raised targetSdk last time.
• Testing before production. Google's testing requirements say new personal developer accounts must run a closed test with at least 12 testers opted in for 14 continuous days before applying for production access. Organization accounts avoid this, which is one more reason to register under your company.
• Data safety and permissions. The Play Console data safety form must match what the app and its SDKs actually collect, and sensitive permissions such as background location need a clear justification. Ask how they audit third-party SDKs.

We cover the wider set of Play Console requirements in our Android app development guide.

Interview questions for Kotlin developers

Skip definitions. Ask about decisions and incidents, and expect specifics.

1. "How do you make sure a sync job runs even if the user closes the app?" Listen for WorkManager, constraints, retries and awareness of manufacturer battery restrictions.
2. "A Compose list stutters on a cheap phone. Walk me through fixing it." Expect profiling, stable keys, avoiding unnecessary recomposition, image sizing and pagination.
3. "How do you handle configuration changes and process death?" Good answers mention ViewModel, SavedStateHandle and testing with "don't keep activities".
4. "What was your last Play Console rejection or policy warning?" Anyone who ships regularly has one.
5. "How do you set up staging and production builds?" Build variants, separate API endpoints and Firebase projects, and signing kept out of the repository.
6. "Which events would you track for our app?" This shows whether they think about the business or only the code.

A paid Android test task

Four to six hours, paid, and close to real work. One that tests the Android-specific skills above:

• A Compose app with a paginated list from a public API and a detail screen.
• Room as the local source of truth, so the list works offline and refreshes when the network returns.
• A WorkManager job that refreshes data periodically.
• Correct behavior on rotation and after process death.
• Unit tests for the repository and one Compose UI test.
• A README explaining structure, trade-offs and what's missing.

Run it on a low-end device, not just an emulator. Then hold a 30-minute walkthrough where they make one change live. It quickly shows whether the work is theirs.

Android developer rates and hiring models

Typical market ranges for experienced Android developers, not quotes. They vary with seniority, location and what's included.

Seniority moves the number more than geography. A senior developer who has shipped and maintained several Play Store apps often costs well above a mid-level one, and usually saves more than the difference in rework, crash fixes and policy surprises. Compare total cost for the same scope, not hourly rates.

Choosing the model:

• Freelancer: works when you have an Android lead who reviews code, and the task is well defined.
• Dedicated developer via a vendor: suits an ongoing roadmap that you manage, with the vendor covering replacement.
• Agency team: best when you need the whole app delivered, including backend, design, QA and Play submission.

If you also need iOS, compare a Flutter team against two native teams before you hire. For offshore options, see our guide to choosing an Android app development company in India.

Accounts and ownership

• Register the Google Play Console account as an organization in your company's name. It has a one-time US$25 registration fee and identity verification.
• Invite developers as Play Console users with only the permissions they need. Keep the owner role yourself.
• Use Play App Signing and make sure your company, not one developer, controls the upload key.
• Keep the code in your Git organization and Firebase and cloud projects under company accounts.

Red flags when you hire an Android app developer

• Only emulator testing and no real low-end device in the process.
• No opinion on battery restrictions or background work on different manufacturers.
• Unaware of the target API cycle or the data safety form.
• Publishing under their own Play account, which makes transferring the app later slow and painful.
• Signing keys on their laptop and nowhere else.

Hiring Android developers through Appryze

Our hire Android developers service gives you Kotlin and Compose engineers from our New Delhi team, with call times that overlap US business hours and weekly written updates. If you need the whole app built, our app development service covers Android, iOS and web, with a fixed-price written quote within 24 hours, free Google Play submission and one month of launch marketing. You own the code and the Play Console account from the start.

Frequently asked questions

How much does it cost to hire an Android developer?

Typical freelance rates run from about $15 to $40 an hour in India to $65 to $150 in the US, and agency blended rates are higher because they include QA, design and project management. These are typical ranges, not quotes. Google Play also charges a one-time US$25 registration fee for the developer account.

What skills should an Android developer have in 2026?

Fluent Kotlin with coroutines and Flow, Jetpack Compose, ViewModel-based architecture with dependency injection, Room and WorkManager, and solid testing. Just as important are real-device testing across cheap and premium phones, handling battery restrictions, and keeping up with Google Play policies such as target API level deadlines.

What target API level does Google Play require?

According to Android's developer documentation, from August 31, 2026 new apps and app updates must target Android 16, API level 36, or higher, with an extension available on request to November 1, 2026. Wear OS, Android TV and some other form factors have lower requirements. Check the current page before each release.

Should I hire a Kotlin developer or a Flutter developer?

Hire a Kotlin developer if your app is Android-first, relies on hardware or background work, or must run well on low-end phones. If you need both Android and iOS with mostly standard screens, a Flutter developer can cover both from one codebase. Decide the platform before you start interviewing so candidates are comparable.

How do I test an Android developer before hiring?

Give a short paid task, such as a Compose list app with Room offline caching, a WorkManager refresh job and tests. Run it on a low-end real device, check it survives rotation and process death, then ask them to walk you through the code and make a small change live.

Keep reading

More in Hire Android Developers · All app development guides