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 experience quality of our toll product — everything that affects how customers actually feel about using it: how clear the onboarding is, how confident a fleet manager feels looking at their costs, how easy it is to handle an exception.

The product works. Your job is to make it feel effortless.

This means spending real time understanding where customers get stuck — through interviews, usability sessions, support data, and analytics. It means translating those findings into clear problems worth solving, prioritizing ruthlessly, and working with engineering and design to ship solutions that actually change behavior.

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.

You run your own discovery — you don't wait for a researcher to hand you insights. You can work with data without needing someone to pull every query. You can have a direct conversation with a stakeholder about why you're not building their idea right now.

B2B product experience is useful. SaaS or mobility background is a plus. Domain knowledge in tolling is not required — it's learnable. Product judgment isn't.

• Mapping the customer journey end-to-end and identifying where it breaks down
• Defining and tracking experience metrics — the meaningful signals, not just NPS
• Running discovery: customer interviews, usability tests, support signal analysis
• Collaborating with CS on recurring issues that turn out to be product problems
• Working with design on new flows and with engineering on what's actually shippable
• Iterating based on outcomes — whether something shipped is less interesting than whether it worked

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