Bjak
Full Stack Engineer
About this role
BJAK seeks a full stack engineer to build features across their AI Neobank app, handling everything from frontend to backend and databases. You'll own complete product features—from onboarding and payments to KYC and support automation—working closely with product and design teams in a fast-moving fintech environment.
What you'll do
- Build and ship complete product features spanning frontend, backend, APIs, and databases
- Develop customer workflows for onboarding, accounts, payments, rewards, travel, FX, and KYC
- Transform ambiguous product requirements into reliable systems with clean UX and solid backend logic
- Create internal tools and automation to reduce manual work and scale team operations
- Collaborate with product, design, mobile, backend, and AI engineers to launch quickly and iterate
- Own post-launch monitoring, debugging, and continuous improvement of deployed features
What they're looking for
- Full stack development with shipped products
- Frontend: React, Next.js, Vue, or equivalent modern frameworks
- Backend: APIs, data modeling, authentication, integrations
- Database design and optimization
- Production debugging and operations support
- Product sense and ability to simplify workflows
- Working with ambiguity and owning outcomes end-to-end
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 shipped product feature you built end-to-end—what was your contribution across frontend, backend, and infrastructure?
- Describe a time you had to turn an ambiguous product requirement into a working system. How did you approach it?