Skip to main content
📱

Mobile Developer Interview Prep — iOS, Android, React Native, Flutter — for engineers in Tashkent

Mobile interviews in Tashkent split between native (Swift/Kotlin), cross-platform (React Native/Flutter), and the rare 'we ship to App Store with one engineer' role. Practice the questions each track actually asks, with real-time AI scoring on communication, technical depth, problem-solving, and cultural fit.

The mobile market in Tashkent is smaller than frontend or backend, but the candidates who clear the interview bar are scarce — and well-paid for it. Local fintechs, ride sharing, and delivery apps hire actively. Outsourcing studios serving the EU and Gulf region pay a noticeable premium for engineers who can ship on both platforms.

The questions below are pulled from real Tashkent interviews and apply across native and cross-platform stacks. Practice them out loud in the language your real interview will be in.

Core skills tested

  • One platform deeply: Swift + UIKit/SwiftUI, or Kotlin + Jetpack Compose
  • Cross-platform option: React Native or Flutter at production level
  • Memory and lifecycle: ARC, retain cycles, Activity / ViewController lifecycles
  • Networking: URLSession / Retrofit / fetch, plus offline strategy
  • Local storage: Core Data, Room, SQLite, MMKV
  • Push notifications + deep linking
  • App Store / Play Store release process and rejection patterns
  • Performance: cold start, frame drops, memory leaks

Salary ranges in Tashkent (2026)

Approximate. Remote-first European roles typically pay 30–50% above local rates.

Junior

8–12M UZS / month

Mid-level

16–26M UZS / month

Senior

32M+ UZS / month (or EUR remote)

What you will actually be asked

Pulled from real interviews recorded on NextSuhbat. Each item is a question you should expect, plus what the interviewer is really testing.

  1. 1

    Recruiter screen

    Walk me through an app you have shipped to a public store.

    Why it is asked: Tests scope and follow-through. Include the rejection you got and how you fixed it.

  2. 2

    Technical

    Explain the difference between strong, weak, and unowned references in Swift (or the equivalent in Kotlin).

    Why it is asked: Memory management is the most common bar at any senior mobile interview.

  3. 3

    Technical

    Walk me through what happens when an iOS / Android app gets backgrounded and then foregrounded.

    Why it is asked: Tests lifecycle understanding. Be specific about state restoration and what should and should not survive.

  4. 4

    Technical

    How would you debug a frame-rate drop in a list?

    Why it is asked: Practical question. Cover Instruments / Profiler, recycler view binding, image decode, layout passes.

  5. 5

    Technical

    Explain the React Native bridge (or Flutter platform channels) and one performance pitfall.

    Why it is asked: Asked at any company using cross-platform. Bonus for Hermes / new architecture / Skia internals.

  6. 6

    Coding

    Build an infinite-scroll feed with image lazy-loading and pull-to-refresh.

    Why it is asked: Tests cell reuse, concurrent image loading, and clean state management.

  7. 7

    Coding

    Implement a debounced search bar that hits an API and cancels stale requests.

    Why it is asked: Same problem on every platform. Tests cancellation primitives (Combine, coroutines, RxJS).

  8. 8

    System design

    Design the offline-first architecture for a messaging app.

    Why it is asked: Local DB, sync conflict resolution, queueing, retry strategy. Cover the bad-network case explicitly.

  9. 9

    Behavioral

    Tell me about a time a release was held up by App Store / Play Store review.

    Why it is asked: Wrong answer: never happened. Right: what got flagged, how you appealed or rebuilt.

  10. 10

    Behavioral

    Why mobile and not web?

    Why it is asked: Have a real reason — touch interactions, offline, hardware integration. Avoid sounding like you fell into it.

Practice these questions out loud — for free

Reading is not practice. Run a 20-minute AI mock interview in English, Russian, or Uzbek and get a scorecard against communication, technical depth, problem-solving, and cultural fit.

Start free mock interview

Built in Tashkent for Central Asia. All practice sessions support English, Russian, and Uzbek voice.

Related reading