ABOUT BJAK

The original mission of BJAK is we believe people deserve smarter ways to plan, save and grow their money. This is the origin of our name.

Started in 2019, we built the first mobile-first, insurance platform, enabling insurance to be accessible online by millions in the region. Today, its the leading insurance platform in Southeast Asia.

Today, we are expanding ways to help people in the region - this includes spending, saving, investing, exchanging, travelling, and more. Our mission is help people get more from their money every day.

We have teams working around the world, with over 20 nationalities from our offices and remotely, who truly enjoys their work. We are looking for the most talented and driven people we can find. We are looking for people who work for their passion, not counting hours. Who loves building great next-generation products, not status quo. Who cares about redefining how everyone around us can get the best financial applications, not for an exclusive few.

THE ROLE

We are looking for a Lead Engineer to take technical ownership of complex products and systems and raise the engineering bar across the team.

This is a hands-on technical leadership role. You will be expected to design systems, write and review code, solve difficult engineering problems, guide other engineers and drive major initiatives from idea to production.

You should be comfortable moving between architecture and implementation - making strong technical decisions while still being close enough to the code to execute when needed.

WHAT YOU'LL OWN

  • Lead the technical design and execution of major products, features and engineering initiatives.
  • Design scalable, reliable and maintainable systems across backend, frontend, APIs, databases and infrastructure.
  • Stay hands-on with engineering through coding, prototyping, code reviews, debugging and production problem-solving.
  • Make architecture decisions and technical trade-offs that balance speed, scalability, reliability and maintainability.
  • Break ambiguous product and technical problems into clear engineering solutions and execution plans.
  • Set a high bar for code quality, system design, testing, security, observability and production reliability.
  • Review technical designs and code from other engineers and provide clear, actionable feedback.
  • Mentor engineers and help strengthen technical capability across the team.
  • Identify technical risks, bottlenecks and architectural weaknesses before they become larger problems.
  • Work closely with engineering, product, design and AI teams to ship high-quality products quickly.
  • Improve engineering tooling, development practices and automation to increase team velocity.
  • Own systems beyond release - monitor production, investigate incidents, resolve root causes and continuously improve reliability.


WHAT WE'RE LOOKING FOR

  • Strong software engineering background with significant experience building and shipping production systems.
  • Deep technical expertise in one or more areas such as backend, frontend, distributed systems, APIs, databases or cloud infrastructure.
  • Strong system design and architecture skills with experience making technical decisions for complex or high-scale systems.
  • Strong coding ability and willingness to remain hands-on.
  • Proven experience leading major engineering projects or providing technical leadership to other engineers.
  • Comfortable reviewing code, debugging complex issues and working directly with production systems.
  • Able to explain complex technical decisions clearly and influence engineers across teams.
  • Strong product sense and ability to connect technical decisions to customer and business outcomes.
  • Able to work fast with ambiguity and take ownership from problem definition through production.
  • Strong judgment around when to move quickly, when to simplify and when deeper engineering investment is required.


THIS ROLE IS NOT FOR

  • Engineers who want a leadership title but no longer want to write or review code.
  • People who only want to work within one narrow technical area.
  • Engineers who wait for complete specifications before starting.
  • Candidates who over-engineer solutions when a simpler approach would achieve the outcome.
  • Engineers who focus only on implementation without understanding the product or business problem.
  • People who avoid production incidents, difficult debugging or ownership after release.
  • Candidates who make vague claims about technical leadership without being able to explain what they personally designed, built, shipped or scaled.


THE BAR

We are looking for technical leaders with real engineering career highlights.

A strong highlight is not simply having a senior title or working at a famous technology company. A strong highlight means you personally designed, built, shipped or scaled a serious product, platform or system and can go deep into the technical decisions behind it.

You should be able to demonstrate both technical depth and technical leadership - someone who can solve difficult engineering problems personally while making the engineers around them stronger.

LOCATION

This is a remote role. We hire globally and work across multiple countries and time zones.

Candidates should be comfortable working effectively in a distributed, fast-moving international team and collaborating with colleagues across different locations.

LANGUAGE

English is our main working language across global teams. Strong English communication is required.

INTERVIEW PROCESS

Our process is designed to move fast:

  • Online assessment or practical task
  • Technical interview
  • CEO / final round

For strong candidates, we aim to complete the process and make an offer within 1 week from the start of the interview process. Candidates who complete assessments quickly will be prioritized.

