Bjak
Mobile Application Developer
United States (Remote)fulltimemidAdded today
About this role
BJAK seeks a mobile developer to build features for its AI-powered neobank app across Android and iOS platforms. You'll own end-to-end mobile experiences for financial services like payments, transfers, and onboarding, collaborating with cross-functional teams to ship reliable, user-focused products.
What you'll do
- Develop mobile features across Android, iOS, or cross-platform depending on expertise
- Own full product-to-launch journey for onboarding, payments, cards, transfers, and AI-assisted features
- Collaborate with backend, design, product, and AI teams on customer-facing features
- Debug production issues and improve app quality using analytics and crash reports
- Raise mobile standards for UX, reliability, and performance across the platform
- Work independently with strong ownership in a startup environment
What they're looking for
- Android development
- iOS development
- Mobile app architecture and design patterns
- API integration and debugging
- Production app deployment and release management
- Mobile performance optimization
- UX/product sense
- Cross-functional collaboration
Benefits
- Remote work (US-based)
- Work on fintech product serving Southeast Asia
- Ownership of shipped, user-facing features
- Fast-moving startup environment
- Global team with 20+ nationalities
- Passionate mission-driven culture
Opens the official application on the employer’s site. No login required.
Bjak
Bjak is a Southeast Asian fintech super app offering insurance, payments, savings, wallets, and investment products through a unified platform. The company is hiring full stack engineers, backend engineers, iOS developers, and Android engineers to build scalable features and reliable systems across mobile and web products.
- Website
- bjak.com
Likely interview questions
- Walk us through a mobile app you shipped to production—what was your specific contribution and how did you measure its success?
- Describe a time you discovered a production bug affecting users. How did you debug it and prevent recurrence?