Android Software Engineer - AI Finance Agent

We need to output HTML fragment with sections: About the role? Actually we need to reformat job posting into clean semantic HTML. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Content: - About BJAK: description of company. Could be "About the role"? Actually "About BJAK" is company description. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have sections: The Role (description of what you'll own) -> could be Responsibilities. What We're Looking For -> Requirements/Qualifications/Skills. Tech Stack -> maybe Skills. The Kind of Builder We Want -> maybe Qualities? Could be part of Requirements. This Role Is Not For -> maybe not needed. Location -> could be part of something else but not a heading we have; we could embed in a paragraph maybe under About the role? But we have no heading for location; we could include in a

under About the role? The instruction: only include sections when posting has real specific content. We have location info: remote but must be based in US. That's specific. Could we put under a heading like "Location"? Not in allowed list. So we must fold minor metadata into a short

or drop it. So we can include location in a paragraph maybe under About the role or under a generic paragraph. Probably best to add a

after the role description. Language: English required. Interview Process: could be a section? Not in allowed headings. Could fold into a paragraph under About the role? Might be considered minor metadata. We'll include as a paragraph. We must not include boilerplate like cookie/navigation/legal/EEO etc. None present. We must not invent or summarize away detail. Preserve all substantive information. We need to use

• for any list of duties/requirements/benefits. So for responsibilities list (What You'll Own) we need a
  . For requirements list (What We're Looking For) also a
  . For Tech Stack maybe also a list. For Kind of Builder maybe list. We must not create Pay/Schedule/Benefits sections unless posting actually states them. No pay, schedule, benefits mentioned. So we omit those sections. We need to decide which headings to use: About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly also "About the role" for company description? Actually "About the role" could be used for description of role (The Role). But we also have "What You'll Own" which is responsibilities. So maybe: -

  About the role

  : includes company description (About BJAK) and maybe role overview? But we have separate "The Role" heading. Could treat "About the role" as the role overview (The Role). Then Responsibilities as What You'll Own. Requirements as What We're Looking For. Qualifications maybe same as Requirements? Could combine. Skills could be Tech Stack. We must not repeat headings with filler. So we need to ensure each heading has substantive content. Let's structure:

  About the role

  ... company description and role overview ...

  Responsibilities

  • ... each bullet from What You'll Own ...

  Requirements

  • ... each bullet from What We're Looking For ...

  Skills

  • ... each item from Tech Stack ...
  Optionally include Language and Location and Interview Process as paragraphs under About the role or after Skills. We must not create Pay/Benefits/Schedule sections. Now ensure we preserve all substantive information: company description, mission, remote location US, language English, interview process steps. Let's extract details: About BJAK: - Original mission: people deserve smarter ways to plan, save and grow their money. Origin of name. - Started 2019, built first mobile-first insurance platform enabling insurance accessible online by millions in region. - Today leading insurance platform in Southeast Asia. - Expanding ways to help people in region — spending, saving, investing, exchanging, travelling, and more. - Mission: help people get more from their money every day. - Teams worldwide, over 20 nationalities from offices and remotely, who truly enjoy work. - Looking for most talented and driven people. - Looking for people who work for passion, not counting hours. - Love building great next-gen products, not status quo. - Care about redefining how everyone can get best financial applications, not for exclusive few. - If you're this person, we'd love to talk. The Role: - Looking for Android software engineers to build native Android experience for BJAK's AI Finance Agent. - Role for someone who cares about clean user flows, fast performance, product quality and shipping reliable mobile features used by real customers. What You'll Own: - Build and ship Android features using Kotlin. - Create clean mobile flows for insurance, payments, claims, renewals and financial services. - Work with product and design to simplify complex user journeys. - Integrate backend APIs and ensure mobile flows are stable, secure and reliable. - Improve app performance, crash rate, loading states, responsiveness and memory usage. - Use analytics, user behaviour and production issues to improve the product. - Build AI-assisted mobile experiences only where they genuinely improve the user journey. What We're Looking For: - 3+ years of Android development experience using Kotlin. - Strong Android fundamentals and experience shipping production apps. - Good knowledge of Jetpack, Coroutines, Flow and modern Android architecture. - Strong sense of mobile UX, usability, edge cases and user flows. - Experience integrating REST APIs and debugging production issues. - Fast execution, high ownership and strong attention to product quality. - App links, GitHub, screenshots or examples of shipped work are a strong advantage. Tech Stack: - Kotlin - Jetpack Compose - Android SDK - Coroutines & Flow - SQL / NoSQL - TensorFlow Lite (on-device inference) The Kind of Builder We Want: - Thinks in user journeys, not just screens. - Cares about making complex financial products feel simple. - Moves fast without creating messy code. - Notices UX, performance and reliability issues before users complain. - Honest about what they personally built, what was team-owned and what impact they can or cannot claim. This Role Is Not For: - Engineers who only want fully defined tickets. - Developers who build screens without caring about user experience. - People who ignore crashes, edge cases, loading states or performance. - Engineers who move slowly in a startup environment. - People who exaggerate impact without explaining their actual contribution. Location: - This role is remote, but candidates must be based in The United States. - We are hiring specifically for this market, so applicants should already be based in The United States. Language: - English is our main working language across global teams. - Strong English communication is required. Interview Process: - Our process is designed to move fast: 1. Online assessment or practical task 2. Role-specific interview 3. 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 preserve all this. Now decide where to put each. About the role: Could include company description and maybe role overview (The Role). Let's put company description and the brief role overview (Looking for Android software engineers...). Then Responsibilities: What You'll Own. Requirements: What We're Looking For (including experience, fundamentals, knowledge, UX, APIs, execution, advantage). Could also include The Kind of Builder We Want as part of Requirements or Qualifications. But we have Qualifications heading available; we could put Kind of Builder there. However Qualifications might be similar to Requirements. To avoid thin sections, we could combine Requirements and Qualifications into one section? But we have separate headings allowed; we could use Requirements for hard requirements, and Qualifications for soft/builder traits. That seems reasonable. Skills: Tech Stack. Then after Skills we can add paragraphs for Location, Language, Interview Process. We must not create extra headings like Location etc. So we will put them as

  under maybe a generic section? But we have no heading for them. We could just place them as

  after Skills without a heading. That's allowed: we can have prose paragraphs not under a heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid having paragraphs outside headings, but likely they expect sections. However we can include them as part of Skills section? Might be odd. Better to create a section like "Additional info" but not allowed. So we could fold them into Skills section as extra list items? Not appropriate. Alternative: we could treat Location, Language, Interview Process as part of "About the role" section (company info). That seems plausible: About the role can include company description, location, language, interview process. That would keep headings limited to the allowed ones. Thus:

  About the role

  Company description...

  Location: remote but must be based in the United States...

  Language: English is main working language; strong English communication required.

  Interview process: online assessment or practical task, role-specific interview, CEO/final round; aim to complete within 1 week for strong candidates; quick assessment completion prioritized.

  Then Responsibilities, Requirements, Qualifications, Skills. Now check if we have any content for Qualifications: we have The Kind of Builder We Want. That's suitable. Now ensure we don't repeat headings with filler. Now produce HTML. We need to use
  • for any list of duties/requirements/benefits. So for Responsibilities, Requirements, Qualifications, Skills we need lists. Let's extract each bullet. Responsibilities (What You'll Own): - Build and ship Android features using Kotlin. - Create clean mobile flows for insurance, payments, claims, renewals and financial services. - Work with product and design to simplify complex user journeys. - Integrate backend APIs and ensure mobile flows are stable, secure and reliable. - Improve app performance, crash rate, loading states, responsiveness and memory usage. - Use analytics, user behaviour and production issues to improve the product. - Build AI-assisted mobile experiences only where they genuinely improve the user journey. Requirements (What We're Looking For): - 3+ years of Android development experience using Kotlin. - Strong Android fundamentals and experience shipping production apps. - Good knowledge of Jetpack, Coroutines, Flow and modern Android architecture. - Strong sense of mobile UX, usability, edge cases and user flows. - Experience integrating REST APIs and debugging production issues. - Fast execution, high ownership and strong attention to product quality. - App links, GitHub, screenshots or examples of shipped work are a strong advantage. Qualifications (The Kind of Builder We Want): - Thinks in user journeys, not just screens. - Cares about making complex financial products feel simple. - Moves fast without creating messy code. - Notices UX, performance and reliability issues before users complain. - Honest about what they personally built, what was team-owned and what impact they can or cannot claim. Skills (Tech Stack): - Kotlin - Jetpack Compose - Android SDK - Coroutines & Flow - SQL / NoSQL - TensorFlow Lite (on-device inference) Now About the role paragraph content: We need to include company description and role overview. Company description: "About BJAKThe original