Staff Android Engineer, AI Native (Experiences)
Life360 is seeking a Staff Android Engineer, AI Native, to drive and define Android experiences across various core features like Maps, Realtime, and Notifications. This role involves unifying product experiences, influencing technical and design direction, and pushing AI-native development practices across the Experiences department, working hands-on to unblock challenges and write production code.
Life360’s mission is to keep people close to the ones they love. Our category-leading mobile app, Tile tracking devices, and Pet GPS tracker empower members to protect the people, pets, and things they care about most with a range of services, including location sharing, safe driver reports, and crash detection with emergency dispatch. Life360 serves approximately 97.8 million monthly active users (MAU), as of March 31, 2026, across more than 180 countries.
Life360 delivers peace of mind and enhances everyday family life with seamless coordination for all the moments that matter, big and small. By continuing to innovate and deliver for our customers, we have become a household name and the must-have mobile-based membership for families (and those friends who are basically family).
Life360 has more than 500 (and growing!) remote-first employees. For more information, please visit life360.com/.
Life360 is a Remote-First company, which means a remote work environment will be the primary experience for all employees. All positions, unless otherwise specified, can be performed remotely (within the US) regardless of any specified location above.
We are building an AI native company where AI is an integral part of how we build and operate. AI tool usage during interviews varies by role. You may be asked to demonstrate proficiency with AI tools, discuss how you leverage AI, or complete interview exercises without AI assistance. Your Recruiter will provide clear guidance as you move through the interview process.
Undisclosed use of AI not previously discussed with or approved by your Recruiter may impact your candidacy.
The Experiences Department is responsible for the core member experience that defines how families use Life360 every day. Our teams build the surfaces and systems that answer essential questions like: How is my family right now? How do we stay coordinated and connected? Where has my family been? We create the foundations and interactions that support real-time awareness, history, communication, insights, and everyday family coordination.
Our 2026 focus is to deliver a fast, cohesive, and emotionally resonant free user experience that reflects the company’s long-term Magic of Location vision. We partner closely with Design, Product, and engineering teams across Location Platform, Intelligence, and Cloud to bring this vision to life at scale.
This role reports directly to the Senior Director of Engineering for Experiences and operates horizontally across all teams within Experiences. You will help unify across the department and ensure we build toward a consistent, high-quality vision.
This role sits horizontally across Experiences, not inside one team. The job is making sure what we build across Maps, Realtime, Feed, Notifications, and History actually fits together into something coherent. Right now that's not always the case and it's costing us.
The core product journeys are the focus: where is my family, how do we stay connected, where have we been. These are what 91M monthly users interact with every time they open the app. The technical and experiential decisions made here have real reach.
We need someone who operates as an owner. That means shaping what gets built, not waiting for a spec. Influencing product and design direction, writing the technical framing for how we sequence work, seeing how the pieces add up (or don't). There's a real gap today between individual features shipping and a coherent experience coming out the other side. Closing that is a big part of this job.
Working in an AI-native way is a real expectation here, not a nice-to-have. We're building toward a model where AI owns the development loop and engineers direct and are accountable for what ships. We expect this person to already work that way — directing agents through the full development cycle, writing clear problem statements AI can run against, holding the quality bar on output. If you're using AI to go faster at the same tasks you'd do anyway, that's not the shift we're making.
The role is hands-on. Deep reviews, prototyping, unblocking things stuck in the middle. The leverage isn't in your direct output though — it's in how much the teams around you move because you're involved.
Posted June 2, 2026