What you'll do:

• You own and shape the team backlog – turning fuzzy ideas, customer feedback, and strategic roadmap objectives into a clear, prioritized list of things actually worth building.
• You translate business needs into crisp user stories and acceptance criteria that hold up when an agent (or a human) reads them at 9am and starts building – clarity isn't optional when code ships this fast.
• You're the team's go-to for "what does this actually mean?" – available, decisive, and ready to cut through ambiguity mid-sprint.
• You keep the agile rhythm sharp: planning, standups, refinement, reviews, and retros that make us better, not just busier.
• You review and accept delivered work against agreed expectations, and give fast, constructive feedback when something isn't there yet.
• You partner with Product Management on the roadmap and keep stakeholders – engineering, professional services, customer success, sales – aligned when priorities shift (they will).
• You protect the team's room to explore and experiment – agentic development rewards discovery – while keeping a firm eye on the time budget, championing small, frequent releases and tight iteration over any big-bang plan.
• You treat the agentic shift as a live experiment: how do estimation, "done," and the whole backlog change when agents do much of the building? You're genuinely excited to help figure that out.
• 
  

What you bring to the table:

• Some hands-on exposure to Agile product work – maybe 2–4 years as a Product Owner, Business Analyst, or in a related role, or a strong transferable background that you're bringing into product management. We care more about how you think than about your title history.
• Relentless curiosity: you ask "why" a lot, you dig into the things you don't understand yet, and you treat a hard, ambiguous problem as the fun part.
• A real pull toward the agentic world – you're fascinated by AI agents and how they're reshaping how software gets built, and ideally you already play with these tools yourself.
• Clear communication: you turn business needs into something engineers can build, and explain technical options to non-technical stakeholders without losing anyone.
• Solid instincts for prioritization and trade-offs – scope vs. time vs. dependencies – and the organization to keep a backlog from turning into a junk drawer.
• Self-aware and balanced: you know when to give the team room to dig in and experiment, and when to nudge toward shipping – and you hold that tension without becoming either a pushover or a deadline cop.
• Comfort with Agile tooling (Jira, Azure DevOps, or similar) and enough technical fluency to hold your own in an engineering conversation.
• Fluent in English (German is a plus) – you'll collaborate with customers and c