Technical Product Owner – PartnerOps

Role Overview

• Owns delivery, iteration, and learning velocity for the assigned component.
• Turns VP-level direction into clear problems to solve, a prioritized backlog, and incrementally shippable scope.
• Runs the feedback loop: discover → define → build → release → measure → iterate, repeatedly.
• Works within the Engineering teams to ensure they are always building the highest-value next increment with clarity and quality.
• Reviews technical designs, reasons about tradeoffs and constraints, and understands their impact on delivery timelines and system behavior, without being the primary implementer.
• Leverages deep experience with cloud ecosystems and partner business models to ensure platform capabilities align with how partners actually operate.
• Leverage your hands-on experience within the cloud ecosystem and understanding of channel, reseller, and partner business models.
• Develop deep empathy for the workflows of cloud partners: billing operations, margin management, reseller customer management, support operations, and service delivery.
• Use direct partner conversations and operational insight to identify friction, gaps, and opportunities to improve how partners run their cloud businesses.
• Prioritize capabilities that materially improve outcomes such as revenue growth, operational efficiency, margin visibility, billing accuracy, and scalability.
• Bring strong understanding of cloud billing constructs, marketplace programs, margin models, and partner incentives across hyperscalers.
• Help shape platform capabilities that manage or abstract complexity in areas such as: Multi-cloud billing aggregation, Partner margin and discount models, Customer invoicing and revenue operations, Usage and cost transparency, Marketplace and private offer workflows.
• Speak frequently with partners (aiming for 3–5 conversations a week) and internal stakeholders to validate ideas, refine workflows, and test assumptions.
• Engage deeply with cloud partners, MSPs, SIs, and resellers to understand how they operate their cloud businesses.
• Communicate clearly and confidently: share concepts early, take feedback openly, synthesize input into decisions, and explain "why" in a way that builds trust.
• Operate as a core member of the component's Engineering team — present in daily collaboration, crisp in decision-making, and pragmatic about constraints.
• Partner with Engineering leads on sequencing, technical tradeoffs, and delivery planning — ensuring product intent survives implementation realities.
• Ensure the component is cohesive across UX, APIs, data, and operational behavior, and supports partner-grade reliability and scalability.
• Define what "success" means for the component with clear metrics (partner adoption, onboarding speed, billing accuracy, workflow completion, retention, reliability signals, partner-reported impact).
• Instrument learning: ensure releases are measurable and that insights reliably flow back into prioritization.
• Own release readiness for your component: documentation, enablement inputs, and clear communication of what’s new and why it matters.
• Ensure platform capabilities account for the operational realities of the cloud partner ecosystem, including billing accuracy, financial reconciliation, and auditability.
• Design systems that maintain trust with partners and their customers through transparency, reporting, and reliable financial workflows.

Requirements

• 7–10 years of direct experience in the cloud ecosystem
• Strong experience with cloud billing systems, cost and usage data, or revenue operations within cloud environments
• Deep understanding of the cloud partner ecosystem (resellers, MSPs, SIs, distributors, marketplaces)
• Experience building or operating platforms that serve channel or partner-driven business models
• Strong product sense for turning messy operational problems into clear scope and shipped value with an excellent user experience
• Technical fluency in cloud fundamentals and APIs across AWS, Google Cloud, and/or Azure
• Coding experience is a plus — enough to collaborate effectively with engineers, reason about feasibility, and understand system behaviors
• Excellent communication skills: ability to engage deeply with partners, cloud experts, and internal stakeholders
• A bias for action and continuous improvement: you ship, measure, learn, and iterate.

Tech Stack

• AWS
• Azure
• Cloud

Benefits

• Unlimited Vacation
• Flexible Working Options
• Health Insurance
• Parental Leave
• Employee Stock Option Plan
• Home Office Allowance
• Professional Development Stipend
• Peer Recognition Program