Product Engineer - AI Stockbroking
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting.
Content:
- About BJAK: description of company mission, history, etc. Could be "About the company" maybe but we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have sections: "About BJAK" (company overview). Could map to "About the role"? Actually "About the role" is more about the role description. But we have "The Role" and "What You'll Own". Could treat as "Responsibilities". Also "What We're Looking For" as "Requirements" or "Qualifications". "The Kind of Builder We Want" maybe "Skills". Also "Location", "Language", "Interview Process". Those might be extra but we only include sections if they have real specific content. We could include "Location" as maybe not in list but we can still include if needed? The instruction says use those headings as examples, not strict list. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings, but also could use others? It says "e.g." implying those are examples, but we should probably stick to those headings for consistency. However we have content like "Location", "Language", "Interview Process". Those are not in the list. Should we create sections for them? Possibly not, because they are not in the given list; but we could still include them as if they have substantive content. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to map content to those headings.
We can have:
- About the role: includes description of role, what you'll own, etc.
- Responsibilities: maybe bullet list of duties.
- Requirements/Qualifications: experience, skills.
- Skills: maybe "The Kind of Builder We Want".
- Benefits: not mentioned; we should not create Benefits section unless posting actually states them. There's no explicit benefits listed. So we skip Benefits.
- Pay: not mentioned; skip.
- Schedule: not mentioned; skip.
We also have company overview "About BJAK". Could be placed before About the role as a
maybe not a heading. The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid a heading like "About BJAK". But the examples list didn't include that. However we could include a heading like "About BJAK" as
maybe okay. But to be safe, we could treat the company overview as a
before the sections, not a heading. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should prefer those. I'd include a brief
for company overview.
Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like: started 2019, first mobile-first insurance platform, leading insurance platform in SEA, expanding ways to help people in region — spending, saving, investing, exchanging, travelling, etc. Mission: help people get more from their money every day. Teams worldwide, over 20 nationalities, enjoy work. Looking for talented driven people, work for passion, love building great next-gen products, care about redefining how everyone can get best financial applications, not exclusive few.
Then "The Role": product managers to own product areas within BJAK's AI Stockbroking. Role for builders who can understand users, define product direction, work with engineering and design, launch fast and keep improving after release.
"What You'll Own": bullet list? It's a paragraph with multiple sentences: Own product areas across insurance, payments, savings, investing, travel or other financial services. Define user problems, product scope, success metrics, roadmap and launch plans. Work with engineering, design, data, operations, compliance and business teams. Turn complex financial products into simple, usable customer journeys. Use data, feedback, research and production issues to improve product decisions. Launch features, monitor performance and drive iterations. Make trade-offs between speed, user experience, business impact, compliance and operational complexity.
That's responsibilities.
"What We're Looking For": bullet list? It's sentences: Experience as Product Manager, Product Owner, founder, growth/product operator or similar role. Strong product sense and ability to simplify complex workflows. Able to work with engineers and designers to ship real products. Comfortable with metrics, user feedback, experiments and post-launch learning. Strong writing, prioritization and stakeholder management. High ownership and ability to drive work with limited guidance. Experience in fintech, insurance, payments, consumer apps or high-growth products is a strong advantage.
"The Kind of Builder We Want": bullet list? Sentences: Starts from user problems, not feature lists. Can make decisions with incomplete information. Knows how to ship quickly and learn after launch. Works well with engineering without hiding behind process. Honest about what changed because of their work versus wider team effort.
"This Role Is Not For": bullet list? Sentences: People who only write decks and do not drive execution. PMs who cannot work deeply with engineering. Candidates who need perfect data before making decisions. People who launch features and then stop caring. PMs who exaggerate business impact without understanding attribution.
"Location": This role is remote, but candidates must be based in US. We are hiring specifically for this market, so applicants should already be based in US.
"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 Role-specific 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.
We need to output HTML fragment with sections.
We need to decide which headings to use.
Potential sections:
- About the role: could include description of role (The Role, What You'll Own). Could combine.
- Responsibilities: bullet list of duties (maybe from What You'll Own). Could also include "Own product areas across ..." etc.
- Requirements: experience, qualifications (What We're Looking For).
- Skills: The Kind of Builder We Want (maybe also include what role is not for as negative? but could be part of Skills or separate). Could treat as "Skills".
- Location: maybe as a
not heading? But we could add a heading "Location" though not in examples. Might be okay but risk. The instruction says "include a section ONLY when the posting has real, specific content for it". It does not forbid headings not in examples. However they gave examples of headings; they didn't say you must only use those. I'd include Location as
because it's specific content. Similarly Language and Interview Process could be sections.
But they said "Prefer a few substantive sections over many thin ones." So maybe we should combine Location, Language, Interview Process into a single "Additional Information" section? But we don't have that heading in examples. Could use for "Additional Information". But better to follow examples: maybe we can treat Location, Language, Interview Process as
paragraphs under a generic "Details" section? Not ideal.
Given the instruction to prefer few substantive sections, we could have:
- About the role (includes role description and what you'll own)
- Responsibilities (bullet list)
- Requirements (bullet list)
- Skills (bullet list)
- Additional Info (Location, Language, Interview Process) as
paragraphs.
But we need to use
for section headings. So Additional Info heading would be Additional Info
. That's okay.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. It doesn't, so we skip.
Now we need to preserve all substantive information. Let's extract details.
Company overview 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 keep that as prose (
). Possibly break into multiple
for readability but not required.
Now The Role: "The Role We are looking for product managers to own product areas within BJAK's AI Stockbroking. This role is for builders who can understand users, define product direction, work with engineering and design, launch fast and keep improving after release."
We can incorporate into About the role section.
What You'll Own: list of responsibilities.
We'll turn each sentence into bullet list items? The instruction: Use
- for any list of duties/requirements/benefits. So we need to make a list for duties. We can break each responsibility into separate
- . Let's list:
- Own product areas across insurance, payments, savings, investing, travel or other financial services.
- Define user problems, product scope, success metrics, roadmap and launch plans.
- Work with engineering, design, data, operations, compliance and business teams.
- Turn complex financial products into simple, usable customer journeys.
- Use data, feedback, research and production issues to improve product decisions.
- Launch features, monitor performance and drive iterations.
- Make trade-offs between speed,
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting. Content: - About BJAK: description of company mission, history, etc. Could be "About the company" maybe but we have headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have sections: "About BJAK" (company overview). Could map to "About the role"? Actually "About the role" is more about the role description. But we have "The Role" and "What You'll Own". Could treat as "Responsibilities". Also "What We're Looking For" as "Requirements" or "Qualifications". "The Kind of Builder We Want" maybe "Skills". Also "Location", "Language", "Interview Process". Those might be extra but we only include sections if they have real specific content. We could include "Location" as maybe not in list but we can still include if needed? The instruction says use those headings as examples, not strict list. It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those headings, but also could use others? It says "e.g." implying those are examples, but we should probably stick to those headings for consistency. However we have content like "Location", "Language", "Interview Process". Those are not in the list. Should we create sections for them? Possibly not, because they are not in the given list; but we could still include them as if they have substantive content. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to map content to those headings.
We can have:
- About the role: includes description of role, what you'll own, etc.
- Responsibilities: maybe bullet list of duties.
- Requirements/Qualifications: experience, skills.
- Skills: maybe "The Kind of Builder We Want".
- Benefits: not mentioned; we should not create Benefits section unless posting actually states them. There's no explicit benefits listed. So we skip Benefits.
- Pay: not mentioned; skip.
- Schedule: not mentioned; skip.
We also have company overview "About BJAK". Could be placed before About the role as a
if they have substantive content. The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those. Safer to map content to those headings.
We can have:
- About the role: includes description of role, what you'll own, etc.
- Responsibilities: maybe bullet list of duties.
- Requirements/Qualifications: experience, skills.
- Skills: maybe "The Kind of Builder We Want".
- Benefits: not mentioned; we should not create Benefits section unless posting actually states them. There's no explicit benefits listed. So we skip Benefits.
- Pay: not mentioned; skip.
- Schedule: not mentioned; skip.
We also have company overview "About BJAK". Could be placed before About the role as a
maybe not a heading. The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid a heading like "About BJAK". But the examples list didn't include that. However we could include a heading like "About BJAK" as
maybe okay. But to be safe, we could treat the company overview as a
before the sections, not a heading. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should prefer those. I'd include a brief
for company overview. Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep details like: started 2019, first mobile-first insurance platform, leading insurance platform in SEA, expanding ways to help people in region — spending, saving, investing, exchanging, travelling, etc. Mission: help people get more from their money every day. Teams worldwide, over 20 nationalities, enjoy work. Looking for talented driven people, work for passion, love building great next-gen products, care about redefining how everyone can get best financial applications, not exclusive few. Then "The Role": product managers to own product areas within BJAK's AI Stockbroking. Role for builders who can understand users, define product direction, work with engineering and design, launch fast and keep improving after release. "What You'll Own": bullet list? It's a paragraph with multiple sentences: Own product areas across insurance, payments, savings, investing, travel or other financial services. Define user problems, product scope, success metrics, roadmap and launch plans. Work with engineering, design, data, operations, compliance and business teams. Turn complex financial products into simple, usable customer journeys. Use data, feedback, research and production issues to improve product decisions. Launch features, monitor performance and drive iterations. Make trade-offs between speed, user experience, business impact, compliance and operational complexity. That's responsibilities. "What We're Looking For": bullet list? It's sentences: Experience as Product Manager, Product Owner, founder, growth/product operator or similar role. Strong product sense and ability to simplify complex workflows. Able to work with engineers and designers to ship real products. Comfortable with metrics, user feedback, experiments and post-launch learning. Strong writing, prioritization and stakeholder management. High ownership and ability to drive work with limited guidance. Experience in fintech, insurance, payments, consumer apps or high-growth products is a strong advantage. "The Kind of Builder We Want": bullet list? Sentences: Starts from user problems, not feature lists. Can make decisions with incomplete information. Knows how to ship quickly and learn after launch. Works well with engineering without hiding behind process. Honest about what changed because of their work versus wider team effort. "This Role Is Not For": bullet list? Sentences: People who only write decks and do not drive execution. PMs who cannot work deeply with engineering. Candidates who need perfect data before making decisions. People who launch features and then stop caring. PMs who exaggerate business impact without understanding attribution. "Location": This role is remote, but candidates must be based in US. We are hiring specifically for this market, so applicants should already be based in US. "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 Role-specific 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. We need to output HTML fragment with sections. We need to decide which headings to use. Potential sections: - About the role: could include description of role (The Role, What You'll Own). Could combine. - Responsibilities: bullet list of duties (maybe from What You'll Own). Could also include "Own product areas across ..." etc. - Requirements: experience, qualifications (What We're Looking For). - Skills: The Kind of Builder We Want (maybe also include what role is not for as negative? but could be part of Skills or separate). Could treat as "Skills". - Location: maybe as a
not heading? But we could add a heading "Location" though not in examples. Might be okay but risk. The instruction says "include a section ONLY when the posting has real, specific content for it". It does not forbid headings not in examples. However they gave examples of headings; they didn't say you must only use those. I'd include Location as
because it's specific content. Similarly Language and Interview Process could be sections.
But they said "Prefer a few substantive sections over many thin ones." So maybe we should combine Location, Language, Interview Process into a single "Additional Information" section? But we don't have that heading in examples. Could use for "Additional Information". But better to follow examples: maybe we can treat Location, Language, Interview Process as
paragraphs under a generic "Details" section? Not ideal. Given the instruction to prefer few substantive sections, we could have: - About the role (includes role description and what you'll own) - Responsibilities (bullet list) - Requirements (bullet list) - Skills (bullet list) - Additional Info (Location, Language, Interview Process) as
paragraphs. But we need to use
for section headings. So Additional Info heading would be Additional Info
. That's okay.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. It doesn't, so we skip.
Now we need to preserve all substantive information. Let's extract details.
Company overview 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 keep that as prose (
). Possibly break into multiple
for readability but not required. Now The Role: "The Role We are looking for product managers to own product areas within BJAK's AI Stockbroking. This role is for builders who can understand users, define product direction, work with engineering and design, launch fast and keep improving after release." We can incorporate into About the role section. What You'll Own: list of responsibilities. We'll turn each sentence into bullet list items? The instruction: Use
- for any list of duties/requirements/benefits. So we need to make a list for duties. We can break each responsibility into separate
- . Let's list: - Own product areas across insurance, payments, savings, investing, travel or other financial services. - Define user problems, product scope, success metrics, roadmap and launch plans. - Work with engineering, design, data, operations, compliance and business teams. - Turn complex financial products into simple, usable customer journeys. - Use data, feedback, research and production issues to improve product decisions. - Launch features, monitor performance and drive iterations. - Make trade-offs between speed,