Technical Product Lead - AI Finance

We need to output HTML fragment with sections: About the role? Actually the posting includes "About BJAK" (company description) then "The Role", "What You'll Own", "What We're Looking For", "Outcome", "Location", "Language", "Interview Process". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. The headings we can use are limited to those listed. We need to map content to those headings appropriately. We have: - About BJAK: company description. Could map to "About the role"? Actually "About the role" is for role description. But we have "About BJAK" which is company overview. Could we use "About the role"? Not exactly. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should use those headings when appropriate. Probably we should use those exact headings if we have content. If we don't have content for a heading, we omit it. We have content about role: "The Role BJAK is building a AI Finance Superapp..." That's role description. Could fit under "About the role". Also "What You'll Own" could be Responsibilities. "What We're Looking For" could be Requirements/Qualifications/Skills. "Outcome" maybe could be something like "Outcomes" but not in list; maybe we could treat as "Responsibilities"? But we already have responsibilities. Could we add a custom heading? The instruction says use those headings; but maybe we can also use other headings if needed? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can create sections with appropriate headings that match content. Probably safe to use headings like "About the role", "Responsibilities", "Requirements", "Qualifications", "Skills", "Benefits", "Pay", "Schedule". We need to map content. We have no explicit Benefits, Pay, Schedule info. So we omit those sections. We have Location and Language and Interview Process. Those are not in the list but we could still include them as headings? The instruction says use those headings for section headings (e.g...). It might be okay to add other headings if needed, but safer to stick to given list. However we need to preserve ALL substantive information; we cannot drop Location, Language, Interview Process. So we need to include them somehow. Perhaps we can incorporate them under existing headings: Location could go under "About the role" or as a separate section with a heading like "Location". The instruction didn't forbid other headings, just gave examples. So we can add headings for Location, Language, Interview Process. Thus produce HTML with sections:

About the role

... (company description + role overview)

Responsibilities

• ... from What You'll Own

Requirements

• ... from What We're Looking For (core)

Qualifications

maybe split nice-to-have? Could put nice-to-have under Qualifications or Skills. We have "Nice to have Engineering or highly technical product background. Experience building zero-to-one fintech or consumer products. Experience defining evaluation frameworks for ML or LLM-powered products." Could be Qualifications.

Skills

maybe technical foundation etc. But we already covered technical foundation in Requirements. Might be redundant. Better to have Requirements (core) and Qualifications (nice-to-have). Skills maybe not needed. We also have Outcome section: "Outcome Clear vertical strategy and legible roadmap..." Could be placed under Responsibilities or as its own section "Outcome". Not in list but we can add. Location, Language, Interview Process sections. We must not include boilerplate like EEO etc. Not present. Let's extract content precisely. About BJAK paragraph: "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. If you're this person, we'd love to talk to you." We need to preserve all substantive info. We'll put that in a

. The Role paragraph: "The Role BJAK is building a AI Finance Superapp for Southeast Asia across payments, remittance, insurance, wealth, and trading. These products move real money. Reliability, regulatory requirements, and third-party financial rails are fundamental to the product - not considerations around the edges. The Technical Product Lead owns a product vertical end-to-end, from strategy and outcomes through technical design, delivery, and launch. We are AI-native by default, but AI is a means, not the goal. The bar is knowing where AI genuinely improves an outcome, where deterministic systems must remain in control, and how to build products that are reliable, auditable, and trusted." We'll include that in About the role section maybe after company description. What You'll Own bullet points (actually sentences): "Owning a product vertical end-to-end, including strategy, metrics, roadmap, priorities and delivery. Shaping technical design with engineering across APIs, data flows, ledgering, reconciliation, failure handling, security and scalability. Driving trade-offs across correctness, speed, cost, reliability, regulatory requirements and user experience. Building regulatory requirements into the product across KYC, transaction monitoring, limits, privacy and licensing. Applying AI where it improves outcomes, with clear evaluation, safeguards, human oversight and failure handling. Shipping products around external dependencies, including regulatory approvals, financial rails and third-party partners. Aligning Engineering, Design, Compliance, Operations, Treasury and Finance around clear product decisions and launch requirements." We'll make each a

. What We're Looking For bullet points: "5+ years of product management experience, including ownership of complex technical products from strategy through production. Strong technical foundation across system architecture, APIs, databases, workflows, failure modes and distributed systems. Experience working closely with engineers and ability to review, challenge and contribute to technical designs. Experience in payments, banking, remittance, insurance, trading or another regulated, high-consequence product domain. Strong product judgment and ability to make difficult trade-offs under technical, regulatory and operational constraints. Experience building with LLMs or AI products, including evaluation, reliability and understanding when AI should not be used." Nice to have: "Nice to have Engineering or highly technical product background. Experience building zero-to-one fintech or consumer products. Experience defining evaluation frameworks for ML or LLM-powered products." Outcome bullet points: "Outcome Clear vertical strategy and legible roadmap Ships fast and clears the gates that actually block launch Money is correct and users are never misled about the state of their funds AI features are valuable, predictable and trusted Trade-offs made deliberately under uncertainty and hold up when challenged Engineering, design, compliance, and operations are aligned with minimal friction" Location: "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: "Language English is our main working language across global teams. Strong English communication is required." Interview Process: "Interview Process Our process is designed to move fast: Online assessment or practical taskTechnical interviewCEO / 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." Note there is a missing space after "task". We'll keep as is. Now construct HTML. We'll have:

About the role

About BJAK ... The Role ...

But we have two paragraphs: About BJAK and The Role. Could combine into one

with both. Ensure we keep all info. Let's craft:

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. If you're this person, we'd love to talk to you. The Role BJAK is building a AI Finance Superapp for Southeast Asia across payments, remittance, insurance, wealth, and trading. These products move real money. Reliability, regulatory requirements, and third-party financial rails are fundamental to the product - not considerations around the edges. The Technical Product Lead owns a product vertical end-to-end, from strategy and outcomes through technical design, delivery, and launch. We are AI-native by default, but AI is a means, not the goal. The bar is knowing where AI genuinely improves an outcome, where deterministic systems must remain in control, and how to build products that are reliable, auditable, and trusted.

Then Responsibilities:

Responsibilities

• Owning a product vertical end-to-end, including strategy, metrics, roadmap, priorities and delivery.
• Shaping technical design with engineering across APIs, data flows, ledgering, reconciliation, failure handling, security and scalability.
• Driving trade-offs across correctness, speed, cost, reliability, regulatory requirements and user experience.
• Building regulatory requirements into the product across KYC, transaction monitoring, limits, privacy and licensing.
• Applying AI where it improves outcomes, with clear evaluation, safeguards, human oversight and failure handling.
• Shipping products around external dependencies, including regulatory approvals, financial rails and third-party partners.
• Aligning Engineering, Design, Compliance, Operations, Treasury and Finance around clear product decisions and launch requirements.

Requirements (core):

Requirements

• 5+ years of product management experience, including ownership of complex technical products from strategy through production.
• Strong technical foundation across system architecture, APIs, databases, workflows, failure modes