• 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. • Before any initiative is committed to, define a clear outcome hypothesis and a measurement mechanism. • 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. • Own the instrumentation requirements for every feature shipped. Acceptance criteria must include what needs to be tracked and how success will be measured. • Lead all squad ceremonies: stand-ups, sprint planning, backlog grooming, and retrospectives. • Own direct relationships with customers within your product area. Do not rely on Customer Success to proxy the customer voice. Own the relationship directly. • Participate in structured customer conversations as part of the Product Trio (Product Owner, UX Designer, and Engineer). • Bring proposals grounded in customer insight and data. Proposals come from direct customer discovery sessions, not internal assumptions or stakeholder opinions. • 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. • Every initiative proceeds with a defined outcome hypothesis. What does success look like? How will it be measured? • Track whether outcomes have actually been reached after delivery. Feature adoption is not enough. Confirm whether the expected customer behaviour or business outcome materialised. • 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. • Use AI tools to accelerate research, synthesis, documentation, and analysis. Reinvest that time in the decisions and relationships that require human judgement. • Own and manage roadmap candidates for your product area. Contribute well-evidenced, outcome-defined candidates to quarterly planning cycles. • 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. • Keep Customer Success and Product Marketing informed of progress, upcoming releases, and what is not coming. No should always come with a reason. • Own the handoff to Technical Writing ahead of every release. Documentation should be ready at the point features ship.

• 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. • Before any initiative is committed to, define a clear outcome hypothesis and a measurement mechanism. • 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. • Own the instrumentation requirements for every feature shipped. Acceptance criteria must include what needs to be tracked and how success will be measured. • Lead all squad ceremonies: stand-ups, sprint planning, backlog grooming, and retrospectives. • Own direct relationships with customers within your product area. Do not rely on Customer Success to proxy the customer voice. Own the relationship directly. • Participate in structured customer conversations as part of the Product Trio (Product Owner, UX Designer, and Engineer). • Bring proposals grounded in customer insight and data. Proposals come from direct customer discovery sessions, not internal assumptions or stakeholder opinions. • 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. • Every initiative proceeds with a defined outcome hypothesis. What does success look like? How will it be measured? • Track whether outcomes have actually been reached after delivery. Feature adoption is not enough. Confirm whether the expected customer behaviour or business outcome materialised. • 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. • Use AI tools to accelerate research, synthesis, documentation, and analysis. Reinvest that time in the decisions and relationships that require human judgement. • Own and manage roadmap candidates for your product area. Contribute well-evidenced, outcome-defined candidates to quarterly planning cycles. • 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. • Keep Customer Success and Product Marketing informed of progress, upcoming releases, and what is not coming. No should always come with a reason. • Own the handoff to Technical Writing ahead of every release. Documentation should be ready at the point features ship.

Role Description In this role, you will take complete, end-to-end ownership of multiple Shopify applications. Serving as both the strategic architect and the operational anchor, you will ensure that every released feature is impactful, user-friendly, and closely aligned with customer needs. - Full-Lifecycle Product Management: Manage the progression of new app features from early validation, conceptual design, and technical scoping through to deployment and continuous post-launch iteration. - Backlog Grooming & Prioritization: Independently structure, refine, and prioritize the product backlog. Act as the definitive filter for incoming feature requests, internal stakeholder inputs, and Customer Success tickets. - In-Depth User Discovery: Uncover and validate genuine user pain points by blending qualitative and quantitative research techniques, utilizing direct interviews, heatmaps, and drop-off analysis. - Technical Specification Writing: Translate abstract conceptual ideas into developer-ready Jira tickets, writing clear user stories, rigorous acceptance criteria, and comprehensive product documentation. - Metrics & Data Analytics: Define precise KPI baselines ahead of engineering sprints and conduct thorough post-launch analyses to guarantee that product iterations remain strictly data-driven. - Strategic Roadmap Collaboration: Work hand-in-hand with executive leadership to shape the long-term product vision, planning major epics, managing cross-functional dependencies, and backing up priority decisions with data. - Greenfield Innovation: Monitor broader e-commerce trends to draft entirely new application concepts, validating them with initial market research and commercial business cases prior to development. Qualifications - Demonstrated PM Expertise: 2+ years of independent product ownership experience, preferably delivering digital products within agile development environments. - Data-Driven Mindset: High proficiency with modern product analytics platforms (e.g., PostHog, Mixpanel, Tableau) to formulate testable hypotheses and accurately measure feature performance. - Structured Prioritization: Practical experience using objective evaluation frameworks (such as RICE or ICE) to make logical trade-offs when navigating resource or timeline constraints. - User-First DNA: A dedicated advocate for the end-user, with a proven track record of converting qualitative behavioral data into highly successful software solutions. - Availability: Prepared to onboard and start actively working by August 1st at the very latest. Requirements - Background working within B2B/B2C SaaS environments or a deep familiarity with the Shopify and broader e-commerce landscape. - Foundational understanding of Product Marketing dynamics, including Go-to-Market (GTM) strategy, user onboarding optimization, and retention loops. - Demonstrated ability to coordinate multiple independent software products or complex feature portfolios simultaneously without losing focus. Benefits - High Operational Freedom: Take full, end-to-end responsibility for live software assets where your strategic decisions directly shape agency growth. - Protected Learning Time: 10% of your core working hours are strictly set aside for your personal upskilling, research initiatives, and professional certifications. - Total Remote Flexibility: Work from any location within Germany via fully digital workflows, along with opportunities to join international company workations. - Psychological Safety: Thrive in a flat organizational layout where human values are prioritized. Innovation requires taking risks, and mistakes are viewed as vital learning milestones. - Premium Employee Perks: - JobRad: Bicycle leasing framework. - Deutschlandticket: Full coverage for local and regional public transit. - Urban Sports Club: Corporate wellness membership. - Mental Health Support: Access to an official well-being platform. - Retirement Planning: Company-backed pension plan (Betriebliche Altersvorsorge).

• Own a problem space end-to-end • Work across both sides of the experience: operator back office and end-customer storefront • Collaborate closely with engineering leads • Stay close to customers and understand their needs • Shape how the company works