Bjak
Product Engineer - AI Finance
About this role
BJAK seeks a Product Engineer to own financial product areas within its AI Finance division, spanning insurance, payments, savings, and investing. You'll define product strategy, collaborate with engineering and design teams, and drive fast launches while balancing user experience, compliance, and business impact.
What you'll do
- Own product areas across insurance, payments, savings, investing, travel and other financial services
- Define user problems, product scope, success metrics, roadmap and launch plans
- Collaborate with engineering, design, data, operations, compliance and business teams
- Convert complex financial workflows into simple, intuitive customer experiences
- Launch features, monitor performance metrics and drive post-launch iterations
- Make trade-offs between speed, UX, business impact, compliance and operational complexity
What they're looking for
- Product management or product ownership experience
- Product sense and ability to simplify complex workflows
- Data analysis and experimentation mindset
- Cross-functional collaboration and stakeholder management
- Strong written communication and prioritization
- Fintech, insurance, payments or consumer app expertise
- Shipping products with limited information
- Post-launch learning and iteration
Opens the application — the Jobs AI extension fills it for you. Set up autofill
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 complex financial product you've shipped—how did you simplify it for users and what metrics proved success?
- Describe a time you made a decision with incomplete data. How did you validate it post-launch?