Senior Product Manager, Platform - Magnet One

Role Overview

Magnet One is the connective layer across our product portfolio, and the platform team builds the foundations every other team depends on: how customer organizations are structured, how users prove who they are, how purchases turn into working access, and how our own teams support all of it.

Our customers are getting larger and structurally more complex - bigger agencies, federated deployments, stricter identity and data residency requirements - and the foundational decisions ahead deserve dedicated ownership rather than being made a ticket at a time. That's the role: one person who owns this domain end to end and gives it a deliberate direction.

This is a builder's role with an unusually direct line to customer pain. Our administrators are IT and operations staff at law enforcement agencies, government labs, and enterprises - people who work under strict security policies, have limited tolerance for surprises, and often manage access for dozens or hundreds of investigators. Getting their experience right is a competitive advantage. Getting it wrong shows up as support tickets, stalled deployments, and renewals at risk.

What You'll Do

You'll be the product owner for five connected areas, listed in the order we expect you to take them on.

1. Account-level administration (the immediate priority) The way customer organizations are modeled and managed in Magnet One: org and sub-org structure, user lifecycle, roles and permissions, seat and entitlement visibility, delegated administration for large or federated agencies, and the audit trails their security teams require. You'll own the permissions model itself - what roles exist, what they can do, and how that scales as customers get larger and more complex.

2. Identity and access Single sign-on (SAML/OIDC), directory-driven provisioning and deprovisioning (SCIM), multi-factor and session policy, service accounts and API credentials, and the migration path for customers on older authentication paths. Much of this is table stakes in enterprise procurement, and gaps here surface early in security reviews.

3. Order fulfillment The path from a closed deal to a customer with working access. Entitlement provisioning, renewals and co-termination, trials, and the handoffs between our commercial systems and the platform. Your goal is to shorten time-to-access and eliminate the manual intervention this process requires today.

4. Deployment site and regional footprint Where customer data lives and how we decide to expand. You'll own the logic for placing a customer in the right region at provisioning time, the constraints that drive that choice - data residency and sovereignty rules, agency policy, latency, regional service availability - and the analysis behind opening new regions. That means building the business case: which deals are blocked today by the absence of a region, what demand justifies the cost of standing one up, and what the sequencing should be. You'll also own how region is surfaced to customers and to sales, and what happens when a customer needs to move.

5. Internal tooling The consoles our support, customer success, and operations teams use to administer accounts, resolve entitlement issues, and assist customers safely - with the auditability that assisting a customer's account demands.

Across all five, you will:

• Work directly with three or more engineering teams and their architects, in their language, on their design decisions.
• Talk to customer administrators regularly and bring their reality back into the roadmap.
• Sequence work across teams and make the tradeoff calls when platform investment competes with feature delivery.
• Define what "good" looks like - provisioning success rates, time-to-first-login, admin task completion, support ticket volume by cause, deals unblocked by region availability - and hold the team to it.
• Build and defend investment cases with quantitative analysis, particularly for regional expansion, where the cost is real and the demand signal is scattered across the pipeline.
• Partner with sales engineering, security, support, revenue operations, and infrastructure, who all depend on these systems.

What year one looks like:

First 90 days. You've built a clear picture of the current account administration and permissions model, including where it breaks. You've talked to at least a dozen customer administrators and internal stakeholders. You've published a prioritized problem inventory the engineering teams agree with.

By six months. There's an agreed target model for organizations, roles, and permissions, and work is underway against it. Identity roadmap commitments are defined with dates you can defend in a customer conversation.

By twelve months. Customer administrators can complete the core set of tasks without contacting support. Order fulfillment requires materially less manual intervention. Your engineering teams and your commercial stakeholders both know what's coming next and why.

What We’re Looking For

• Roughly 4-6 years in product management, focused on platform, infrastructure, or B2B administrative capabilities rather than end-user features.
• A hands-on engineering background earlier in your career. You read code and API contracts comfortably, and you can hold your own in an architecture discussion without a translator.
• Direct experience with at least one of: identity and access management, multi-tenant account or organization modeling, permissions and authorization systems, or billing and entitlement provisioning.
• Enterprise or B2B SaaS experience, including exposure to how security reviews and procurement shape what you can ship.
• Analytical rigor. You can pull pipeline and usage data, size an opportunity, and put a defensible number in front of a leadership team - regional expansion decisions in particular are made on evidence, not instinct.
• Demonstrated autonomy. You'll be trusted to run this domain, escalate the right things, and make defensible calls on the rest.
• Strong written communication. Platform decisions are consumed by teams who weren't in the room, and writing is how this role scales.
• Comfort working with customers whose environments are locked down, whose change windows are narrow, and who may be several steps removed from you organizationally.

Nice to Have Skills

• Experience introducing SSO or SCIM to a product that didn't have it, including customer migration.
• Experience with data residency, sovereignty, or multi-region deployment decisions.
• Experience serving public sector, regulated, or highly security-conscious customers.
• Having built internal tooling for support and operations teams.
• Experience being the first PM on a platform team.