Senior Software Engineer II, Mobile - Revenue Experimentation (AI Native)

Life360 is a remote-first company building mobile products and services that help people protect and stay connected with the people, pets, and things they care about. The Senior Software Engineer II will design, build, instrument, and analyze Android growth and monetization experiments while advancing AI-native engineering workflows and practices across the mobile organization.

Responsibilities:

• Design and build high-quality Android growth and monetization features and experiments — subscription paywalls and pricing tests, ad placement and mediation experiments, one-time purchase (IAP) flows, and upsell/upgrade surfaces — running dozens of concurrent tests across the Life360 app
• Partner with product, design, data science, and analytics to translate hypotheses into shippable experiments, and turn results into the next decision — pushing back when a hypothesis or plan doesn't hold up
• Work with AI (Claude Code or equivalent) as a first-class collaborator — your primary workflow involves orchestrating agents to create specs, generate code and tests, verify results, and perform reviews
• Instrument experiments accurately — exposure logging and analytics — so the results downstream teams rely on are trustworthy
• Ship polished, performant, reliable Android experiences to tens of millions of users, with strong attention to startup time, memory, battery, ANR, and crash-free rates
• Take ambiguous or partially-specced ideas and get a working version in front of real users fast — treating the first cut as a learning tool, not a final answer
• Help define and codify AI-native Android engineering practices for the team, establishing playbooks the broader mobile org can adopt
• Contribute to architectural decisions, code reviews, and a culture of craft and continuous improvement on the Android codebase
• Participate in on-call rotation and incident response for mobile experiments and releases
• Mentor other engineers and contribute to team processes, technical standards, and the evolution of the team's AI-native engineering practices

Requirements:

• 6+ years of Android software engineering experience shipping production apps at consumer scale
• At least 1 year of hands-on experience prompting, evaluating, and building with LLMs
• Strong proficiency with Kotlin and Jetpack Compose (and the Android View system); deep familiarity with the modern Android toolchain (Android Studio, Kotlin Coroutines, Flow)
• Experience with Android architecture patterns (MVVM, MVI, Clean Architecture, Jetpack/ViewModel/Navigation, Hilt or Dagger) in a large, multi-team codebase
• Comfort with mobile experimentation concepts: feature flagging, A/B testing, exposure logging, holdouts, and guardrail metrics
• Solid grounding in mobile performance, memory, battery, ANR, and crash diagnostics (Android Studio Profiler, Perfetto/Systrace, Macrobenchmark, Crashlytics or equivalent)
• Experience with CI/CD for Android (Gradle, Fastlane, GitHub Actions, Bitrise, or similar) and modular build systems
• Deep experience with agentic workflows, prompt engineering, context-window management, and MCP/function calling — you understand the research-plan-implement cycle but don't outsource thinking to agents
• Bachelor's degree in a technical field, or equivalent experience
• Agency — You don't wait to be told what to do. Given a rough hypothesis or a half-finished doc, you can get a working version in front of users without needing a fully-specced ticket first, and you take responsibility for the outcome, not just the task
• Ownership mentality — You own your work from design through production and beyond, including what happens when the experiment doesn't go as planned
• Taste and craft — You have opinions about what a good experiment, a good rollout, and a good user experience look like, and you can articulate why — not just execute a spec
• Growth mindset — You structure problems precisely, learn quickly, show interest outside "your lane," and are always happy to try something new
• AI-native working style — You use AI tooling (Claude Code or equivalent) as a genuine development partner: delegating discrete tasks, reviewing outputs critically, and running parallel workstreams rather than hand-holding one agent at a time
• Collaborative approach — You communicate clearly, work well across teams, and value diverse perspectives; you give and take feedback well
• Experience working with an experimentation platform (Statsig, LaunchDarkly, Optimizely, Eppo, GrowthBook, or similar)
• Background in mobile analytics pipelines (Amplitude, Segment, Snowflake/Databricks downstream)
• Familiarity with Bayesian or sequential testing methods and how they affect client-side implementation
• Previous work on subscription, paywall, pricing, or onboarding surfaces at consumer scale
• Deep in at least one of Kotlin/Android, Swift, or React, and comfortable shipping in another
• Contributions to mobile open source or internal developer tooling