Lead Android Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests we should use those headings if applicable. However we can also use other headings? It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to map content to those standard headings where appropriate. But we can also use other headings if they fit? The examples are just examples; they didn't forbid other headings. However they say "use for section headings". So any heading we output should be . We'll produce sections: About the role (maybe from "Why Rogo" and "The Role"?), Responsibilities (What You’ll Own), Requirements (What You’ll Need + Bonus?), Qualifications (maybe same as Requirements), Skills (maybe from What You’ll Need), Benefits (Why Join Rogo?), Pay (none), Schedule (none). We should only include sections when posting has real specific content. Pay and Schedule not present, so omit.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to not repeat job title as heading. Not include Job ID.
We need to output only HTML fragment.
Let's parse content:
"Why Rogo" paragraph: mission description. Could go under About the role? Or maybe we treat as About the role (company overview). We'll put
About the role
then with that paragraph.
"The Role": description of role. Could be part of About the role? But we already used About the role for company. Maybe better: Use About the role for role description? Actually "About the role" typical heading for role description. The "Why Rogo" is company mission. Could be separate section like "About the company". But not in list. However we can still use
About the role
for role description, and maybe include company mission in a preceding before that? But we need to preserve all info. Could combine: first
company mission, then
About the role
then role description.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings where appropriate. So we can have:
About the role
(role description)
Responsibilities
(What You’ll Own)
Requirements
(What You’ll Need)
Skills
maybe from Bonus? Or we could incorporate Bonus into Requirements or Skills. But we need to avoid thin sections. Could combine Requirements and Skills into one? But they said prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits. Skills could be part of Requirements. Bonus could be part of Requirements as "Preferred qualifications". But we need to preserve all detail; we can include Bonus as a under Requirements with heading "Preferred qualifications"? But we cannot create new headings not in list? 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 they gave examples. Safer to stick to those headings. We can map Bonus to Skills (preferred skills). So we can have Skills section for bonus items.
Qualifications maybe same as Requirements; we could omit Qualifications to avoid duplication.
Thus sections:
- About the role (company mission + role overview? Actually role overview is in The Role paragraph; we could put that in About the role.)
- Responsibilities (What You’ll Own)
- Requirements (What You’ll Need)
- Skills (Bonus)
- Benefits (Why Join Rogo?)
Check each for substantive content.
Now we need to format lists.
Let's extract content.
About the role: combine "Why Rogo" paragraph and "The Role" paragraph (first paragraph of The Role? Actually The Role includes multiple paragraphs: "We’re looking for a Lead Android Engineer...". That's role description. We'll include that as prose.
So About the role
will contain both mission and role description? Might be long but okay.
Responsibilities: "What You’ll Own" bullet list. We'll turn each line into
- .
Requirements: "What You’ll Need" bullet list. We'll turn each line into
- .
Skills: "Bonus" bullet list. We'll turn each line into
- .
Benefits: "Why Join Rogo?" bullet list? Actually it's a few paragraphs with bold headings: Up and to the right..., Extraordinary team..., A one-of-one problem..., Real ownership..., Always at the frontier... We'll treat each as
- .
Now ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
We need to wrap each section:
About the role
...
then Responsibilities
- ...
etc.
Make sure to not include extra blank lines? It's fine.
Let's craft the prose.
About the role prose:
Combine:
"Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want to help build the future of finance, we invite you to join us."
Then The Role paragraph:
"We’re looking for a Lead Android Engineer to build Rogo’s Android app from the ground up. Rogo is not available on Android app yet. You will start with a blank canvas and own the foundational decisions that shape the product for years to come: architecture, technology choices, design patterns, development standards, release processes, observability, and quality. You won’t be maintaining someone else’s decisions or modernizing a legacy codebase. You’ll define what excellent Android engineering looks like at Rogo. You’ll work directly with product, design, engineering, and customers to translate Rogo’s AI platform into an exceptional native mobile experience. You’ll decide how sophisticated, AI-powered financial workflows should work on Android and then build them. This is a rare opportunity to create a category-defining application from its first line of code, ship it to demanding professional users, and build the foundation for an Android engineering team around your work."
Combine into one maybe two
? The instruction says use
for prose. Could have multiple
elements. We'll separate into two
for readability.
Now Responsibilities list items:
- Build and launch the first version of Rogo’s native Android application
- Define the application’s architecture, technical stack, and core engineering patterns
- Establish the standards for testing, security, performance, observability, releases, and code quality
- Partner closely with product and design to define how AI-native workflows should work on mobile
- Own major features end-to-end, from early user research and technical design through launch and iteration
- Create smooth, stable, and responsive experiences across the Android device ecosystem
- Integrate Rogo’s AI platform and backend services into an intuitive native experience
- Develop reusable foundations that allow the application and future Android team to scale
- Work directly with customers and Customer Success to understand professional workflows and rapidly incorporate feedback
- Help hire, mentor, and set the technical bar for future Android engineers
Now Requirements list:
- 5+ years of professional Android development experience
- A track record of building and launching high-quality Android applications
- Strong command of Kotlin, Jetpack Compose, and the Android SDK
- Experience making foundational architecture and technology decisions
- Deep understanding of Android application architecture, lifecycle management, and platform conventions
- Experience with Kotlin coroutines, Flow, concurrency, threading, and performance optimization
- Strong product judgment and an instinct for polished, intuitive user experiences
- Experience designing reusable, testable components and maintainable application architecture
- High standards for reliability, security, privacy, and production readiness
- Comfort operating with ambiguity and turning an open-ended opportunity into a shipped product
- Passion for building delightful AI-powered experiences
Now Skills (Bonus) list:
- You have built an Android app or major mobile product from zero to one
- You have been an early mobile engineer at a fast-growing startup
- Experience with Java, RxJava, Dagger or Hilt, and established Android architecture patterns
- Experience integrating with backend services through REST APIs, gRPC, WebSockets, or Server-Sent Events
- Experience with offline functionality, local persistence, background processing, and push notifications
- Experience deploying Android applications in an enterprise context, including managed Google Play, Microsoft Intune, or mobile-device-management environments
- Experience building secure applications that handle sensitive enterprise data
- Background at a design-forward product company such as Notion or Figma
- Strong interest in AI and how it can reshape professional mobile workflows
Now Benefits list (Why Join Rogo?):
- Up and to the right: Rogo has strong product adoption with the world's leading financial institutions, and we are still early. The upside is enormous.
- Extraordinary team: we take talent density seriously. You'll do the best work of your career alongside some of the sharpest people in AI and finance.
- A one-of-one problem: bringing AI to the core of how Wall Street works is one of the most ambitious, technically demanding, and consequential problems today. There is nowhere else you can work on it at this scale.
- Real ownership: You'll own real surface area and watch the world's most sophisticated users rely on your work.
- Always at the frontier: we work at the edge of what the best models can do and turn it into products people trust. If you're obsessed with AI, this is where it's happening.
Now produce HTML.
We'll output:
About the role
Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they want us to map content to those standard headings where appropriate. But we can also use other headings if they fit? The examples are just examples; they didn't forbid other headings. However they say "use for section headings". So any heading we output should be . We'll produce sections: About the role (maybe from "Why Rogo" and "The Role"?), Responsibilities (What You’ll Own), Requirements (What You’ll Need + Bonus?), Qualifications (maybe same as Requirements), Skills (maybe from What You’ll Need), Benefits (Why Join Rogo?), Pay (none), Schedule (none). We should only include sections when posting has real specific content. Pay and Schedule not present, so omit.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to not repeat job title as heading. Not include Job ID.
We need to output only HTML fragment.
Let's parse content:
"Why Rogo" paragraph: mission description. Could go under About the role? Or maybe we treat as About the role (company overview). We'll put
About the role
then with that paragraph.
"The Role": description of role. Could be part of About the role? But we already used About the role for company. Maybe better: Use About the role for role description? Actually "About the role" typical heading for role description. The "Why Rogo" is company mission. Could be separate section like "About the company". But not in list. However we can still use
About the role
for role description, and maybe include company mission in a preceding before that? But we need to preserve all info. Could combine: first
company mission, then
About the role
then role description.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings where appropriate. So we can have:
About the role
(role description)
Responsibilities
(What You’ll Own)
Requirements
(What You’ll Need)
Skills
maybe from Bonus? Or we could incorporate Bonus into Requirements or Skills. But we need to avoid thin sections. Could combine Requirements and Skills into one? But they said prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits. Skills could be part of Requirements. Bonus could be part of Requirements as "Preferred qualifications". But we need to preserve all detail; we can include Bonus as a under Requirements with heading "Preferred qualifications"? But we cannot create new headings not in list? 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 they gave examples. Safer to stick to those headings. We can map Bonus to Skills (preferred skills). So we can have Skills section for bonus items.
Qualifications maybe same as Requirements; we could omit Qualifications to avoid duplication.
Thus sections:
- About the role (company mission + role overview? Actually role overview is in The Role paragraph; we could put that in About the role.)
- Responsibilities (What You’ll Own)
- Requirements (What You’ll Need)
- Skills (Bonus)
- Benefits (Why Join Rogo?)
Check each for substantive content.
Now we need to format lists.
Let's extract content.
About the role: combine "Why Rogo" paragraph and "The Role" paragraph (first paragraph of The Role? Actually The Role includes multiple paragraphs: "We’re looking for a Lead Android Engineer...". That's role description. We'll include that as prose.
So About the role
will contain both mission and role description? Might be long but okay.
Responsibilities: "What You’ll Own" bullet list. We'll turn each line into
- .
Requirements: "What You’ll Need" bullet list. We'll turn each line into
- .
Skills: "Bonus" bullet list. We'll turn each line into
- .
Benefits: "Why Join Rogo?" bullet list? Actually it's a few paragraphs with bold headings: Up and to the right..., Extraordinary team..., A one-of-one problem..., Real ownership..., Always at the frontier... We'll treat each as
- .
Now ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
We need to wrap each section:
About the role
...
then Responsibilities
- ...
etc.
Make sure to not include extra blank lines? It's fine.
Let's craft the prose.
About the role prose:
Combine:
"Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want to help build the future of finance, we invite you to join us."
Then The Role paragraph:
"We’re looking for a Lead Android Engineer to build Rogo’s Android app from the ground up. Rogo is not available on Android app yet. You will start with a blank canvas and own the foundational decisions that shape the product for years to come: architecture, technology choices, design patterns, development standards, release processes, observability, and quality. You won’t be maintaining someone else’s decisions or modernizing a legacy codebase. You’ll define what excellent Android engineering looks like at Rogo. You’ll work directly with product, design, engineering, and customers to translate Rogo’s AI platform into an exceptional native mobile experience. You’ll decide how sophisticated, AI-powered financial workflows should work on Android and then build them. This is a rare opportunity to create a category-defining application from its first line of code, ship it to demanding professional users, and build the foundation for an Android engineering team around your work."
Combine into one maybe two
? The instruction says use
for prose. Could have multiple
elements. We'll separate into two
for readability.
Now Responsibilities list items:
- Build and launch the first version of Rogo’s native Android application
- Define the application’s architecture, technical stack, and core engineering patterns
- Establish the standards for testing, security, performance, observability, releases, and code quality
- Partner closely with product and design to define how AI-native workflows should work on mobile
- Own major features end-to-end, from early user research and technical design through launch and iteration
- Create smooth, stable, and responsive experiences across the Android device ecosystem
- Integrate Rogo’s AI platform and backend services into an intuitive native experience
- Develop reusable foundations that allow the application and future Android team to scale
- Work directly with customers and Customer Success to understand professional workflows and rapidly incorporate feedback
- Help hire, mentor, and set the technical bar for future Android engineers
Now Requirements list:
- 5+ years of professional Android development experience
- A track record of building and launching high-quality Android applications
- Strong command of Kotlin, Jetpack Compose, and the Android SDK
- Experience making foundational architecture and technology decisions
- Deep understanding of Android application architecture, lifecycle management, and platform conventions
- Experience with Kotlin coroutines, Flow, concurrency, threading, and performance optimization
- Strong product judgment and an instinct for polished, intuitive user experiences
- Experience designing reusable, testable components and maintainable application architecture
- High standards for reliability, security, privacy, and production readiness
- Comfort operating with ambiguity and turning an open-ended opportunity into a shipped product
- Passion for building delightful AI-powered experiences
Now Skills (Bonus) list:
- You have built an Android app or major mobile product from zero to one
- You have been an early mobile engineer at a fast-growing startup
- Experience with Java, RxJava, Dagger or Hilt, and established Android architecture patterns
- Experience integrating with backend services through REST APIs, gRPC, WebSockets, or Server-Sent Events
- Experience with offline functionality, local persistence, background processing, and push notifications
- Experience deploying Android applications in an enterprise context, including managed Google Play, Microsoft Intune, or mobile-device-management environments
- Experience building secure applications that handle sensitive enterprise data
- Background at a design-forward product company such as Notion or Figma
- Strong interest in AI and how it can reshape professional mobile workflows
Now Benefits list (Why Join Rogo?):
- Up and to the right: Rogo has strong product adoption with the world's leading financial institutions, and we are still early. The upside is enormous.
- Extraordinary team: we take talent density seriously. You'll do the best work of your career alongside some of the sharpest people in AI and finance.
- A one-of-one problem: bringing AI to the core of how Wall Street works is one of the most ambitious, technically demanding, and consequential problems today. There is nowhere else you can work on it at this scale.
- Real ownership: You'll own real surface area and watch the world's most sophisticated users rely on your work.
- Always at the frontier: we work at the edge of what the best models can do and turn it into products people trust. If you're obsessed with AI, this is where it's happening.
Now produce HTML.
We'll output:
About the role
Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want
. We'll produce sections: About the role (maybe from "Why Rogo" and "The Role"?), Responsibilities (What You’ll Own), Requirements (What You’ll Need + Bonus?), Qualifications (maybe same as Requirements), Skills (maybe from What You’ll Need), Benefits (Why Join Rogo?), Pay (none), Schedule (none). We should only include sections when posting has real specific content. Pay and Schedule not present, so omit.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to not repeat job title as heading. Not include Job ID.
We need to output only HTML fragment.
Let's parse content:
"Why Rogo" paragraph: mission description. Could go under About the role? Or maybe we treat as About the role (company overview). We'll put
About the role
then with that paragraph.
"The Role": description of role. Could be part of About the role? But we already used About the role for company. Maybe better: Use About the role for role description? Actually "About the role" typical heading for role description. The "Why Rogo" is company mission. Could be separate section like "About the company". But not in list. However we can still use
About the role
for role description, and maybe include company mission in a preceding before that? But we need to preserve all info. Could combine: first
company mission, then
About the role
then role description.
But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings where appropriate. So we can have:
About the role
(role description)
Responsibilities
(What You’ll Own)
Requirements
(What You’ll Need)
Skills
maybe from Bonus? Or we could incorporate Bonus into Requirements or Skills. But we need to avoid thin sections. Could combine Requirements and Skills into one? But they said prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits. Skills could be part of Requirements. Bonus could be part of Requirements as "Preferred qualifications". But we need to preserve all detail; we can include Bonus as a under Requirements with heading "Preferred qualifications"? But we cannot create new headings not in list? 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 they gave examples. Safer to stick to those headings. We can map Bonus to Skills (preferred skills). So we can have Skills section for bonus items.
Qualifications maybe same as Requirements; we could omit Qualifications to avoid duplication.
Thus sections:
- About the role (company mission + role overview? Actually role overview is in The Role paragraph; we could put that in About the role.)
- Responsibilities (What You’ll Own)
- Requirements (What You’ll Need)
- Skills (Bonus)
- Benefits (Why Join Rogo?)
Check each for substantive content.
Now we need to format lists.
Let's extract content.
About the role: combine "Why Rogo" paragraph and "The Role" paragraph (first paragraph of The Role? Actually The Role includes multiple paragraphs: "We’re looking for a Lead Android Engineer...". That's role description. We'll include that as prose.
So About the role
will contain both mission and role description? Might be long but okay.
Responsibilities: "What You’ll Own" bullet list. We'll turn each line into
- .
Requirements: "What You’ll Need" bullet list. We'll turn each line into
- .
Skills: "Bonus" bullet list. We'll turn each line into
- .
Benefits: "Why Join Rogo?" bullet list? Actually it's a few paragraphs with bold headings: Up and to the right..., Extraordinary team..., A one-of-one problem..., Real ownership..., Always at the frontier... We'll treat each as
- .
Now ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
We need to wrap each section:
About the role
...
then Responsibilities
- ...
etc.
Make sure to not include extra blank lines? It's fine.
Let's craft the prose.
About the role prose:
Combine:
"Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want to help build the future of finance, we invite you to join us."
Then The Role paragraph:
"We’re looking for a Lead Android Engineer to build Rogo’s Android app from the ground up. Rogo is not available on Android app yet. You will start with a blank canvas and own the foundational decisions that shape the product for years to come: architecture, technology choices, design patterns, development standards, release processes, observability, and quality. You won’t be maintaining someone else’s decisions or modernizing a legacy codebase. You’ll define what excellent Android engineering looks like at Rogo. You’ll work directly with product, design, engineering, and customers to translate Rogo’s AI platform into an exceptional native mobile experience. You’ll decide how sophisticated, AI-powered financial workflows should work on Android and then build them. This is a rare opportunity to create a category-defining application from its first line of code, ship it to demanding professional users, and build the foundation for an Android engineering team around your work."
Combine into one maybe two
? The instruction says use
for prose. Could have multiple
elements. We'll separate into two
for readability.
Now Responsibilities list items:
- Build and launch the first version of Rogo’s native Android application
- Define the application’s architecture, technical stack, and core engineering patterns
- Establish the standards for testing, security, performance, observability, releases, and code quality
- Partner closely with product and design to define how AI-native workflows should work on mobile
- Own major features end-to-end, from early user research and technical design through launch and iteration
- Create smooth, stable, and responsive experiences across the Android device ecosystem
- Integrate Rogo’s AI platform and backend services into an intuitive native experience
- Develop reusable foundations that allow the application and future Android team to scale
- Work directly with customers and Customer Success to understand professional workflows and rapidly incorporate feedback
- Help hire, mentor, and set the technical bar for future Android engineers
Now Requirements list:
- 5+ years of professional Android development experience
- A track record of building and launching high-quality Android applications
- Strong command of Kotlin, Jetpack Compose, and the Android SDK
- Experience making foundational architecture and technology decisions
- Deep understanding of Android application architecture, lifecycle management, and platform conventions
- Experience with Kotlin coroutines, Flow, concurrency, threading, and performance optimization
- Strong product judgment and an instinct for polished, intuitive user experiences
- Experience designing reusable, testable components and maintainable application architecture
- High standards for reliability, security, privacy, and production readiness
- Comfort operating with ambiguity and turning an open-ended opportunity into a shipped product
- Passion for building delightful AI-powered experiences
Now Skills (Bonus) list:
- You have built an Android app or major mobile product from zero to one
- You have been an early mobile engineer at a fast-growing startup
- Experience with Java, RxJava, Dagger or Hilt, and established Android architecture patterns
- Experience integrating with backend services through REST APIs, gRPC, WebSockets, or Server-Sent Events
- Experience with offline functionality, local persistence, background processing, and push notifications
- Experience deploying Android applications in an enterprise context, including managed Google Play, Microsoft Intune, or mobile-device-management environments
- Experience building secure applications that handle sensitive enterprise data
- Background at a design-forward product company such as Notion or Figma
- Strong interest in AI and how it can reshape professional mobile workflows
Now Benefits list (Why Join Rogo?):
- Up and to the right: Rogo has strong product adoption with the world's leading financial institutions, and we are still early. The upside is enormous.
- Extraordinary team: we take talent density seriously. You'll do the best work of your career alongside some of the sharpest people in AI and finance.
- A one-of-one problem: bringing AI to the core of how Wall Street works is one of the most ambitious, technically demanding, and consequential problems today. There is nowhere else you can work on it at this scale.
- Real ownership: You'll own real surface area and watch the world's most sophisticated users rely on your work.
- Always at the frontier: we work at the edge of what the best models can do and turn it into products people trust. If you're obsessed with AI, this is where it's happening.
Now produce HTML.
We'll output:
About the role
Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want
for prose. We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We need to not repeat job title as heading. Not include Job ID. We need to output only HTML fragment. Let's parse content: "Why Rogo" paragraph: mission description. Could go under About the role? Or maybe we treat as About the role (company overview). We'll put
About the role
thenwith that paragraph. "The Role": description of role. Could be part of About the role? But we already used About the role for company. Maybe better: Use About the role for role description? Actually "About the role" typical heading for role description. The "Why Rogo" is company mission. Could be separate section like "About the company". But not in list. However we can still use
About the role
for role description, and maybe include company mission in a precedingbefore that? But we need to preserve all info. Could combine: first
company mission, then
About the role
then role description. But the instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should use those headings where appropriate. So we can have:
About the role
(role description)
Responsibilities
(What You’ll Own)
Requirements
(What You’ll Need)
Skills
maybe from Bonus? Or we could incorporate Bonus into Requirements or Skills. But we need to avoid thin sections. Could combine Requirements and Skills into one? But they said prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits. Skills could be part of Requirements. Bonus could be part of Requirements as "Preferred qualifications". But we need to preserve all detail; we can include Bonus as a under Requirements with heading "Preferred qualifications"? But we cannot create new headings not in list? 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 they gave examples. Safer to stick to those headings. We can map Bonus to Skills (preferred skills). So we can have Skills section for bonus items.
Qualifications maybe same as Requirements; we could omit Qualifications to avoid duplication.
Thus sections:
- About the role (company mission + role overview? Actually role overview is in The Role paragraph; we could put that in About the role.)
- Responsibilities (What You’ll Own)
- Requirements (What You’ll Need)
- Skills (Bonus)
- Benefits (Why Join Rogo?)
Check each for substantive content.
Now we need to format lists.
Let's extract content.
About the role: combine "Why Rogo" paragraph and "The Role" paragraph (first paragraph of The Role? Actually The Role includes multiple paragraphs: "We’re looking for a Lead Android Engineer...". That's role description. We'll include that as prose.
So About the role
will contain both mission and role description? Might be long but okay.
Responsibilities: "What You’ll Own" bullet list. We'll turn each line into
- .
Requirements: "What You’ll Need" bullet list. We'll turn each line into
- .
Skills: "Bonus" bullet list. We'll turn each line into
- .
Benefits: "Why Join Rogo?" bullet list? Actually it's a few paragraphs with bold headings: Up and to the right..., Extraordinary team..., A one-of-one problem..., Real ownership..., Always at the frontier... We'll treat each as
- .
Now ensure we don't include filler like "commensurate with experience". Not present.
Now produce HTML.
We need to wrap each section:
About the role
...
then Responsibilities
- ...
etc.
Make sure to not include extra blank lines? It's fine.
Let's craft the prose.
About the role prose:
Combine:
"Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want to help build the future of finance, we invite you to join us."
Then The Role paragraph:
"We’re looking for a Lead Android Engineer to build Rogo’s Android app from the ground up. Rogo is not available on Android app yet. You will start with a blank canvas and own the foundational decisions that shape the product for years to come: architecture, technology choices, design patterns, development standards, release processes, observability, and quality. You won’t be maintaining someone else’s decisions or modernizing a legacy codebase. You’ll define what excellent Android engineering looks like at Rogo. You’ll work directly with product, design, engineering, and customers to translate Rogo’s AI platform into an exceptional native mobile experience. You’ll decide how sophisticated, AI-powered financial workflows should work on Android and then build them. This is a rare opportunity to create a category-defining application from its first line of code, ship it to demanding professional users, and build the foundation for an Android engineering team around your work."
Combine into one maybe two
? The instruction says use
for prose. Could have multiple
elements. We'll separate into two
for readability.
Now Responsibilities list items:
- Build and launch the first version of Rogo’s native Android application
- Define the application’s architecture, technical stack, and core engineering patterns
- Establish the standards for testing, security, performance, observability, releases, and code quality
- Partner closely with product and design to define how AI-native workflows should work on mobile
- Own major features end-to-end, from early user research and technical design through launch and iteration
- Create smooth, stable, and responsive experiences across the Android device ecosystem
- Integrate Rogo’s AI platform and backend services into an intuitive native experience
- Develop reusable foundations that allow the application and future Android team to scale
- Work directly with customers and Customer Success to understand professional workflows and rapidly incorporate feedback
- Help hire, mentor, and set the technical bar for future Android engineers
Now Requirements list:
- 5+ years of professional Android development experience
- A track record of building and launching high-quality Android applications
- Strong command of Kotlin, Jetpack Compose, and the Android SDK
- Experience making foundational architecture and technology decisions
- Deep understanding of Android application architecture, lifecycle management, and platform conventions
- Experience with Kotlin coroutines, Flow, concurrency, threading, and performance optimization
- Strong product judgment and an instinct for polished, intuitive user experiences
- Experience designing reusable, testable components and maintainable application architecture
- High standards for reliability, security, privacy, and production readiness
- Comfort operating with ambiguity and turning an open-ended opportunity into a shipped product
- Passion for building delightful AI-powered experiences
Now Skills (Bonus) list:
- You have built an Android app or major mobile product from zero to one
- You have been an early mobile engineer at a fast-growing startup
- Experience with Java, RxJava, Dagger or Hilt, and established Android architecture patterns
- Experience integrating with backend services through REST APIs, gRPC, WebSockets, or Server-Sent Events
- Experience with offline functionality, local persistence, background processing, and push notifications
- Experience deploying Android applications in an enterprise context, including managed Google Play, Microsoft Intune, or mobile-device-management environments
- Experience building secure applications that handle sensitive enterprise data
- Background at a design-forward product company such as Notion or Figma
- Strong interest in AI and how it can reshape professional mobile workflows
Now Benefits list (Why Join Rogo?):
- Up and to the right: Rogo has strong product adoption with the world's leading financial institutions, and we are still early. The upside is enormous.
- Extraordinary team: we take talent density seriously. You'll do the best work of your career alongside some of the sharpest people in AI and finance.
- A one-of-one problem: bringing AI to the core of how Wall Street works is one of the most ambitious, technically demanding, and consequential problems today. There is nowhere else you can work on it at this scale.
- Real ownership: You'll own real surface area and watch the world's most sophisticated users rely on your work.
- Always at the frontier: we work at the edge of what the best models can do and turn it into products people trust. If you're obsessed with AI, this is where it's happening.
Now produce HTML.
We'll output:
About the role
Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but they gave examples. Safer to stick to those headings. We can map Bonus to Skills (preferred skills). So we can have Skills section for bonus items. Qualifications maybe same as Requirements; we could omit Qualifications to avoid duplication. Thus sections: - About the role (company mission + role overview? Actually role overview is in The Role paragraph; we could put that in About the role.) - Responsibilities (What You’ll Own) - Requirements (What You’ll Need) - Skills (Bonus) - Benefits (Why Join Rogo?) Check each for substantive content. Now we need to format lists. Let's extract content. About the role: combine "Why Rogo" paragraph and "The Role" paragraph (first paragraph of The Role? Actually The Role includes multiple paragraphs: "We’re looking for a Lead Android Engineer...". That's role description. We'll include that as prose. So About the role
will contain both mission and role description? Might be long but okay. Responsibilities: "What You’ll Own" bullet list. We'll turn each line into
About the role
...
thenResponsibilities
- ...
maybe two
? The instruction says use
for prose. Could have multiple
elements. We'll separate into two
for readability. Now Responsibilities list items: - Build and launch the first version of Rogo’s native Android application - Define the application’s architecture, technical stack, and core engineering patterns - Establish the standards for testing, security, performance, observability, releases, and code quality - Partner closely with product and design to define how AI-native workflows should work on mobile - Own major features end-to-end, from early user research and technical design through launch and iteration - Create smooth, stable, and responsive experiences across the Android device ecosystem - Integrate Rogo’s AI platform and backend services into an intuitive native experience - Develop reusable foundations that allow the application and future Android team to scale - Work directly with customers and Customer Success to understand professional workflows and rapidly incorporate feedback - Help hire, mentor, and set the technical bar for future Android engineers Now Requirements list: - 5+ years of professional Android development experience - A track record of building and launching high-quality Android applications - Strong command of Kotlin, Jetpack Compose, and the Android SDK - Experience making foundational architecture and technology decisions - Deep understanding of Android application architecture, lifecycle management, and platform conventions - Experience with Kotlin coroutines, Flow, concurrency, threading, and performance optimization - Strong product judgment and an instinct for polished, intuitive user experiences - Experience designing reusable, testable components and maintainable application architecture - High standards for reliability, security, privacy, and production readiness - Comfort operating with ambiguity and turning an open-ended opportunity into a shipped product - Passion for building delightful AI-powered experiences Now Skills (Bonus) list: - You have built an Android app or major mobile product from zero to one - You have been an early mobile engineer at a fast-growing startup - Experience with Java, RxJava, Dagger or Hilt, and established Android architecture patterns - Experience integrating with backend services through REST APIs, gRPC, WebSockets, or Server-Sent Events - Experience with offline functionality, local persistence, background processing, and push notifications - Experience deploying Android applications in an enterprise context, including managed Google Play, Microsoft Intune, or mobile-device-management environments - Experience building secure applications that handle sensitive enterprise data - Background at a design-forward product company such as Notion or Figma - Strong interest in AI and how it can reshape professional mobile workflows Now Benefits list (Why Join Rogo?): - Up and to the right: Rogo has strong product adoption with the world's leading financial institutions, and we are still early. The upside is enormous. - Extraordinary team: we take talent density seriously. You'll do the best work of your career alongside some of the sharpest people in AI and finance. - A one-of-one problem: bringing AI to the core of how Wall Street works is one of the most ambitious, technically demanding, and consequential problems today. There is nowhere else you can work on it at this scale. - Real ownership: You'll own real surface area and watch the world's most sophisticated users rely on your work. - Always at the frontier: we work at the edge of what the best models can do and turn it into products people trust. If you're obsessed with AI, this is where it's happening. Now produce HTML. We'll output:
About the role
Why Rogo Our mission is to transform global finance by empowering professionals at the world's top investment banks, private equity funds, and investment firms with AI that delivers unparalleled speed, accuracy, and insight. We're not just improving financial workflows; we're redefining them. This is a unique opportunity to join a generational company driving transformation in one of the most important industries in the world. With a rapidly growing, global client base, proven product-market fit, and backing from world-class investors, we are scaling quickly and defining a new category of enterprise AI. Our team is sharp, motivated, and deeply committed to Rogo’s mission. We take ownership of complex problems and stay relentlessly focused on our users. If you thrive in a fast-paced environment, demand excellence, and want