Life360 - Product Builder, Orchestration

• Systems depth • Systems • You've built—or redesigned—a personalization or content orchestration system before, not just shipped features on top of one. You understand ML-driven content ranking, modular UI architecture, and what it means to replace fixed placement logic with algorithmic decisioning. You can talk fluently about signals, weights, feedback loops, and what "good" looks like when you can't directly observe every individual decision the system makes. • Organizational muscle • You've worked on a surface that had become a resource allocation problem and helped fix it. You know what it feels like when a stakeholder tells you their campaign needs the top slot because of a deal they've struck—and you know how to move that conversation from ownership to user value without losing the relationship. You help build shared mental models before the team builds systems. Alignment doesn't happen in one meeting, and you don't expect it to. • AI-native — hard requirement • Life360 is an AI-native company. That means entire workflows managed by semi-autonomous systems, with humans setting direction and intervening at the decision points that require judgment. This role operates in that model—not as an aspiration, but as a baseline. • You direct AI-driven execution across the full product development lifecycle. Research synthesis, spec drafting, experiment analysis, and status reporting run autonomously. Your time goes to strategy, user insight, stakeholder alignment, and building the reusable workflows that compound over time. You're comfortable operating across functional boundaries, think in outcomes, and treat every successful AI workflow as infrastructure for the next one. • Vision instinct • Vision • You don't just execute a roadmap—you have a point of view on where this is going. You can hold the technical detail of content ingestion architecture in one hand and a magical end user experience in the other, and make decisions that serve both. You've driven at least one initiative per year that produced material, company-level impact—not a 2% lift, but a result that changed the shape of a core metric. • What Success Looks Like • 3 months • A shared mental model of the Orchestrator—what it is, what it optimizes for, what it isn't—is established across partner teams company-wide. That includes alignment on the measurement framework: the north star metric, driver metrics, and how the objective function can evolve as business context changes. This clarity is the foundation for both the organization and the systems to optimize for the same outcomes. The first modular content layer is in production, with server-side configurability enabling audience-targeted experiences on at least one core surface. • 6 months • The Orchestrator is a functioning system with measurable lift in L5+ engagement and action rate on delivered content. Content from multiple upstream teams flows through a unified ingestion model. The feedback loop to the Composer lifecycle layer is operational and actively improving decisioning. • 1 year • No two members see the same Life360. The Orchestrator is the platform layer that makes Family AI real at the interface level—assembling a contextually relevant experience for every member, every session, without anyone having to navigate to find it.