About This Role

10 to 15 years of experience

Skills: iOS and Android Development, Solution Architect, Swift, Kotlin

About the work A large consumer-facing mobile product is being rebuilt from the ground up as two fully native applications. The existing app was built on a cross-platform framework; the new iOS and Android apps will be independent native codebases. This role owns the technical shape of both.

The role You are the single technical owner across both platforms. You set the architecture, the module boundaries, the API contract, the testing strategy and the release process, and you write production code on both platforms while doing it. This is not a design-and-hand-off role — roughly half your time is in the codebase.

You will be the person the platform leads escalate to, the person who decides when the two apps should converge on a pattern and when platform idiom should win, and the person accountable for the two codebases not drifting apart over the life of the program.

What you will own

- End-to-end architecture for both native applications: layering, modularization, dependency and navigation strategy, state management
- The client-facing API contract — an OpenAPI specification treated as the source of truth, with generated Swift and Kotlin client SDKs — and the working relationship with the backend team that keeps it honest
- Authentication and session architecture, secure credential storage, and token lifecycle across both platforms
- Offline behavior and data synchronization strategy, including how conflicts are resolved and how it is implemented consistently on both sides
- CI/CD, signing, release trains, staged rollout, feature flagging and kill-switch capability
- Migration and coexistence strategy while the outgoing app remains live in both stores
- Technical standards, code review culture,



and the definition of done that the platform teams work to

Required

- 10+ years building mobile applications, with production ownership on both iOS and Android — genuine depth on each, not familiarity with one and a passing knowledge of the other
- Current Swift: Swift 6 language mode, strict concurrency, actors, Sendable and @MainActor isolation; SwiftUI with the Observation framework; Swift Package Manager modularization
- Current Kotlin: Kotlin 2.x with the K2 compiler, Jetpack Compose, Navigation 3, coroutines and Flow, Hilt, multi-module Gradle with Kotlin DSL and version catalogs
- Demonstrated architecture ownership on an application of meaningful scale — you can walk through a system you designed, the trade-offs you made, and what you would do differently
- Contract-first API design experience: OpenAPI or equivalent, client code generation, versioning and deprecation strategy for clients you cannot force-update
- REST integration against Node.js backend services; comfort reasoning about document-oriented data models and their implications for mobile payload design
- Practical command of CI/CD for mobile, including code signing, provisioning, and automated store submission on both platforms
- Hands-on: you will be expected to write and review production code on both platforms every week

Preferred

- You have migrated an application off a cross-platform framework to native before, and can speak concretely about what went wrong
- Experience defining a backend-for-frontend layer for mobile clients
- Custom offline sync implementation experience (not solely a managed sync product)
- Mobile security depth: certificate pinning, App Attest and Play Integrity, biometric authentication, secure logging practices in a regulated setting
- Performance work: startup time, memory, Baseline Profiles, Instruments and Android profiling tooling

📌 Mobile Architect (Chennai)
🏢 Bounteous
📍 Chennai