Android Software Engineer

The Role

We are looking for Android software engineers to build the native Android experience for BJAK's AI Finance Agent.

This role is for someone who cares about clean user flows, fast performance, product quality and shipping reliable mobile features used by real customers.

What You'll Own

• Build and ship Android features using Kotlin .
• Create clean mobile flows for insurance, payments, claims, renewals and financial services.
• Work with product and design to simplify complex user journeys.
• Integrate backend APIs and ensure mobile flows are stable, secure and reliable.
• Improve app performance, crash rate, loading states, responsiveness and memory usage.
• Use analytics, user behaviour and production issues to improve the product.
• Build AI-assisted mobile experiences only where they genuinely improve the user journey.

What We're Looking For

• 3+ years of Android development experience using Kotlin .
• Strong Android fundamentals and experience shipping production apps.
• Good knowledge of Jetpack , Coroutines , Flow and modern Android architecture.
• Strong sense of mobile UX, usability, edge cases and user flows.
• Experience integrating REST APIs and debugging production issues.
• Fast execution, high ownership and strong attention to product quality.
• App links, GitHub, screenshots or examples of shipped work are a strong advantage.

Tech Stack

• Kotlin
• Jetpack Compose
• Android SDK
• Coroutines & Flow
• SQL / NoSQL
• TensorFlow Lite (on-device inference)

The Kind of Builder We Want

• Thinks in user journeys, not just screens.
• Cares about making complex financial products feel simple.
• Moves fast without creating messy code.
• Notices UX, performance and reliability issues before users complain.
• Honest about what they personally built, what was team-owned and what impact they can or cannot claim.

This Role Is Not For

• Engineers who only want fully defined tickets.
• Developers who build screens without caring about user experience.
• People who ignore crashes, edge cases, loading states or performance.
• Engineers who move slowly in a startup environment.
• People who exaggerate impact without explaining their actual contribution.