Über diese Product Owner (Integrations) Stelle bei Keyloop
Purpose of the Role
The Product Owner owns the outcomes of a product area within Keyloop's core dealer management platform and its integration ecosystem: the systems that connect our platform to manufacturers, third parties, and other data sources. You'll work with an engineering team that combines deep platform expertise with delivery skill, turning integration and platform priorities into a backlog that keeps the ecosystem reliable and moving forward.
This role suits someone comfortable with technical complexity and long-lived systems. You won't need to be an engineer, but you'll need to be able to hold your own in a conversation about APIs, data contracts, and system dependencies.
AI tooling is a growing and permanent part of how our Product and Engineering teams work, and this role is evolving with it. We expect Product Owners to grow into hands-on AI-building over time. This is a deliberate direction for the role, not a distant possibility, and we're looking for people who are genuinely ready and willing to make that journey, even if they're not there yet.
Responsibilities
- Own and prioritise the development team backlog, balancing new integration delivery against platform stability and technical debt
- Write, refine, and prioritise epics and user stories, including ones with less obvious “customer” framing, where the customer is another system or internal team
- Work directly with engineers to understand technical constraints and translate them into backlog decisions
- Collaborate with the development team during Iteration Planning, stand-ups, and reviews
- Accept completed work against the Definition of Done, including technical acceptance criteria
- Work with the Product Manager to align delivery priorities with the wider platform and integration roadmap
- Track delivery and reliability metrics, and use them to prioritise fixes and improvements
- Manage dependencies and sequencing across multiple integration partners or workstreams
Working with AI: where this role is going
- Use AI tools (e.g. Claude) to support day-to-day product work now: drafting specs, exploring data, speeding up research and analysis
- Grow into hands-on use of AI coding tools (e.g. Claude Code) to prototype and validate ideas yourself, with structured training and time provided to get there
- Apply judgement on where AI-assisted output needs human review
- Understand that this capability will become a core, evaluated part of the role over time, not an optional extra
Skills, know-how and experience
Must have
- Solid understanding of Agile principles and the Product Owner role within Scaled Agile
- Proven ability to write clear, concise epics and user stories, including technical/integration-facing ones
- Comfortable engaging with technical detail: can read an API spec or data model well enough to write meaningful acceptance criteria, without needing to write the code
- Strong communication skills, able to bridge technical and non-technical stakeholders
- Ability to analyse data (including system/reliability metrics) and make prioritisation calls
- Comfortable using AI tools day-to-day to support product work (e.g. research, writing, analysis), plus a clear, genuine willingness to grow into hands-on AI-building (e.g. Claude Code) as this becomes a core part of the role. This is where the Product Owner role at Keyloop is deliberately heading. Candidates should be ready to commit to that development path, even if not yet hands-on today.
- Experience owning backlog for a platform, integration, or infrastructure team (rather than a purely customer-facing team)
- Familiarity with Jira, Confluence, or similar tools
- Relevant certifications (e.g. CSPO, SAFe POPM)
- Experience with legacy system modernisation or working across old and new tech stacks simultaneously
- Understanding of automotive aftersales processes (e.g. service booking, workshop operations, repair order lifecycle) and how they depend on integration and platform reliability
- Existing hands-on experience using AI coding tools (e.g. Claude Code) to build or prototype software
Preferred
Development pathway
Growing into hands-on AI-building is an expected part of every Product Owner's development here. This isn't an exception process, it's the plan for everyone. We'll invest in structured training and dedicated time to help you get there. What matters on day one is genuine readiness and willingness to make that journey, not that you've already arrived.
