Senior Mobile Engineer iOS, Android

1. 5+ years building mobile applications, with at least one production app owned through multiple release cycles. The role requires setting architectural standards, debugging production incidents, coaching engineers, and supporting hiring - depth below this bar will not carry it.
2. Strong native proficiency in one platform:
- Android: Kotlin - Compose, Coroutines
- iOS: Swift - SwiftUI, Structured Concurrency
3. Practical experience with MVVM or equivalent, asynchronous programming, and REST API integration.
4. Familiarity with regulated-environment features: secure storage, biometric authentication, certificate pinning, root/jailbreak detection, obfuscation, and data residency requirements.
5. Unit and UI testing as a working habit, not an afterthought. Familiarity with app store submission and review for financial applications.
6. Git and collaborative branching workflows; comfortable working within a CI/CD pipeline.
7. Track record of mentoring less-experienced engineers and giving constructive code review.
8. Working English. Chinese is a plus for cross-region collaboration.
9. Degree in Computer Science or equivalent practical experience.
Nice to Have
- Practical Clean Architecture experience.
- Production on-call or incident response experience (significant plus).
- Scrum experience.
- Cross-platform exposure (Flutter / React Native).
- Performance profiling depth.
- Prior fintech or banking delivery.
How We Work - Read This Before Applying
Our engineers work inside a defined AI-assisted development framework rather than ad hoc AI usage. Tickets move through defined phases with human approval gates, Jira holds the state, and AI contribution is measured per project and reviewed.
We expect you to already be applying AI tools in your current workflow, with judgement about where they fail and clear awareness of the security and data-privacy limits on their use in a regulated environment. Experience with Claude Code or Codex specifically is a plus, not a requirement - the tooling is learnable, the judgement is not.
You will have a direct hand in shaping how this framework applies to mobile. This suits engineers who want to define how AI changes mobile delivery rather than consume tooling someone else built. It does not suit engineers who treat AI tooling as optional.