The Toll team at Eurowag builds and runs the platform that handles electronic toll payments for commercial vehicles across Europe. Our customers are fleet operators and drivers who need to move goods across country borders. When the product works well, they barely notice it — toll is just handled. When it doesn't, it's a real problem.

You'll own the product side of adding new toll domains to our platform. The strategic direction — which countries to add and when — is set at a level above this role. Your job starts from there: given that we're adding a new toll domain, what needs to be built, in what sequence, and what does 'done well' actually look like?

You'll work alongside domain owners who cover external partnerships and the regulatory landscape. Understanding both at a high level is part of the job — not to be the expert, but to know what they mean for the product: what trade-offs they create, what constraints shape the solution, and where decisions need to be made.

One thing you'll keep constant focus on: as we add new toll domains, the product shouldn't get harder to use for the customers already on it. Coherence across a growing portfolio is part of the job.

You'll own your roadmap and backlog. You set the priorities, you defend them, and you're accountable for outcomes — not just delivery. Roughly 5 years of product management experience is a good baseline — but we'll move fast for someone earlier in their career who clearly has the instincts, the drive, and a bias for getting things done without waiting for perfect conditions.

You don't get blocked. When a decision needs to be made and it's in your domain, you make it — then course-correct if needed. You take ownership of outcomes, not just delivery, and you don't need someone above you to clear every path forward.

Ideally you've worked in a domain with external dependencies — partners, regulators, integrations, or geographic complexity. That kind of background shortens the ramp-up. But it's not a gate.

You're comfortable with ambiguity and know how to make a decision when the information will never be complete. You can hold a business conversation with an external partner and translate it into a product brief for your engineering team.

Enough technical familiarity to understand what an integration constraint means for your roadmap. You don't need to write the API, but you need to understand the tradeoffs it creates. Domain knowledge in tolling is not required.

• Scoping what needs to be built to support a new toll domain and sequencing the work
• Defining what good looks like at launch — and what can come later
• Translating external constraints (regulatory, technical, operational) into product requirements
• Working with domain owners and engineering to make sure the product reflects reality on the ground
• Keeping the overall product experience coherent as coverage expands
• Understanding what completing coverage in a new country unlocks — for existing customers who currently work around the gap, and for prospects for whom it was the last missing piece
• Tracking outcomes post-launch and feeding learnings back into future expansion

Tools: Claude (Cowork), Figma, Jira, Confluence, Miro, GA4, Azure DevOps