Android Software Engineer - AI Neobank App
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content.
We have content: About Doit (company description). The Role (description). What You'll Own (responsibilities). What We're Looking For (requirements/qualifications). Tech Stack (maybe Skills). The Kind of Builder We Want (maybe more qualifications). This Role Is Not For (maybe not needed). Location (maybe schedule? Actually location is remote but US based). Language (maybe not needed). Interview Process (maybe not needed but could be considered as part of process but not required). We should omit boilerplate like cookie/navigation/legal/EEO etc. There's none.
We need to preserve all substantive info, not invent. Do not repeat job title as heading. No Job ID.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We should avoid sections with filler like "commensurate with experience". Not present.
We need to decide which sections to include: About (maybe "About the company" but they said "About the role" as example; but we can use "About Doit" as heading? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings if appropriate? Probably we should stick to those examples. But we have "About Doit" which is about company, not role. Could use "About the role" heading and put the company description there? Might be okay. However they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have "About the role" as heading and include company description and role overview.
Then "Responsibilities" for What You'll Own.
Then "Requirements" or "Qualifications" for What We're Looking For and The Kind of Builder We Want (maybe combine). Could also have "Skills" for Tech Stack.
We should not create Pay/Schedule/Benefits unless present. Not present.
Location: maybe we could include as a short
under a section? But they said only include a section when posting has real, specific content for it. Location is specific: remote but US based. Could be a short paragraph under maybe "About the role" or separate? There's no example heading for location; but we could include as a
within a section like "About the role". However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could add a section for Location if we want, but not in the list. Safer to keep within existing sections.
Language: maybe also within About.
Interview Process: maybe we could include as a section? Not in list but could be omitted? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we omit Interview Process as it's thin? But it's substantive. However they didn't list Interview Process as example heading; but we could still use for it? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those.
Thus we will have sections: About the role, Responsibilities, Requirements, Skills.
We need to include all substantive info.
Let's extract:
About Doit: paragraph about mission, AI, etc. Also mention 2019 insurance platform, leading in SEA. Also mention teams worldwide, over 20 nationalities, remote offices. Also mention objective to build tools to help people get more from money, become expert at ease. Also mention belief AI will help finance smart, assessible and safe. Also mention looking for talented people, passion, building next-gen products, caring about redefining financial apps for everyone, not exclusive few. Also mention remote but US based? Actually location later.
The Role: Android software engineers to build native Android experience for Doit's AI Neobank App. Cares about clean user flows, fast performance, product quality, shipping reliable mobile features used by real customers.
What You'll Own: bullet list:
- 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: bullet list:
- 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: list:
- Kotlin
- Jetpack Compose
- Android SDK
- Coroutines & Flow
- SQL / NoSQL
- TensorFlow Lite (on-device inference)
The Kind of Builder We Want: bullet list (maybe as part of Requirements):
- 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: bullet list (maybe we could omit as it's negative but still substantive). Could include under Requirements as "Not suitable for". But maybe we can include as a separate subsection under Requirements? Might be okay.
Location: remote, but candidates must be based in US. Language: English is main working language, strong English communication required.
Interview Process: steps.
We need to decide what to include. Since we want few substantive sections, we could combine many into Requirements and Skills.
Let's propose sections:
About the role
... combine About Doit, The Role, Location, Language maybe.
Responsibilities
... What You'll Own
Requirements
... What We're Looking For, The Kind of Builder We Want, This Role Is Not For (maybe as negative), Language requirement.
Skills
... Tech Stack
We could also include Interview Process as a separate section but maybe it's thin? It's three steps and timeline. Could be included as under About the role? Might be okay.
But we need to preserve all substantive info. If we put Interview Process inside About the role paragraph, it's still preserved.
Let's craft.
We must not include boilerplate like cookie/navigation/legal/EEO etc. None.
We must not repeat job title as heading. Not.
We must not put Job ID/requisition numbers as headings. None.
We must not create Pay/Schedule/Benefits sections unless posting actually states them. Not present.
We must not emit heading followed by filler/placeholder text. We'll avoid.
Now produce HTML fragment.
Let's write:
About the role
Doit is focused on reinventing how people spend, save, invest, exchange, travel, and more, building tools that help people get more from their money and become experts at ease. The company believes AI will make finance smart, accessible, and safe, and seeks talented, driven people who work for passion, not just hours, and love building next‑generation products that redefine financial applications for everyone, not just an exclusive few. With teams in over 20 nationalities across global offices and remote work, Doit launched the first mobile‑first insurance platform in 2019, now the leading insurance platform in Southeast Asia. This role is for an Android software engineer to build the native Android experience for Doit's AI Neobank App, focusing on clean user flows, fast performance, product quality, and shipping reliable mobile features used by real customers. The position is remote but requires candidates to be based in the US, with English as the main working language and strong communication skills required.
Responsibilities
- 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
- 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.
- 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.
- Strong English communication is required.
- This role is not suited for engineers who only want fully defined tickets, developers who build screens without caring about UX, people who ignore crashes, edge cases, loading states or performance, engineers who move slowly in a startup environment, or those who exaggerate impact without explaining their actual contribution.
Skills
- Kotlin
- Jetpack Compose
- Android SDK
- Coroutines & Flow
- SQL / NoSQL
- TensorFlow Lite (on‑device inference)
We should ensure no extra whitespace issues. Output only HTML fragment.
Let's double-check we didn't miss any substantive info: The interview process details (online assessment, role-specific interview, CEO/final round, aim to complete within 1 week, prioritize fast completions). We omitted that. Should we include? It's substantive. Could add a short paragraph under About the role or maybe a separate section "Process". But we said prefer few sections. Could add a under About the role after the location paragraph. Let's add a paragraph about interview process.
Add after location sentence: "The interview process consists of an online assessment or practical task, a role‑specific interview, and a CEO/final round, with the goal of making an offer within one week for strong candidates; those who complete assessments quickly are prioritized."
Thus About the role paragraph will be longer.
Let's rewrite
- for any list of duties/requirements/benefits, and
for prose. We should avoid sections with filler like "commensurate with experience". Not present. We need to decide which sections to include: About (maybe "About the company" but they said "About the role" as example; but we can use "About Doit" as heading? The instruction: use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use other headings if appropriate? Probably we should stick to those examples. But we have "About Doit" which is about company, not role. Could use "About the role" heading and put the company description there? Might be okay. However they said "Do NOT repeat the job title as a heading (the page already shows it)". So we can have "About the role" as heading and include company description and role overview. Then "Responsibilities" for What You'll Own. Then "Requirements" or "Qualifications" for What We're Looking For and The Kind of Builder We Want (maybe combine). Could also have "Skills" for Tech Stack. We should not create Pay/Schedule/Benefits unless present. Not present. Location: maybe we could include as a short
under a section? But they said only include a section when posting has real, specific content for it. Location is specific: remote but US based. Could be a short paragraph under maybe "About the role" or separate? There's no example heading for location; but we could include as a
within a section like "About the role". However they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we could add a section for Location if we want, but not in the list. Safer to keep within existing sections. Language: maybe also within About. Interview Process: maybe we could include as a section? Not in list but could be omitted? The instruction: "Prefer a few substantive sections over many thin ones." So maybe we omit Interview Process as it's thin? But it's substantive. However they didn't list Interview Process as example heading; but we could still use
for it? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. Thus we will have sections: About the role, Responsibilities, Requirements, Skills. We need to include all substantive info. Let's extract: About Doit: paragraph about mission, AI, etc. Also mention 2019 insurance platform, leading in SEA. Also mention teams worldwide, over 20 nationalities, remote offices. Also mention objective to build tools to help people get more from money, become expert at ease. Also mention belief AI will help finance smart, assessible and safe. Also mention looking for talented people, passion, building next-gen products, caring about redefining financial apps for everyone, not exclusive few. Also mention remote but US based? Actually location later. The Role: Android software engineers to build native Android experience for Doit's AI Neobank App. Cares about clean user flows, fast performance, product quality, shipping reliable mobile features used by real customers. What You'll Own: bullet list: - 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: bullet list: - 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: list: - Kotlin - Jetpack Compose - Android SDK - Coroutines & Flow - SQL / NoSQL - TensorFlow Lite (on-device inference) The Kind of Builder We Want: bullet list (maybe as part of Requirements): - 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: bullet list (maybe we could omit as it's negative but still substantive). Could include under Requirements as "Not suitable for". But maybe we can include as a separate subsection under Requirements? Might be okay. Location: remote, but candidates must be based in US. Language: English is main working language, strong English communication required. Interview Process: steps. We need to decide what to include. Since we want few substantive sections, we could combine many into Requirements and Skills. Let's propose sections:
About the role
... combine About Doit, The Role, Location, Language maybe.
Responsibilities
- ... What You'll Own
Requirements
- ... What We're Looking For, The Kind of Builder We Want, This Role Is Not For (maybe as negative), Language requirement.
Skills
- ... Tech Stack
under About the role? Might be okay. But we need to preserve all substantive info. If we put Interview Process inside About the role paragraph, it's still preserved. Let's craft. We must not include boilerplate like cookie/navigation/legal/EEO etc. None. We must not repeat job title as heading. Not. We must not put Job ID/requisition numbers as headings. None. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Not present. We must not emit heading followed by filler/placeholder text. We'll avoid. Now produce HTML fragment. Let's write:
About the role
Doit is focused on reinventing how people spend, save, invest, exchange, travel, and more, building tools that help people get more from their money and become experts at ease. The company believes AI will make finance smart, accessible, and safe, and seeks talented, driven people who work for passion, not just hours, and love building next‑generation products that redefine financial applications for everyone, not just an exclusive few. With teams in over 20 nationalities across global offices and remote work, Doit launched the first mobile‑first insurance platform in 2019, now the leading insurance platform in Southeast Asia. This role is for an Android software engineer to build the native Android experience for Doit's AI Neobank App, focusing on clean user flows, fast performance, product quality, and shipping reliable mobile features used by real customers. The position is remote but requires candidates to be based in the US, with English as the main working language and strong communication skills required.
Responsibilities
- 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
- 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.
- 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.
- Strong English communication is required.
- This role is not suited for engineers who only want fully defined tickets, developers who build screens without caring about UX, people who ignore crashes, edge cases, loading states or performance, engineers who move slowly in a startup environment, or those who exaggerate impact without explaining their actual contribution.
Skills
- Kotlin
- Jetpack Compose
- Android SDK
- Coroutines & Flow
- SQL / NoSQL
- TensorFlow Lite (on‑device inference)
under About the role after the location paragraph. Let's add a paragraph about interview process. Add after location sentence: "The interview process consists of an online assessment or practical task, a role‑specific interview, and a CEO/final round, with the goal of making an offer within one week for strong candidates; those who complete assessments quickly are prioritized." Thus About the role paragraph will be longer. Let's rewrite