Senior GRC Engineer, Life360

• 5+ years in GRC, security engineering, or a hybrid role where you owned both the policy and control side and the technical implementation — not one or the other
• You build with AI tools, not just use them. You've used LLMs and agents in real work — drafting, code, automation, investigation — and can make judgment calls about where AI creates leverage and where it introduces risk. Experience designing or operating agentic workflows is a strong signal
• Coding ability that ships. Python or equivalent — you can call APIs, build integrations, schedule jobs, and deploy a working pipeline without help. Show us something you built
• You can evidence controls directly in cloud environments — identity, audit logs, configuration posture, secrets management — without relying on screenshots or system owners. You pull evidence from APIs
• You've implemented, integrated, or significantly extended a modern GRC platform. You know what these platforms actually solve, where they fall short, and when to write your own code instead
• SOC 2, ISO 27001, and NIST AI RMF at the control level, not just the headers. You understand how these frameworks are evolving to account for AI and agentic systems
• You've worked through SOX ITGC cycles at a public company — managing evidence, walkthroughs, and findings with external auditors
• Built or scaled a TPRM program — you've designed tiering, pushed back on bad vendors, and automated parts of the assessment workflow
• Quantitative risk experience — you've owned a risk register and made it useful to engineers and executives. FAIR or equivalent methodology in real use is a strong signal
• Clear writing — policies, control narratives, audit responses, and risk statements that engineers and lawyers both understand
• Bachelor's degree or equivalent
• We encourage people of all backgrounds to apply. We believe that a diversity of perspectives and experiences create a foundation for the best ideas. Come join us in building something meaningful. Even if you don’t meet 100% of the below qualifications, you should still seriously consider applying!

Desirable

• 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 Information Security and Technology team is responsible for keeping Life360 safe — our systems, our employees, and the tens of millions of families who trust us with their location data. That obligation is the starting point. How we meet it is what makes this team different
• We are builders. Security controls that don't get used aren't controls. Compliance programs that create friction without reducing risk aren't programs. We build things that work in production, earn adoption from engineering teams, and get better over time — and we use AI to do it at a scale a traditional team couldn't
• We're also at an inflection point. Life360 is deploying agentic systems into how we build and operate, and the security and governance implications of that are still being worked out — by us, and by the industry. The threat surface is expanding. The compliance frameworks are catching up. The people on this team aren't waiting for either
• Governance, Risk, and Compliance (GRC) has been on a slow progression from audit binders and manual evidence collection toward policy as code, continuous control testing, and compliance infrastructure that generates its own proof. We're hiring someone already living at that frontier — and ready to push past it
• Life360 is mid-transformation into an AI-native company, which means this role has two jobs running in parallel. The first is building the technical foundation of a modern GRC program: policies version-controlled in Git, controls that self-test, evidence generated by integrations rather than collected by humans, and a TPRM program that reflects how we actually use third parties. SOC 2, ISO 27001, and SOX anchor this work
• The second job is harder and less charted. As Life360 deploys agentic systems into how we build and operate, the policy and control landscape is shifting in real time. Major frameworks are actively working out how to account for autonomous agents, and new control sets are emerging faster than the regulations that require them. You'll anticipate new policy requirements, adapt existing controls, and ensure our governance architecture is ready before the auditors ask
• Own the governance framework for Life360's agentic systems. The major compliance frameworks are still figuring out how to account for autonomous agents. Define the policies, control sets, and compliance posture that govern how agents are built and deployed at Life360 — and build ahead of the regulation
• Take an agentic approach to GRC itself. Automate evidence collection, draft control narratives, triage vendor questionnaires — use AI and internal tooling to do the work humans shouldn't be doing manually. Write the integrations and pipelines that make it real. Know where AI creates leverage, where it introduces risk, and where a human needs to stay in the loop
• Build the policy program as code. Policies in Git, peer-reviewed via pull request. Requirements expressed as enforceable rules and automated checks, not static PDFs. A common controls framework that satisfies SOC 2, ISO 27001, NIST CSF, and future frameworks from a single control reference — no rework
• Drive SOC 2 Type 2, ISO 27001, and SOX ITGC end-to-end as management owner — managing evidence, coordinating with external assessors, and closing gaps before auditors find them. Build the automation once; satisfy three frameworks. Financial reporting controls beyond ITGC live with Internal Audit; you'll partner closely with them on shared control libraries, evidence pipelines, and walkthroughs. Internal Audit retains independent SOX program ownership, third-line testing, and Audit Committee reporting . The goal is audit readiness as a continuous state, not a quarterly sprint
• Build an operational risk function, not a register. Quantitative-leaning, FAIR-informed, and connected to live data sources across cloud security posture, endpoint detection, vulnerability management, and asset inventory. Risk scoring that reflects current reality and is actionable at every altitude — service owner to board executive leadership, with Audit Committee reporting on enterprise risk coordinated with Internal Audit. Build the data model, workflow layer, and closed loop that turns risk from a prioritization exercise into a lifecycle with owners and treatment decisions
• Mature the TPRM program. Tiered reviews by risk and data sensitivity. Automated evidence collection and agent-based workflows that reduce friction for vendors and internal teams alike — making it easier to do this right than to skip it
• Be the auditor's primary management contact. Own scoping, walkthroughs, evidence delivery, and management responses for SOC 2, ISO 27001, and SOX ITGC. Auditors leave knowing more about how Life360 actually works than they did when they walked in — and findings get closed before they become repeat findings
• Build the cross-functional relationships that make GRC work in practice. Engineering, Legal, Privacy, Internal Audit and Procurement are all load-bearing parts of this program — own those partnerships and build the workflows that make compliance a shared practice, not a security team deliverable
• Maintain clear role boundaries between management’s first- and second-line GRC operations and Internal Audit’s third-line independent assurance