Android / IOS Application Developer

We’re building something significant — and we need the right engineer to help us get there.📋 Role OverviewAs an Android Engineer, you will design, build, and maintain high-quality features for our consumer-facing Android application. You’ll collaborate closely with product, design, and backend engineers to deliver experiences that are fast, reliable, and delightful to use.⚡Key ResponsibilitiesBuild and maintain robust Android features using Kotlin and Jetpack Compose.Design clean, scalable UI with both Compose and XML layouts depending on context.Architect features following MVVM principles, ensuring separation of concerns and testability.Collaborate with product and design teams to translate specs into polished user experiences.Write unit and UI tests; participate in code reviews to maintain quality standards.Monitor production performance, debug issues, and ship timely fixes.Contribute to architectural decisions and help establish best practices on the team.✅ Required Skills & Qualifications1–2+ years of professional Android development experience.Hands-on experience in high-paced, high-growth production Android applications.Proficient in Kotlin— idiomatic, clean, and confident.Strong command of Jetpack Compose for building modern declarative UIs.Solid XML layout skills— comfortable working across legacy and modern UI systems.Deep familiarity with MVVM architecture and Android Architecture Components (ViewModel,LiveData/StateFlow).Working knowledge of REST APIs, JSON parsing, and async patterns (Coroutines / Flow).Experience with Git and standard collaborative workflows (PRs, code review).✨ Good-to-Have Skills0–1 experience: built an Android app or key feature from scratch.Familiarity with CI/CD pipelines (GitHub Actions, Bitrise, or similar).Experience with analytics SDKs, crash reporting (Firebase, Sentry), or A/B testing tools.Published apps on the Google Play Store.AI Usage Policy: We encourage AI tools (Cursor, Copilot, GPT-4) as force multipliers — but you must own your code, explain trade-offs, and debug without solely relying on AI