Product Owner - CMP

About the role

Storyteq's Content Marketing Platform (CMP) is an enterprise SaaS product recognised as a Gartner Leader in both Content Marketing Platforms and Digital Asset Management. It serves some of the world's largest brands, helping marketing and creative teams manage the full content lifecycle: briefing, workflow, project management, templated creative production, review and approval, and asset distribution at scale. The platform is AI-enabled and in active evolution. The Product Owner - CMP is embedded within a software engineering squad and is responsible for a defined area of this platform. Operating at a quarterly horizon, this role owns the problem space for their area, working to understand what customers need, what outcomes matter, and what the right thing to build next is. This is a decisive, customer-facing, outcome-owning role. It is not a role that waits for direction. Key Responsibilities 1. Product Area Ownership & Backlog Management - Area Ownership: Own a clearly defined area of the CMP product, with full accountability for the quality and direction of the backlog and the outcomes delivered within that area. - Outcome-Driven Planning: Before any initiative is committed to, define a clear outcome hypothesis and a measurement mechanism. - Backlog Stewardship: Maintain a well-prioritised, clearly articulated backlog. User stories define the problem and desired outcome, not the solution. Solution design belongs with the engineering team. - Analytics Ownership: Own the instrumentation requirements for every feature shipped. Acceptance criteria must include what needs to be tracked and how success will be measured. - Squad Ceremonies: Lead all squad ceremonies: stand-ups, sprint planning, backlog grooming, and retrospectives. 2. Customer-Led Discovery - Direct Customer Relationships: Own direct relationships with customers within your product area. Do not rely on Customer Success to proxy the customer voice. Own the relationship directly. - Product Trio Practice: Participate in structured customer conversations as part of the Product Trio (Product Owner, UX Designer, and Engineer). - Evidence-Based Proposals: Bring proposals grounded in customer insight and data. Proposals come from direct customer discovery sessions, not internal assumptions or stakeholder opinions. - Problem Framing: Engage with the underlying problem, not the surface request. When feedback arrives, probe for the root cause before forming a view on what to build. 3. Evidence-Based Delivery - Hypothesis First: Every initiative proceeds with a defined outcome hypothesis. What does success look like? How will it be measured? - Outcome Confirmation: Track whether outcomes have actually been reached after delivery. Feature adoption is not enough. Confirm whether the expected customer behaviour or business outcome materialised. - Decisive Ownership: When engineering, UX, and stakeholders have competing views, the Product Owner makes the call. Decisions are made with the available evidence, the rationale is documented, and the outcome is owned. - AI-Enabled Working: Use AI tools to accelerate research, synthesis, documentation, and analysis. Reinvest that time in the decisions and relationships that require human judgement. 4. Planning, Communication & Release - Roadmap Candidate Management: Own and manage roadmap candidates for your product area. Contribute well-evidenced, outcome-defined candidates to quarterly planning cycles. - Request Evaluation & Initiative Shaping: Receive and evaluate inbound requests from Customer Success and commercial teams. Assess them against the evidence bar. Where requests have merit, shape them into properly defined initiatives for quarterly planning, not ad-hoc additions to the sprint. - Stakeholder Communication: Keep Customer Success and Product Marketing informed of progress, upcoming releases, and what is not coming. No should always come with a reason. - Documentation Readiness: Own the handoff to Technical Writing ahead of every release. Documentation should be ready at the point features ship. Why This Role Matters CMP is Storyteq's flagship product. Some of the world's most recognised brands run their content operations on it. What a Product Owner delivers here directly affects how marketing and creative teams at global enterprises do their work. This is not a backlog management role. It is a role that owns outcomes, works directly with customers, and is held to an evidence standard by the clients who depend on the platform. Requirements & Skills - 3+ years in a Product Owner or Product Management role within an Agile SaaS environment, with hands-on customer discovery, end-to-end backlog ownership, and measurable outcomes you can speak to specifically. - Strong working knowledge of Scrum, with the ability to lead and keep ceremonies purposeful: stand-ups, sprint planning, backlog grooming, and retrospectives. - Ability to write clear, outcome-focused user stories and acceptance criteria that include me

Your Match

How well this role fits your profile.

Company Intel

What employees say

Worked at Storyteq? Share your experience