āļ—āļąāļāļĐāļ°āļ—āļĩāđˆāļˆāļģāđ€āļ›āđ‡āļ™
  • Cloud Computing
  • Architecture
  • Leadership Skill
āļ›āļĢāļ°āļŠāļšāļāļēāļĢāļ“āđŒāļ—āļĩāđˆāļˆāļģāđ€āļ›āđ‡āļ™
  • āđ„āļĄāđˆāļĢāļ°āļšāļļāļ›āļĢāļ°āļŠāļšāļāļēāļĢāļ“āđŒāļ‚āļąāđ‰āļ™āļ•āđˆāļģ
āļĢāļ°āļ”āļąāļšāļ•āļģāđāļŦāļ™āđˆāļ‡āļ‡āļēāļ™
  • āļĢāļ°āļ”āļąāļšāļœāļđāđ‰āļˆāļąāļ”āļāļēāļĢ / āļ­āļēāļ§āļļāđ‚āļŠ
āđ€āļ‡āļīāļ™āđ€āļ”āļ·āļ­āļ™
  • āļŠāļēāļĄāļēāļĢāļ–āļ•āđˆāļ­āļĢāļ­āļ‡āđ„āļ”āđ‰
āļŠāļēāļĒāļ‡āļēāļ™
  • āļ§āļīāļĻāļ§āļāļĢāļĢāļĄ
  • āļāļēāļĢāļˆāļąāļ”āļāļēāļĢ
āļ›āļĢāļ°āđ€āļ āļ—āļ‡āļēāļ™
  • āļ‡āļēāļ™āļ›āļĢāļ°āļˆāļģ

āđ€āļāļĩāđˆāļĒāļ§āļāļąāļšāļšāļĢāļīāļĐāļąāļ—

āļˆāļģāļ™āļ§āļ™āļžāļ™āļąāļāļ‡āļēāļ™:100-500 āļ„āļ™
āļ›āļĢāļ°āđ€āļ āļ—āļšāļĢāļīāļĐāļąāļ—:āļ›āļĢāļ°āļāļąāļ™āļ āļąāļĒ / āļŠāļĩāļ§āļīāļ•
āļ—āļĩāđˆāļ•āļąāđ‰āļ‡āļšāļĢāļīāļĐāļąāļ—:n/a
āđ€āļ§āđ‡āļšāđ„āļ‹āļ•āđŒ:bjak.my
āļāđˆāļ­āļ•āļąāđ‰āļ‡āđ€āļĄāļ·āđˆāļ­āļ›āļĩ:2019

BJAK āđāļžāļĨāļ•āļŸāļ­āļĢāđŒāļĄāļ›āļĢāļ°āļāļąāļ™āļ­āļ­āļ™āđ„āļĨāļ™āđŒāļŠāļąāđ‰āļ™āļ™āļģāđƒāļ™āđ€āļ­āđ€āļŠāļĩāļĒāļ•āļ°āļ§āļąāļ™āļ­āļ­āļāđ€āļ‰āļĩāļĒāļ‡āđƒāļ•āđ‰ āļŠāļģāļ™āļąāļāļ‡āļēāļ™āđƒāļŦāļāđˆāļĄāļēāđ€āļĨāđ€āļ‹āļĩāļĒ āļ‚āļĒāļēāļĒāđ„āļ› āđ„āļ—āļĒ āļāļĩāđˆāļ›āļļāđˆāļ™ āđ„āļ•āđ‰āļŦāļ§āļąāļ™

āļāđˆāļ­āļ•āļąāđ‰āļ‡ 2019 āđ€āļ›āļĢāļĩāļĒāļšāđ€āļ—āļĩāļĒāļš/āļ‹āļ·āđ‰āļ­/āļ•āđˆāļ­āļ­āļēāļĒāļļāļ›āļĢāļ°āļāļąāļ™āļĒāļēāļ™āļĒāļ™āļ•āđŒāļ­āļ­āļ™āđ„āļĨāļ™āđŒ āļ­āļ™āļļāļĄāļąāļ•āļī BNM āļœāļđāđ‰āđƒāļŠāđ‰āļāļ§āđˆāļē 6 āļĨāđ‰āļēāļ™

āļĢāđˆāļ§āļĄāļ‡āļēāļ™āļāļąāļšāđ€āļĢāļē:

Join a high-growth insurtech used by millions across Asia.

  • 6M+ users
  • Digital product culture (20+ nationalities)
  • Real insurance/fintech problems
  • Hybrid office

