Staff Product Manager, Identity Platform

Vanta · Enterprise · U.S. · Remote · Product Management

Staff Product Manager for Vanta's Identity Platform, focusing on authentication, authorization, and user modeling for a diverse customer base from startups to federal agencies. This role shapes how permissions scale as Vanta expands into enterprise and government markets, requiring deep collaboration across teams and a systems-thinking approach to complex platform problems.

What you'd actually do

  1. Own the IAM product vision and roadmap, setting direction for authentication, authorization, user modeling, and ownership frameworks in close partnership with engineering leadership
  2. Drive the User Model split to completion — separating IAM Users (auth/permissions) from Personnel Records (GRC/compliance) in a complex, cross-team data migration with org-wide impact
  3. Define Ownership 3.0 — chart the path from binary object-level ownership to customer-customizable, role-based permissions that serve both startups and large enterprises
  4. Shape Vanta's authorization strategy proactively, ensuring product teams build on shared platform capabilities rather than ad hoc permission solutions
  5. Contribute to multi-tenant access architecture, enabling seamless cross-domain experiences for auditors, MSPs, and multi-workspace enterprise customers

Skills

Required

  • 8-12+ years of product management experience
  • at least 3-4 years at a Staff/Senior level in platform or infrastructure roles
  • Enterprise platform PM experience: you've worked on permissions, RBAC, multi-tenancy, or identity systems at scale in B2B SaaS
  • Systems thinking: you can reason about how authentication, authorization, and identity interconnect and affect every product surface — and explain it simply
  • Strong cross-functional collaboration: this role touches every team at Vanta and requires building consensus across Product, Engineering, Design, and GTM
  • Storytelling for technical concepts: you can explain why an authorization architecture decision matters to non-technical stakeholders and translate complex IAM concepts into clear business value
  • Customer empathy at multiple scales: you understand that a 10-person startup and a federal agency have vastly different permission needs, and can design systems that serve both
  • Comfort with ambiguity: you've navigated complex platform problems with many open design questions and competing stakeholder needs

Nice to have

  • Experience with policy engines (Oso, OPA, Cedar) or authorization architecture patterns
  • Background in GRC, compliance, or security-adjacent products
  • Familiarity with multi-tenant SaaS architectures

What the JD emphasized

  • Enterprise platform PM experience
  • Enterprise complexity
  • enterprise and government markets
  • federal agencies