Skip to main content

Bjak

iOS Developer

United States (Remote)fulltimemidAdded today

About this role

BJAK seeks an iOS engineer to build native features for their AI-powered neobank app serving Southeast Asia. You'll develop onboarding, payments, transfers, and AI-assisted experiences while prioritizing performance, reliability, and user-centric design in a fast-moving fintech startup.

What you'll do

  • Build and ship native iOS features for onboarding, accounts, cards, payments, transfers, and rewards
  • Simplify complex financial workflows into clean, fast mobile experiences
  • Collaborate with product, design, backend, and AI teams from concept to production
  • Own app quality including performance, crashes, edge cases, and release stability
  • Debug production issues and use analytics to improve features post-launch
  • Integrate APIs, authentication, secure data handling, and financial workflows reliably

What they're looking for

  • Swift (strong native iOS experience)
  • SwiftUI and UIKit
  • Async/await and concurrency patterns
  • iOS architecture patterns and design
  • Performance debugging and optimization
  • API integration and secure data handling
  • Product sense and UX awareness
  • Shipping production apps at scale

Benefits

  • Remote work (US-based)
  • Global team with 20+ nationalities
  • Fast-moving fintech startup environment
  • Focus on meaningful financial products for millions
  • Rapid interview process (1 week target for strong candidates)
Apply on the employer's site

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
View all jobs at Bjak

Likely interview questions

  • Describe a production iOS app you shipped. What was your specific contribution and how did users benefit?
  • How do you approach debugging a crash or performance issue reported by users in production?