āļ•āļģāđāļŦāļ™āđˆāļ‡āļ‡āļēāļ™āļ§āđˆāļēāļ‡āļ—āļĩāđˆāļ„āļļāļ“āļ™āđˆāļēāļˆāļ°āļŠāļ™āđƒāļˆ

āļ”āļđāļ‡āļēāļ™āļ—āļąāđ‰āļ‡āļŦāļĄāļ” >

āļ—āļĩāđˆ WorkVenture āđ€āļĢāļēāđƒāļŦāđ‰āļĄāļđāļĨāđ€āļŠāļīāļ‡āđ€āļāļĩāđˆāļĒāļ§āļāļąāļšāļšāļĢāļīāļĐāļąāļ— āļšāļĢāļīāļĐāļąāļ— āļšāļĩ āļˆāļąāļ (āļ›āļĢāļ°āđ€āļ—āļĻāđ„āļ—āļĒ) āļˆāļģāļāļąāļ” āđ‚āļ”āļĒāļĄāļĩāļ‚āđ‰āļ­āļĄāļđāļĨāļ—āļĩāđˆāđ€āļāļĩāđˆāļĒāļ§āļ‚āđ‰āļ­āļ‡ āļ•āļąāđ‰āļ‡āđāļ•āđˆāļ āļēāļžāļšāļĢāļĢāļĒāļēāļāļēāļĻāļāļēāļĢāļ—āļģāļ‡āļēāļ™ āļĢāļđāļ›āļ–āđˆāļēāļĒāļ‚āļ­āļ‡āļ—āļĩāļĄāļ‡āļēāļ™ āđ„āļ›āļˆāļ™āļ–āļķāļ‡āļĢāļĩāļ§āļīāļ§āđ€āļŠāļīāļ‡āļĨāļķāļāļ‚āļ­āļ‡āļāļēāļĢāļ—āļģāļ‡āļēāļ™āļ—āļĩāđˆāļ™āļąāđˆāļ™ āļ‹āļķāđˆāļ‡āļ‚āđ‰āļ­āļĄāļđāļĨāļ—āļļāļāļ­āļĒāđˆāļēāļ‡āļšāļ™āļŦāļ™āđ‰āļēāļ‚āļ­āļ‡āļšāļĢāļīāļĐāļąāļ— āļšāļĢāļīāļĐāļąāļ— āļšāļĩ āļˆāļąāļ (āļ›āļĢāļ°āđ€āļ—āļĻāđ„āļ—āļĒ) āļˆāļģāļāļąāļ” āļĄāļĩāļžāļ™āļąāļāļ‡āļēāļ™āļ—āļĩāđˆāļāļģāļĨāļąāļ‡āļ—āļģāļ‡āļēāļ™āļ—āļĩāđˆāļšāļĢāļīāļĐāļąāļ— āļšāļĢāļīāļĐāļąāļ— āļšāļĩ āļˆāļąāļ (āļ›āļĢāļ°āđ€āļ—āļĻāđ„āļ—āļĒ) āļˆāļģāļāļąāļ” āļŦāļĢāļ·āļ­āđ€āļ„āļĒāļ—āļģāļ‡āļēāļ™āļ—āļĩāđˆāļ™āļąāđˆāļ™āļˆāļĢāļīāļ‡āđ† āđ€āļ›āđ‡āļ™āļ„āļ™āđƒāļŦāđ‰āļ‚āđ‰āļ­āļĄāļđāļĨāļˆāļĢāļīāļ‡āļŠāļĄāļąāļ„āļĢāļ‡āļēāļ™ āđ€āļˆāļĄāļēāļĢāđŒāļ—āļŠāļĄāļąāļ„āļĢāļ‡āļēāļ™ āđ€āļ­āđ‡āļāļ‹āđŒāđ€āļ‹āļĨāđ€āļĨāļ™āļ‹āđŒāļŠāļĄāļąāļ„āļĢāļ‡āļēāļ™ āļšāļĢāļīāļĐāļąāļ— āđ€āļ™āļĨ āđ€āļĨāļ­ āđ‚āļš āļˆāļģāļāļąāļ”āļŠāļĄāļąāļ„āļĢāļ‡āļēāļ™ āļšāļĢāļīāļĐāļąāļ— āđ€āļ§āļīāļĢāđŒāļ„āđ€āļ§āļ™āđ€āļˆāļ­āļĢāđŒ āđ€āļ—āļ„āđ‚āļ™āđ‚āļĨāļˆāļĩāļŠāđŒ āļˆāļģāļāļąāļ”