Principal Product Manager, Builder

Life360 is a company dedicated to keeping people connected with their loved ones through innovative technology. The Principal Product Manager will lead the development of the Orchestrator system, a real-time decision-making layer that personalizes user experiences based on various contextual signals and family dynamics.

Responsibilities:

• Orchestrator system design and roadmap. Partnering with engineering, design, and data science to shape the real-time layer that decides what each member sees—per session, per context—based on who they are and what their family is doing right now
• Measurement framework. Working with stakeholders across the business to define and align on the north star metric, driver metrics, and objective function that guide every decisioning tradeoff the Orchestrator makes—and ensuring that framework can evolve as business context changes. This is the shared language that keeps the organization and the system optimizing for the same outcomes
• Content ingestion architecture. Working with partner teams across the company to define how they contribute to the Orchestrator without competing for fixed placements—and helping drive the alignment that makes a shared model stick
• Member context model. Collaborating with data science, engineering, and partner teams to define the signals and profile data that power real-time decisioning: time of day, location context, family state, behavioral history
• Delivery surfaces and content templates. Working within Life360's existing in-app UI patterns to ensure the Orchestrator can deliver content effectively across the surfaces already built—and flagging gaps where new templates or surfaces are needed to unlock the next layer of personalization
• Feedback loops. Contributing to how engagement and display data flows back to upstream systems to improve decisioning over time
• Stakeholder operating model. Helping translate competing team priorities into weighted inputs to a shared system—and serving as an educator and evangelist to partner teams on what the Orchestrator is, what it can do, and how to build with it

Requirements:

• 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
• 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
• 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
• 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