Lead Product Manager, Orb

• 7+ years of experience as a Product Manager working on B2B SaaS software
• You have a strong record of delivering impact on customer outcomes and company goals, including defining new products
• You understand the importance of advocating for customer needs while balancing business priorities
• You excel at building strong partnerships with engineering and design counterparts, as well as cross-functional stakeholders
• You apply product discovery and optimization techniques to turn ambiguity into a plan
• You have a demonstrated drive to ship early and often
• Based in the San Francisco Bay Area or willing to relocate (with support from Orb)

Desirable

• We're seeking a Lead Product Manager to define and own Orb's Entitlements & Spend Platform — the runtime layer where billing state becomes something customers can act on in real time: alerting, spend controls, entitlement checks, and usage analytics
• This is where customers come to know what's been consumed, what's allowed, and what should happen next, both as reactive alerts the moment a limit is crossed and as live, on-demand reads of balance and entitlement state
• Because it's computed against Orb's actual pricing, credits, and commits, customers can put it directly in the critical path of their own spend and access decisions
• This is a foundational role
• Enterprise and AI customers increasingly treat entitlements, spend controls, and real-time analytics as a single problem rather than three separate features, which makes this one of the highest-leverage areas of Orb's roadmap, and one of the most open
• You'll set the product strategy, decide what gets built and in what order, and shape the big questions this domain hasn't answered yet, working hand in hand with your engineering and design partners
• Define and own the product strategy for entitlements, spend controls, alerting, and usage analytics — turning a fast-converging, ambiguous space into a clear plan with the right customer outcomes and business impact
• Lead product discovery: talk to customers constantly, learn how they actually govern spend and access, and translate that into what the team builds
• Identify the smallest possible unit of value for the team to ship, and drive it through discovery, in-flight work, and launch
• Shape the strategic questions that define the domain — how far entitlements stand on their own, where real-time enforcement matters most, what customers will build their most critical spend and access logic on top of
• Build strong partnerships with engineering and design, bringing them into discovery early so user and business implications surface before the plan is set
• Context-switch fluidly across bugs, discovery, in-flight work, and launch planning
• Lay the groundwork for product practices and processes so the team can define and deliver its highest-impact work as it grows