Android / Kotlin: market
Data as of November 19, 2026: 428 open Android / Kotlin jobs, 39% remote among jobs that state a work format; median advertised salary $6,521/mo (from 38 postings that state a salary). Source: Zorky, updated daily.
Android development — native mobile development for the Android platform in Kotlin (official language since 2019) or Java (legacy). The largest mobile segment in CIS thanks to Android dominance in the region (70%+ of devices). Role family: Android Developer (general — Kotlin + Jetpack Compose + MVVM/MVI architecture), Senior Android Engineer (Compose Multiplatform + modular architecture), Junior Java Android (legacy maintenance — banking apps on the old stack), Android Tech Lead (SDK/lib architecture + mentoring), Android Game Developer (Unity/Unreal on Android — separate niche). Stack: Kotlin (must — coroutines, flow, generics, sealed classes), Jetpack Compose (modern declarative UI framework — replaces XML layouts, dominator of new projects 2024–2026), XML layouts (legacy in existing codebases), Coroutines + Flow (must for async), MVI/MVVM/Clean Architecture, Hilt (DI — Dagger-based), Room (SQLite ORM), Retrofit + OkHttp (REST), Kotlin Serialization (modern) or Moshi/Gson, Coil/Glide (image loading), Navigation Component or Compose Navigation, Firebase (Crashlytics + Analytics + Remote Config + Cloud Messaging), JUnit5+Mockk+Espresso+Compose Testing. Top stack: kotlin, jetpack compose, java, git, agile. Among jobs with a stated work format, 39% are remote. Senior Android ≈ Senior Backend in Moscow; at banks/fintech +10-15% for regulatory requirements.
Data as of:
Key numbers for the Android / Kotlin market: open jobs, median salary, observed talent pool and remote share.
The Android / Kotlin market currently has 428 open roles, 375 of them freshly observed. Median salary $6,521/mo.
Among jobs with a stated work format, 39% are remote. Mobile development is cloud-based by nature (Firebase Test Lab for real devices). Russian product companies — hybrid or remote. Banks — more often office due to compliance.
⚠ salary known for 38 of 428 jobs; remote share from 346 with a stated format; 375 counted as fresh observations; trend and hiring difficulty are not shown
Timeline: postings and sources
How many Android / Kotlin postings appeared each week since Jun 1, and from how many sources. The lower chart separates market growth from coverage growth: a jump in the week new sources were connected means we started seeing more, not that the market grew.
New postings per week
Chart data
| Period | New postings per week |
|---|---|
| 2026-06-01 | 20 |
| 2026-06-08 | 11 |
| 2026-06-15 | 5 |
| 2026-06-22 | 45 |
| 2026-06-29 | 41 |
| 2026-07-06 | 46 |
| 2026-07-13 | 41 |
| 2026-07-20 | 57 |
| 2026-07-27 | 35 |
| 2026-08-03 | 53 |
| 2026-08-10 | 19 |
| 2026-08-17 | 30 |
| 2026-08-24 | 17 |
| 2026-08-31 | 28 |
| 2026-09-07 | 24 |
| 2026-09-14 | 30 |
| 2026-09-21 | 162 |
| 2026-09-28 | 61 |
| 2026-10-05 | 82 |
| 2026-10-12 | 263 |
| 2026-10-19 | 135 |
| 2026-10-26 | 92 |
| 2026-11-02 | 97 |
| 2026-11-09 | 83 |
Active sources per week
Sources over the period: 133. ▲ — a week with a large batch of new sources.
Chart data
| Period | Active sources |
|---|---|
| 2026-06-01 | 8 |
| 2026-06-08 | 9 |
| 2026-06-15 | 5 |
| 2026-06-22 | 12 |
| 2026-06-29 | 23 |
| 2026-07-06 | 21 |
| 2026-07-13 | 26 |
| 2026-07-20 | 35 |
| 2026-07-27 | 19 |
| 2026-08-03 | 17 |
| 2026-08-10 | 11 |
| 2026-08-17 | 20 |
| 2026-08-24 | 14 |
| 2026-08-31 | 11 |
| 2026-09-07 | 18 |
| 2026-09-14 | 21 |
| 2026-09-21 | 29 |
| 2026-09-28 | 30 |
| 2026-10-05 | 33 |
| 2026-10-12 | 43 |
| 2026-10-19 | 36 |
| 2026-10-26 | 31 |
| 2026-11-02 | 32 |
| 2026-11-09 | 37 |
New sources connected: Jun 8 +8 · Jun 22 +9 · Jun 29 +14 · Jul 6 +10 · Jul 13 +13 · Jul 20 +12 · Oct 5 +9 · Oct 12 +9 · all weeks (23) in the table
| Week | New sources | New postings |
|---|---|---|
| Jun 8 | +8 | 11 |
| Jun 15 | +2 | 5 |
| Jun 22 | +9 | 45 |
| Jun 29 | +14 | 41 |
| Jul 6 | +10 | 46 |
| Jul 13 | +13 | 41 |
| Jul 20 | +12 | 57 |
| Jul 27 | +4 | 35 |
| Aug 3 | +3 | 53 |
| Aug 10 | +1 | 19 |
| Aug 17 | +4 | 30 |
| Aug 24 | +2 | 17 |
| Aug 31 | +1 | 28 |
| Sep 7 | +1 | 24 |
| Sep 14 | +3 | 30 |
| Sep 21 | +2 | 162 |
| Sep 28 | +3 | 61 |
| Oct 5 | +9 | 82 |
| Oct 12 | +9 | 263 |
| Oct 19 | +4 | 135 |
| Oct 26 | +2 | 92 |
| Nov 2 | +4 | 97 |
| Nov 9 | +5 | 83 |
The current week is not over yet and is not shown: an incomplete week would look like a drop.
Week = posting first-seen date, all statuses; postings are selected by the same rule as this page's counter. Sources are distinct collection channels; their names are not published.
Chart data
| Week | New postings per week | Active sources |
|---|---|---|
| 2026-06-01 | 20 | 8 |
| 2026-06-08 | 11 | 9 |
| 2026-06-15 | 5 | 5 |
| 2026-06-22 | 45 | 12 |
| 2026-06-29 | 41 | 23 |
| 2026-07-06 | 46 | 21 |
| 2026-07-13 | 41 | 26 |
| 2026-07-20 | 57 | 35 |
| 2026-07-27 | 35 | 19 |
| 2026-08-03 | 53 | 17 |
| 2026-08-10 | 19 | 11 |
| 2026-08-17 | 30 | 20 |
| 2026-08-24 | 17 | 14 |
| 2026-08-31 | 28 | 11 |
| 2026-09-07 | 24 | 18 |
| 2026-09-14 | 30 | 21 |
| 2026-09-21 | 162 | 29 |
| 2026-09-28 | 61 | 30 |
| 2026-10-05 | 82 | 33 |
| 2026-10-12 | 263 | 43 |
| 2026-10-19 | 135 | 36 |
| 2026-10-26 | 92 | 31 |
| 2026-11-02 | 97 | 32 |
| 2026-11-09 | 83 | 37 |
Remote work over time
Share of Android / Kotlin postings offering fully remote work, per week.
Remote postings, %
Chart data
| Period | Remote |
|---|---|
| 2026-06-01 | 52.6 |
| 2026-06-08 | 50 |
| 2026-06-15 | — |
| 2026-06-22 | 52.4 |
| 2026-06-29 | 58.1 |
| 2026-07-06 | 44.4 |
| 2026-07-13 | 33.3 |
| 2026-07-20 | 38.9 |
| 2026-07-27 | 67.9 |
| 2026-08-03 | 28 |
| 2026-08-10 | 58.3 |
| 2026-08-17 | 25 |
| 2026-08-24 | 26.7 |
| 2026-08-31 | 40.9 |
| 2026-09-07 | 5 |
| 2026-09-14 | 47.6 |
| 2026-09-21 | 55.9 |
| 2026-09-28 | 42.1 |
| 2026-10-05 | 54.2 |
| 2026-10-12 | 41.1 |
| 2026-10-19 | 61.2 |
| 2026-10-26 | 42.6 |
| 2026-11-02 | 41.7 |
| 2026-11-09 | 44.4 |
The share is among postings that state a format (remote, hybrid, office). Weeks with fewer than 10 such postings are left blank.
Chart data
| Week | Remote |
|---|---|
| 2026-06-01 | 52.6 |
| 2026-06-08 | 50 |
| 2026-06-15 | — |
| 2026-06-22 | 52.4 |
| 2026-06-29 | 58.1 |
| 2026-07-06 | 44.4 |
| 2026-07-13 | 33.3 |
| 2026-07-20 | 38.9 |
| 2026-07-27 | 67.9 |
| 2026-08-03 | 28 |
| 2026-08-10 | 58.3 |
| 2026-08-17 | 25 |
| 2026-08-24 | 26.7 |
| 2026-08-31 | 40.9 |
| 2026-09-07 | 5 |
| 2026-09-14 | 47.6 |
| 2026-09-21 | 55.9 |
| 2026-09-28 | 42.1 |
| 2026-10-05 | 54.2 |
| 2026-10-12 | 41.1 |
| 2026-10-19 | 61.2 |
| 2026-10-26 | 42.6 |
| 2026-11-02 | 41.7 |
| 2026-11-09 | 44.4 |
Technologies over time
How the share of Android / Kotlin postings mentioning each of the top technologies changed.
Postings mentioning the technology, %
Chart data
| Period | Kotlin | Java | jetpack compose |
|---|---|---|---|
| 2026-09-21 | 84.1 | 20.5 | 50 |
| 2026-09-28 | 89.4 | 29.8 | 44.7 |
| 2026-10-05 | 89.4 | 28.8 | 48.5 |
| 2026-10-12 | 58.8 | 47.4 | 19.1 |
| 2026-10-19 | 86.3 | 29.1 | 66.7 |
| 2026-10-26 | 86.5 | 36.5 | 44.6 |
| 2026-11-02 | 83.3 | 43.6 | 39.7 |
| 2026-11-09 | 85.3 | 22.7 | 56 |
The series starts on Sep 21: there is no data before that.
Share among postings with a tagged stack; the series starts on Aug 10: earlier stack tags were assigned differently. Weeks with fewer than 20 tagged postings are left blank.
Chart data
| Week | Kotlin | Java | jetpack compose | android | cloud |
|---|---|---|---|---|---|
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | — | — | — | — | — |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | — | — | — | — | — |
| 2026-09-07 | — | — | — | — | — |
| 2026-09-14 | — | — | — | — | — |
| 2026-09-21 | 84.1 | 20.5 | 50 | 0 | 6.8 |
| 2026-09-28 | 89.4 | 29.8 | 44.7 | 6.4 | 6.4 |
| 2026-10-05 | 89.4 | 28.8 | 48.5 | 22.7 | 19.7 |
| 2026-10-12 | 58.8 | 47.4 | 19.1 | 5.2 | 14.9 |
| 2026-10-19 | 86.3 | 29.1 | 66.7 | 11.1 | 2.6 |
| 2026-10-26 | 86.5 | 36.5 | 44.6 | 9.5 | 6.8 |
| 2026-11-02 | 83.3 | 43.6 | 39.7 | 14.1 | 14.1 |
| 2026-11-09 | 85.3 | 22.7 | 56 | 13.3 | 17.3 |
Countries over time
How the share of Android / Kotlin postings in each of the top countries changed, per week.
Postings in the country, %
Chart data
| Period | Poland | USA | Russia |
|---|---|---|---|
| 2026-06-22 | 66.7 | 3 | 3 |
| 2026-06-29 | 16.2 | 18.9 | 18.9 |
| 2026-07-06 | 10 | 35 | 17.5 |
| 2026-07-13 | 9.1 | 27.3 | 21.2 |
| 2026-07-20 | 19.2 | 19.2 | 23.1 |
| 2026-07-27 | 45.8 | 8.3 | 16.7 |
| 2026-08-03 | 6.4 | 21.3 | 6.4 |
| 2026-08-10 | — | — | — |
| 2026-08-17 | 3.7 | 11.1 | 40.7 |
| 2026-08-24 | — | — | — |
| 2026-08-31 | 3.8 | 0 | 11.5 |
| 2026-09-07 | 4.8 | 4.8 | 23.8 |
| 2026-09-14 | 3.8 | 23.1 | 23.1 |
| 2026-09-21 | 5.7 | 10.2 | 7.6 |
| 2026-09-28 | 17 | 15.1 | 18.9 |
| 2026-10-05 | 37.1 | 11.4 | 14.3 |
| 2026-10-12 | 13.3 | 27.2 | 6.7 |
| 2026-10-19 | 20.8 | 9.2 | 7.7 |
| 2026-10-26 | 13.9 | 16.5 | 13.9 |
| 2026-11-02 | 20.9 | 16.3 | 4.7 |
| 2026-11-09 | 19.7 | 7 | 16.9 |
The series starts on Jun 22: there is no data before that.
Share among postings with a known country; the chart shows the five countries with the most postings over six months. Weeks with fewer than 20 postings with a known country are left blank. A rising share can mean a newly connected source in that country rather than market growth.
Chart data
| Week | Poland | USA | Russia | India | UK |
|---|---|---|---|---|---|
| 2026-06-01 | — | — | — | — | — |
| 2026-06-08 | — | — | — | — | — |
| 2026-06-15 | — | — | — | — | — |
| 2026-06-22 | 66.7 | 3 | 3 | 0 | 3 |
| 2026-06-29 | 16.2 | 18.9 | 18.9 | 0 | 2.7 |
| 2026-07-06 | 10 | 35 | 17.5 | 5 | 5 |
| 2026-07-13 | 9.1 | 27.3 | 21.2 | 0 | 0 |
| 2026-07-20 | 19.2 | 19.2 | 23.1 | 7.7 | 9.6 |
| 2026-07-27 | 45.8 | 8.3 | 16.7 | 4.2 | 0 |
| 2026-08-03 | 6.4 | 21.3 | 6.4 | 2.1 | 2.1 |
| 2026-08-10 | — | — | — | — | — |
| 2026-08-17 | 3.7 | 11.1 | 40.7 | 3.7 | 14.8 |
| 2026-08-24 | — | — | — | — | — |
| 2026-08-31 | 3.8 | 0 | 11.5 | 0 | 11.5 |
| 2026-09-07 | 4.8 | 4.8 | 23.8 | 9.5 | 9.5 |
| 2026-09-14 | 3.8 | 23.1 | 23.1 | 15.4 | 0 |
| 2026-09-21 | 5.7 | 10.2 | 7.6 | 7 | 7.6 |
| 2026-09-28 | 17 | 15.1 | 18.9 | 5.7 | 3.8 |
| 2026-10-05 | 37.1 | 11.4 | 14.3 | 12.9 | 2.9 |
| 2026-10-12 | 13.3 | 27.2 | 6.7 | 8.3 | 5.6 |
| 2026-10-19 | 20.8 | 9.2 | 7.7 | 2.3 | 5.4 |
| 2026-10-26 | 13.9 | 16.5 | 13.9 | 7.6 | 2.5 |
| 2026-11-02 | 20.9 | 16.3 | 4.7 | 11.6 | 9.3 |
| 2026-11-09 | 19.7 | 7 | 16.9 | 4.2 | 11.3 |
Clean market: hiring index
The same 7,505 employer job boards; the posting count comes from the board itself. Connecting new sources does not move this index — it shows the market, not our coverage. This is the whole panel market, not just Android / Kotlin.
Hiring index, Oct 16 = 100
Chart data
| Period | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
Chain index: each day compares only boards polled on both that day and the previous one; outliers and platform-wide polling outages are excluded. Days with no comparable pairs are left blank.
Chart data
| Day | Hiring index |
|---|---|
| 2026-10-16 | 100 |
| 2026-10-17 | 100.03 |
| 2026-10-18 | 99.76 |
| 2026-10-19 | 99.68 |
| 2026-10-20 | 99.27 |
| 2026-10-21 | 98.6 |
| 2026-10-22 | 99.07 |
| 2026-10-23 | 97.4 |
| 2026-10-24 | 97.41 |
| 2026-10-26 | 97.33 |
| 2026-10-27 | 96.76 |
| 2026-10-28 | 96.21 |
| 2026-10-29 | 95.17 |
| 2026-10-30 | 95.13 |
| 2026-10-31 | 93.65 |
| 2026-11-01 | 93.33 |
| 2026-11-02 | 92.67 |
| 2026-11-03 | 92.65 |
| 2026-11-04 | 92.41 |
| 2026-11-05 | 92.13 |
| 2026-11-06 | 90.44 |
| 2026-11-07 | 90.48 |
| 2026-11-08 | 90.45 |
| 2026-11-10 | 90.29 |
| 2026-11-11 | 90.22 |
| 2026-11-13 | 90.12 |
| 2026-11-14 | 89.7 |
| 2026-11-15 | 89.68 |
| 2026-11-16 | 89.62 |
| 2026-11-18 | 88.91 |
| 2026-11-19 | 88.02 |
How many open Android / Kotlin jobs there are and how many matching specialists Zorky observes.
Demand and observed supply
Chart data
| Metric | Value |
|---|---|
| Open demand | 428 |
| Open demand | 428 |
| Observed supply | — not published |
Android forms the largest mobile job flow in CIS thanks to Android dominance in the region (70%+ of devices). Drivers: banking apps, e-commerce, XML → Jetpack Compose migration. Trend 2026: Compose Multiplatform for iOS support.
⚠ candidates matching a vacancy are not counted yet: demand and the observed pool are shown
How salaries in Android / Kotlin jobs are distributed, in US dollars per month.
Salary distribution
Chart data
| Metric | Value |
|---|---|
| <$1k | 2 |
| $1–2k | 1 |
| $2–3k | 2 |
| $3–4k | 2 |
| $4–5k | 4 |
| $5–6k | 5 |
| $6–7k | 6 |
| $7–8k | 1 |
| $8–9k | 3 |
| $9–10k | 3 |
| $10–12k | 2 |
| $12–15k | 2 |
| $15–20k | 5 |
| $20k+ | 0 |
- usable for the calculation: 38 (8.9%)
- stated but not converted to USD/month: 53 (12.4%)
- not stated: 337 (78.7%)
One in ten postings offers under $2,082, one in ten over $15,833. Half of the postings offer between $4,456 and $9,830. Sample: 38.
Chart data
| Metric | Lower bound | Upper bound | Count |
|---|---|---|---|
| <$1k | 0 | 1,000 | 2 |
| $1–2k | 1,000 | 2,000 | 1 |
| $2–3k | 2,000 | 3,000 | 2 |
| $3–4k | 3,000 | 4,000 | 2 |
| $4–5k | 4,000 | 5,000 | 4 |
| $5–6k | 5,000 | 6,000 | 5 |
| $6–7k | 6,000 | 7,000 | 6 |
| $7–8k | 7,000 | 8,000 | 1 |
| $8–9k | 8,000 | 9,000 | 3 |
| $9–10k | 9,000 | 10,000 | 3 |
| $10–12k | 10,000 | 12,000 | 2 |
| $12–15k | 12,000 | 15,000 | 2 |
| $15–20k | 15,000 | 20,000 | 5 |
| $20k+ | 20,000 | — | 0 |
Which countries have the most open Android / Kotlin jobs.
Demand geography
| country | jobs | share |
|---|---|---|
| Poland | 78 | 21.2% |
| United States | 75 | 20.4% |
| India | 26 | 7.1% |
| Russia | 23 | 6.3% |
| United Kingdom | 17 | 4.6% |
| Sweden | 16 | 4.3% |
| Canada | 12 | 3.3% |
| Germany | 10 | 2.7% |
| Spain | 8 | 2.2% |
| Netherlands | 7 | 1.9% |
| Other countries | 96 | 26.1% |
The leader by Android job count is Poland (78 positions). Russia — banking + e-commerce dominate. Poland — large remote market for Russian-speaking Android Senior.
⚠ job counts only: salary by country is not published
Chart data
| Country | Jobs |
|---|---|
| PL | 78 |
| US | 75 |
| IN | 26 |
| RU | 23 |
| GB | 17 |
| SE | 16 |
| CA | 12 |
| DE | 10 |
| ES | 8 |
| NL | 7 |
Which technologies are most often required in the same job as Android / Kotlin.
Used together with
Share — how many of the 428 jobs in the Android / Kotlin market mention this technology. Ordered by job count, not by “strength of association”. Umbrella terms like cloud are not a specific cloud (AWS, Azure).
Top Android stack 2026: Kotlin (must), Jetpack Compose (modern declarative UI — dominator of new projects), XML layouts (legacy in existing codebases), Coroutines + Flow (async), MVI/MVVM/Clean Architecture, Hilt (DI), Room (SQLite ORM), Retrofit + OkHttp (REST), Kotlin Serialization, Coil/Glide, Navigation Component / Compose Navigation, Firebase (Crashlytics + Analytics + Remote Config), JUnit 5 + Mockk + Espresso + Compose Testing.
Common pairs: Kotlin + Compose, Compose + Hilt, Kotlin + Coroutines, Compose + Navigation, Room + Retrofit. Learning roadmap: Kotlin → Android fundamentals → Jetpack Compose → Coroutines + Flow → Hilt + Room → Retrofit + Firebase.
Chart data
| Name | Count |
|---|---|
| kotlin | 304 |
| java | 146 |
| jetpack compose | 141 |
| android | 46 |
| cloud | 40 |
| junit | 30 |
| flutter | 27 |
| c++ | 17 |
| react | 16 |
| dart | 15 |
| javascript | 15 |
| llm | 15 |
How many Android / Kotlin jobs there are at each level, from junior to principal.
Demand by grade
| grade | jobs |
|---|---|
| senior | 186 |
| middle | 34 |
| principal | 19 |
| junior | 17 |
| lead | 6 |
Junior market is moderate (banks + outsourcers hire after courses). Career flow: Junior → Middle → Senior → Tech Lead / Staff Android Engineer / Mobile Architect (cross-platform).
⚠ demand side only: the grade of the observed pool is unknown for most of it
Chart data
| Level | Count |
|---|---|
| senior | 186 |
| middle | 34 |
| principal | 19 |
| junior | 17 |
| lead | 6 |
Who hires the most for Android / Kotlin and how concentrated demand is among the largest companies.
Employers
Demand is spread across 298 employers. The largest accounts for 2.9%, the top ten for 12.2%; the remaining 87.8% is long tail.
| share | value |
|---|---|
| top-1 | 2.9% |
| top-3 | 6.5% |
| top-10 | 12.2% |
| long tail | 87.8% |
⚠ names are not shown: staffing agencies and end employers are not yet told apart by the classifier
Which company sites and job boards Zorky collects Android / Kotlin jobs from.
Where Zorky sees this market
Observed across 61 sources; the largest accounts for 12.4% — this market does not rest on a single channel.
Chart data
| Class | Name | English name | Count | Share |
|---|---|---|---|---|
| ats | ATS и карьерные сайты | ATS & career sites | 239 | 0.5584 |
| board | джоб-борды и агрегаторы | job boards & aggregators | 147 | 0.3435 |
| telegram | Telegram | Telegram | 42 | 0.0981 |
The newest Android / Kotlin jobs from company career sites.
Recent openings
- Android Developer - AI Finance Agent · AT
- Android Developer - AI Finance Agent · INT
- Android Developer in Uzbekistan · UZ · $1,087
- Android Developer
- C++/Android Engineer · US
- [쿠팡이츠] Senior, Android Engineer (Customer Android) · KR
- Senior, Android Engineer ([…] Eats) · KR
- Senior Android Engineer - Kotlin (m|w|d) · DE
Latest open Android jobs — the most recent 10 positions with adequate description quality. The full list is in our CRM or via the "see all" link below.
Adjacent markets
Android — the largest mobile segment in CIS. Salaries ≈ Senior Backend in Moscow; at banks/fintech a premium of 10-15%. Comparison with iOS/Flutter/cross-platform — in the SiblingSubnichesChart above.
⚠ adjacent markets for comparison are not defined yet
How this is measured
- Vacancy
- an open job that cleared the quality gate and lists at least two technologies
- Observed candidate
- a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter
- Matchable candidate
- not counted yet
- Window
- jobs open at the moment the snapshot was built
About the data
- Some breakdowns are hidden: their data coverage is not yet sufficient.
- Statistics are shown only where the sample clears a quality gate.
- A missing block does not mean a value of zero.
Breakdowns currently hidden: 8.
Direction: Mobile
Related specializations
Inside Android: Android Developer (general — Kotlin + Compose + MVVM/MVI), Senior Android Engineer (Compose Multiplatform + modular architecture), Junior Java Android (legacy maintenance — banking apps), Android Tech Lead (SDK/lib architecture + mentoring), Android Game Developer (Unity/Unreal on Android). Comparison with iOS/Flutter/cross-platform — in the bar below.
Frequently asked questions
The most common questions about Android: pay, Kotlin vs Java (learn only Kotlin), Jetpack Compose vs XML layouts, difference from Flutter / React Native, remote, how to start (8-12 months), Senior skills. Answers recompute automatically.
What does an Android Junior, Middle, Senior, or Lead earn?
Junior market is moderate — banks/fintech regularly hire after courses. The Junior → Middle jump — Kotlin coroutines + Compose + Clean Architecture + one DI (Hilt). Senior owns a feature module + mentor. Lead Android — architectural decisions + SDK for other teams. Career flow: Junior → Middle → Senior → either Tech Lead (management), Staff Android Engineer (deep technical), or Mobile Architect (cross-platform — Android + iOS + Compose Multiplatform).
What stack does Android most often need?
Top 5: kotlin, jetpack compose, java, git, agile. Java only in legacy banking. Jetpack Compose — modern declarative UI framework, dominator of new projects 2024–2026, gradually replaces XML layouts. XML layouts — legacy in existing codebases (mandatory for maintenance). Kotlin Coroutines + Flow — must for async. Architecture: MVI (trendy 2024+), MVVM (mainstream), Clean Architecture for large apps. Hilt (DI — Dagger-based, dominator). Room (SQLite ORM). Retrofit + OkHttp for REST API. Kotlin Serialization (modern) or Moshi/Gson. Coil (modern image loading) or Glide. Navigation Component or Compose Navigation. Firebase — Crashlytics + Analytics + Remote Config + Cloud Messaging + Firestore. Testing: JUnit 5 + Mockk + Espresso (UI) + Compose Testing + Roborazzi (screenshot testing). Gradle Kotlin DSL — modern build. Knowledge of Android internals (Activity/Fragment lifecycle, Process death, Doze mode) — Senior must.
Kotlin vs Java — what should beginners learn in 2026?
Kotlin right away — that's the lock in 2026. Java was Android's official language only until 2019 (Google announced Kotlin-first). All new projects are in Kotlin; legacy is in Java existing codebases. Kotlin advantages: null-safety (NullPointerException sharply reduced), data classes, sealed classes for algebraic types, extension functions, named/default arguments, coroutines (cleaner async than RxJava). Junior should learn ONLY Kotlin from the very start. However, Java basics (collections, generics, OOP) are useful for understanding JVM bytecode and legacy maintenance. Strategy: learn Kotlin as primary, pick up Java basics in parallel (if you land in a legacy project — you'll have to read Java).
Jetpack Compose vs XML layouts — what to learn?
Jetpack Compose — modern declarative UI framework (Google, stable since 2021). Reactive approach, less boilerplate than XML, better for complex UI with animations. Dominator of new projects 2024–2026. Gradually replaces XML. XML layouts + View system — legacy approach since 2008 (from the first Android). Mandatory to know for maintenance + integration (Compose can host XML views and vice versa). Strategy: Compose first for new projects (2024+ — the industry is moving there), XML mandatory to understand at the level of "read someone else's code + add a feature to legacy". Junior starts with Compose, but pick up XML basics quickly (1-2 weeks) — to understand existing production apps.
What share of jobs are remote?
Among jobs with a stated work format, 39% are remote. Jobs without a stated format are excluded from the denominator; hybrid work is not counted as remote.
How is Android Native different from Flutter / React Native?
Android Native (this page) — native development in Kotlin/Java for Android only. Advantages: best performance, full access to platform APIs (camera/GPS/Bluetooth/NFC via native SDKs), native UX (Material Design 3). Downsides: codebase duplication for iOS. Flutter (Dart) — cross-platform from Google. One codebase for iOS + Android. Dominator in startups + CIS thanks to development speed. Senior Flutter ≈ Senior Native. React Native (JavaScript) — cross-platform from Meta. Used by international startups. See React (canonical redirect points there). Strategy: Native Android — if you work at a bank/large product company (performance-critical apps); Flutter — if a startup with fast iteration; React Native — if you already know React. Career switch Android Native → Flutter in 2-3 months (Dart is similar to Kotlin/TS).
Where to start in Android in 2026?
Roadmap: 1) Kotlin — official documentation kotlinlang.org + book "Kotlin in Action" Jemerov. Master OOP in Kotlin + null safety + coroutines basics. 2) Java basics (1-2 weeks) — for legacy + JVM understanding. 3) Android Fundamentals — Activity/Fragment lifecycle, Process death, Intent system. Google's Android Developer Codelabs (free). 4) Jetpack Compose — Compose Pathway (Google free tutorial) + Compose Cookbook. Master declarative UI patterns. 5) Coroutines + Flow for async — Kotlin Coroutines official guide. 6) Architecture: MVVM or MVI + Clean Architecture. Book "Android Application Development with Kotlin" Wickham. 7) Hilt (DI) + Room (DB) + Retrofit (REST). 8) Firebase basics. 9) JUnit + Mockk + Compose Testing. 10) Pet project: one full-fledged Android app (TODO/notes/weather with REST API + auth + Firebase Analytics), published on Google Play. Books: "Head First Android Development" Sierra, "Kotlin in Action" Jemerov. Time to Junior — 8-12 months full-time.
How many open jobs are in this sample?
The published sample contains 428 open jobs after merging reposts. This is the same count shown in the main indicator. The geography section describes the sample coverage; this is not an estimate of the entire market.
What skills does a Senior Android need?
A Senior Android owns the full mobile development cycle. Kotlin mastery: coroutines deep (StateFlow/SharedFlow vs LiveData, structured concurrency, dispatchers), generics with variance, sealed classes for state modelling, extension functions, DSL design (like Anko/Compose). Jetpack Compose: deep understanding of Composition phases, smart recomposition (remember/derivedStateOf), CompositionLocal, side-effects (LaunchedEffect/DisposableEffect/produceState), custom layouts via Layout API, animations + transitions, performance (Modifier order matters, stable parameters). Architecture: Clean Architecture mastery (feature modules, use-cases, repository pattern), MVI with unidirectional data flow, navigation strategies (single-activity vs multi-activity). Performance: profiling via Android Profiler (CPU/memory/network), startup time optimisation (Baseline Profiles + Startup Profiles), Compose performance (recomposition counter), memory leaks via LeakCanary. Build: Gradle Kotlin DSL mastery, modularisation strategies (feature modules + buildSrc + convention plugins), R8/ProGuard rules. Testing: risk-based coverage, JUnit5 + Mockk + Truth + Espresso + Compose Testing + Roborazzi (screenshot regression). Test coverage targets depend on system risks and criticality; coverage alone does not guarantee quality. Google Testing. Soft: code review, mentoring, communication with designer (Material Design 3 / iOS UX patterns). English for Senior+ must — for EU relocation and the Toptal network.
Leave a request
Describe the task and leave a contact — the request goes to our CRM and we reply at the contact you provide.