Staff Android Engineer (Founding)

We need to output HTML fragment with sections for About the role? Actually the posting includes "About Us", "The Opportunity", "What You'll Be Doing", "You'll Be a Good Fit If", "Bonus", "Employment Type: Full Time, Exempt Base Compensation: ..." etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we must only include sections when posting has real specific content. We need to map content to these headings. We have: - About Us (company description) could map to "About the role"? Actually "About the role" is about the role, not company. But we have "The Opportunity" describing role. Could use "About the role" heading for that. - Responsibilities: "What You'll Be Doing" list. - Requirements/Qualifications/Skills: "You'll Be a Good Fit If You" list (requirements). Also "Bonus" could be extra qualifications/skills. - Benefits: list under "Full Time Employee Benefits". - Pay: compensation range. - Schedule: hybrid role expectation (onsite three days per week, travel 2-3 times per year). That's schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, application instructions, etc. Also remove "Research shows that some groups hesitate..." etc. Also remove "Employment Type: Full Time, Exempt" maybe we can incorporate into schedule? Actually employment type is full time; we could include in schedule or maybe not needed. But we can include schedule section with hybrid expectation. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like compensation range, benefits list, responsibilities list, requirements list, bonus list, schedule details. We need to output only HTML fragment, no /, no markdown fences. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We must not create sections with filler like "commensurate with experience". We have actual content. Let's structure:

  About the role

  ... content from "The Opportunity" paragraph(s) describing role, Staff role, end-to-end ownership, etc.

  Responsibilities

  • Design the architecture and technical foundations for Grow's native Android app, from project structure and state management through build, testing, and release infrastructure.
  • Ship consumer-facing features on that foundation, building the experiences that help clients discover care, connect with providers, and manage their care journey between sessions.
  • Set coding standards, tooling, and engineering practices for Android, and evolve them as the team grows around you.
  • Own the path to production: CI/CD, Google Play release management, observability, and the quality and security practices a healthcare app requires.
  • Partner closely with product, design, and the iOS and backend teams to connect technical decisions to product goals, and product goals back to technical tradeoffs.
  • Drive cross-functional decisions and represent Android's roadmap and tradeoffs to stakeholders across the company, often without a precedent to point to.

  Requirements

  • 8+ years of software engineering experience, the majority in native Android development with Kotlin, spanning both platform/architecture work and consumer-facing feature development.
  • Led the technical direction for an Android app or platform from an early or 0-to-1 stage, or through a major re-architecture: chose the architecture, stood up the tooling, shipped to production, and comfortable making those calls with incomplete information and no established playbook.
  • Production depth in modern Android: Jetpack Compose, Kotlin coroutines and Flow, dependency injection, modularization, and Gradle build tooling, and a considered testing strategy.
  • Strong product instincts and a genuine ability to partner with product and design, connecting technical decisions to what users actually experience.
  • Use AI development tools (e.g., Cursor, Claude Code, GitHub Copilot) as a core part of how you build, and have grounded opinions on where they help and where they don't.

  Preferred Qualifications

  maybe "Bonus" as preferred qualifications. Use heading "Preferred Qualifications" or "Bonus". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't list "Preferred Qualifications" but we can use "Qualifications" for bonus? Actually we have Requirements and Qualifications separate. Could treat "Bonus" as "Preferred Qualifications". We'll use

  Qualifications

  for bonus list.

  Qualifications

  • Personal connection to mental health care or a strong pull toward Grow's mission.
  • Considered view on Kotlin Multiplatform and shared-code strategies, grounded in something you've shipped or evaluated.
  • Built mobile apps in a regulated or healthcare setting, with real attention to sensitive data and accessibility.
  • Helped uplevel an Android team around you through hiring, mentoring, and standards others adopted.

  Benefits

  • Comprehensive medical, dental, vision, life, and disability coverage.
  • Grow for Grow: No cost access to therapy through the Grow platform (available to US employees)
  • Financial Wellness: Retirement savings programs and equity opportunities to help you invest in your future.
  • Flexible Time Off, Paid Holidays & Winter Break: Flexible time off, company paid holidays (which vary by country), and a full company wide Winter Break to rest and recharge
  • Parental Leave: Up to 18 weeks of paid parental leave to support you and your growing family and a new child stipend.
  • Mental Health Mornings/Afternoons: Dedicated weekly flexible time for self care, whether that's therapy, exercise, journaling, time with family, or simply taking a break.
  • Wellness & Development Stipend: Annual stipend to support your personal wellbeing and professional growth, from fitness and education to books and learning resources.
  • Commuter Benefits: Pre tax commuter benefits to support teammates working from one of our hub locations.
  • Home Office & Meals: Support for your home workspace plus meal benefits, with offerings tailored to both remote and hub based employees.
  • Additional Perks: A variety of wellbeing benefits, including wellness memberships, virtual care, pet insurance discounts (where available), and global travel assistance.

  Pay

  The base compensation range for this position is $217,000–$289,000 USD annually. Base compensation will vary depending on relevant experience, qualifications, and the candidate's working location.

  Schedule

  This is a hybrid role with the expectation to work onsite from one of our office locations - San Francisco, Seattle, New York, and Waterloo - three days per week (Tuesday, Wednesday, and Thursday) and travel 2–3 times per year (e.g., company and department offsites).

  We also need to include About the role prose from "The Opportunity". Let's craft that paragraph: "The Opportunity Grow Therapy's iOS app launched earlier this year, and mobile is now a core part of how clients find care, connect with their providers, and stay engaged between sessions. Android is next, and we're hiring our founding Android engineer to build it. This is a Staff role with end-to-end ownership. You will set the technical direction for Android from day one: the architecture, the developer experience, the first production release, and the systems every future Android engineer will build on. Android at Grow is greenfield, but you won't be starting from zero. A shipped iOS app, a shared backend, and an established design system give you a proven product and platform to build from. You'll report to our Director of Engineering for the Momentum pillar and work alongside the iOS, product, and design partners who built the first app. This is a hands-on role in an AI-forward engineering organization. We expect the person in this seat to make deliberate architectural calls with incomplete information, ship the first release, and set the standards a growing Android team inherits." We should preserve all that. No fluff. Now ensure we didn't include any boilerplate like EEO, legal, application instructions, etc. We removed those. Check for any leftover like "Research shows that some groups hesitate..." removed. Also removed "Employment Type: Full Time, Exempt" maybe we could mention full time in schedule? Not needed. The schedule section already mentions hybrid role; we could add "Full-time" but not required. The instruction says include schedule only if posting states it; we have schedule details. It didn't explicitly say full-time but we could add "Full-time" as part of schedule? Might be extra but not invented. It's in the posting: "Employment Type: Full Time, Exempt". That's substantive. We could incorporate into schedule paragraph: "This is a full-time, hybrid role..." Let's do that to preserve that detail. Thus schedule paragraph: "This is a full-time hybrid role with the expectation to work onsite from one of our office locations - San Francisco, Seattle, New York, and Waterloo - three days per week (Tuesday, Wednesday, and Thursday) and travel 2–3 times per year (e.g., company and department offsites)." Now check that we didn't miss any substantive info: "About Us" paragraph about company mission, funding, etc. Should we include that? The instruction says we should include About the role section, not About Us. But About Us is company description; maybe we could include under About the role? The instruction says use headings like About the role, Responsibilities, etc. It didn't forbid including company description elsewhere, but we should preserve all substantive information. Where to put About Us? Could be part of About the role? Might be better to include a brief paragraph under About the role that includes company mission? However the About Us is separate from role. 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 headings. However we must preserve all substantive information. The About Us paragraph is substantive. We could include it as a paragraph under About the role heading, or we could add another heading like "About Grow" but that's not in the list. Safer to incorporate it into About the role paragraph, as it's still about the role context. The instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid adding extra headings beyond the list, but says "Prefer a few substantive sections over many thin ones." So we could add an "About Grow" section but that would be thin? It's a paragraph. Might be okay but better to stick to given headings. We'll merge About Us into About the role paragraph. Thus About the role paragraph will include both the opportunity description and company mission/funding etc. Let's craft: "Grow was born to tackle a critical challenge: making mental health care more effective and accessible for everyone. Since launching in 2020, 15 million sessions have started on Grow, and we've barely scratched the surface. We do it through a three-sided marketplace that empowers providers, augments insurance payors, and serves patients. Every solution we build reveals ten more waiting to be delivered, and that's just what gets us going. We've backed that ambition with more than $328M in funding, including our Series D at a $3B valuation from