Senior Product Manager

THE OPPORTUNITY IN A NUTSHELL You? A senior Product Manager who is curious about what a platform has to become when it is no longer only people interacting with it — and who wants to be one of the people working that out. Role? Own the product direction for DAIM — Data, APIs, Integrations & ML — the team that supplies the data and integration foundation the rest of Vend Mobility builds on. Location? Oslo, Stockholm and Kraków. Hybrid. Why us? Agentic commerce is on the rise, and we intend to be among the leading innovators in the Nordics. We think the pieces we'd build on are ones nobody else has: years of accumulated dealer behaviour, verified vehicle condition data, and buyer intent across three countries. We don't pretend to know exactly what agent-native looks like yet — but almost every step towards it is, in practice, a data or API delivery. This is the team that has to make them real — and right now it has no product manager. Sounds like your cup of tea? Check out the details below! WHAT'S THE JOB LIKE? DAIM owns the external API platform our professional customers integrate with, the backend services behind our insight products, our data integrations, and our core ML capability. Our customers are professional dealers — in cars and across our other mobility sub-verticals — and their software vendors, our own product areas, and, increasingly, the AI agents acting on all of their behalf. The mission is to make that a trusted platform : something people can build on, integrate against, and pay for. You own the product direction for it. One thing to be clear about up front: this team wins through other teams, or not at all. Product teams across our marketplaces build their own data products, and they should. DAIM does not own all of them. We build the ones a single team cannot — the ones that need data from several teams at once, or that carry insight complexity beyond what one team can reasonably take on. Knowing which is which, and being welcome in the rooms where that gets decided, is most of the job. In practice, five things: Make integrations solve the customer's actual problem. We have an engineering team that builds and operates this platform to a standard we are proud of. What the team is missing is a product counterpart: someone who keeps the customer in the room, makes sure what we build meets what dealers and their software vendors genuinely struggle with, and that integrating with us is smooth enough that adoption follows. Together you own the outcome — you measure it in adoption and time-to-integrate. Get our export API right. This is the sharpest problem in the first six months: deciding what belongs in the API for partners to build on, and what should stay only in our own dealer platform. It is a boundary question with commercial and strategic consequences, and it cannot be answered alone — it takes close work with the areas on either side of the line. Enable the vertical — and build what's better built once. Our mission is to enable the whole Mobility organization to build great data products, and most of that is foundation: the pieces product teams build on top of themselves. But some things are complex enough that it makes more sense for us to build, own and maintain them — we buy external data, and we hold data across teams, and in some cases the value only appears when the pieces come together. Where that boundary sits is unclear by design. Finding it, case by case, with the product teams, is part of this job. Own the portfolio. Map every data product and API we run today, internal and external, and give each one a verdict: invest, maintain, or retire. Then act on the retire list — including reviewing and winding down the legacy contracts behind it. Set the agentic direction. Our platform was designed for people. We think it will increasingly have to serve agents acting on our customers' behalf as well — and we're honest that nobody knows exactly what that looks like yet. Establish what the evolution towards agent-native would actually take, prove it with a pilot, then write the plan that gets us there. We see this as a no-regret investment: the floor, not the moat. We should be standing on that floor. Success in this role means After 6 months: The export API has a decided scope, agreed with the areas on both sides of the boundary — we know what we expose and what stays in the dealer platform, and why. Our professional customers are adopting the API platform, and you can show it. You are a trusted counterpart to the other product areas rather than a service desk they file tickets with. After 1 year: We have delivered agent-native pilots that have given us real proof points and demonstrable customer value, and a funded plan for scaling them. We also have a shared position on the whole portfolio — what we invest in, what we maintain, what we retire — and the first retirements are done. WHO ARE YOU? 5+ years as a Product Manager , with real experience of data products, APIs, or platform products — not only user-facing features. You get things done through other teams. You are energised, not frustrated, by work where your leverage comes from other people's roadmaps. You can tell the difference between a product we should build and one another team should own — and you are willing to hand over the second kind. Outcome-oriented. Shipping is where the job starts, not where it ends. You obsess over adoption, time-to-integrate, and whether the customer's problem actually went away. Portfolio thinker, not project deliverer. You can hold a whole estate of products in your head and decide what dies so something else can live. Tech-minded. Authentication and authorisation, event streams, data pipelines, API and schema design. You speak the language of engineering and can tell a real architectural trade-off from a preference. Commercially minded. You have monetised data or API access before, through pricing, packaging or partnerships, and you can build a model that survives cont