Senior Technical Product Manager II - Europe
We are looking for an experienced Senior Product Manager to own the multi-year vision, roadmap, and performance for a key product area at Storyblok. You will own the what and the why around your products, from early discovery and definition through launch and improvement. You will set standards across the product team, working closely with Engineering and Design to turn strategy into a clear delivery plan, make practical calls on scope and tradeoffs, and support teams all the way through to shipping. You'll report on how your product area is performing, and represent that direction to executives, key customers, and industry analysts. You'll also partner closely with our Developer Experience team to make working with our APIs, SDKs, and docs something developers actively enjoy.
ESSENTIAL JOB FUNCTIONS
Key Responsibilities:
Product area vision & roadmap: Set the multi-year vision and own the roadmap for a key product area. Decide what gets built in what order across this area, and explain why you made those calls. Bring net-new product bets to the executive team when you spot one worth making.
Product Discovery: Set the research agenda across your area rather than running all of it yourself. Decide what needs investigating, commission the work, and spot market shifts before they show up in the numbers.
Developer experience. Treating docs, error messages, and the composable/MACH integration ecosystem as part of the product.
Business cases: Build company-level business cases, such as a new pricing tier or a new market, that hold up in front of leadership and show how product spend turns into results the business can measure.
Release strategy: Set the standards for how releases are governed across the company: what ships in what order, what has to be working before it does, and what every team needs in place to be ready.
Stakeholder management: Keep executives, key customers and industry analysts informed and on the same page as priorities shift.
Cross-team leadership: Become the leader in your area, shaping organisation-wide product culture. Arbitrate the conflicts and competing priorities that span whole orgs rather than passing them up the chain.
Metrics & measurement: Set the metrics and analytics standards other product areas work to, and report on how your own area is performing.
Design and engineering collaboration: Work closely with design and engineering from the first research through launch. You shape the design philosophy at the platform level and set the component and API conventions teams follow, they bring the craft and the technical judgement, and together you decide what ships, what waits, and how good it has to be.
Writing: Set the spec and writing standards other product teams work to, and write the internal docs that inform executive-level decisions.
External communication and launch stories: Represent the product narrative externally through keynotes and analyst briefings, and drive category-defining thought leadership.
Mentoring: Mentor across the product team, growing ownership and judgement in other PMs rather than making their calls for them.
Education and experience
A degree in engineering, product, or something related
8+ years in product management, at least 3 of them on technical, developer-facing, or platform products
Hands-on experience with developer tools, or platform products.
Experience owning a whole product area, not single features
Demonstrated technical fluency: you can read API documentation, run discovery interviews with senior engineers, and write a PRD that engineers respect.
A track record of setting a multi-year vision and carrying it through to shipped results you can measure, including at least one company-level bet such as a new market or a new pricing tier
Experience in CMS, content infrastructure, or DXP is a strong plus
Qualifications
You understand how SaaS businesses work, along with their customers, partners, and the wider B2B world
Strong commercial sense. You can build the case for a new tier or a new market, and connect product decisions to revenue, retention, and cost
Strong writing and speaking. Comfortable on a keynote stage or in an analyst briefing, not just in front of executives and customers
Technical enough to hold your own on platform architecture decisions with engineering, rather than only following them
Hands on: You'd rather build a rough prototype than describe the idea in a doc.