Senior Technical Product Owner — Revenue Management (m/f/d)

About this role

Revenue Management at SIXT runs on systems that gather, interpret, and act on huge amounts of commercial data, with automation and agentic tooling doing the work. Based in Pullach near Munich, this role owns the products where the hard calls are engineering judgment as much as product judgment, where correctness is verified by observing behavior, not by reading a spec. You'll sit with the engineers who build these systems and make the calls that keep them moving: what we build, what we decline, what "done" means, when a direction is wrong.

You work directly with our business stakeholders as their technical partner, turning what the business needs into something buildable. No direct reports, no ambition to get any: seniority here is mandate and depth, not headcount. The role reports into Engineering, keeping these systems anchored to technical reality even as commercial demands pull on them. We use AI heavily across engineering, and part of this portfolio is agentic.

We're hiring someone who can own hard technical products, whatever they're built from. YOUR ROLE AT SIXT You own the deep-tech slice of the portfolio, one or two products at a time: Full ownership — direction, scope, priorities, and the call to stop doing something. Pricing logic, automated decisioning, agentic tooling: products where the roadmap depends on how the system behaves, combined with what stakeholders ask for.

No floating between five initiatives, no project management: you carry the decisions yourself and move on only once the current one is genuinely stable You define correctness for systems you can't just read: Some of what we build is generated or emergent enough that behavior is easier to observe than implementation is to inspect. You define "working," design how we verify it, and call when the evidence is good enough to ship You set the boundaries for AI in the products themselves: Automated pricing and agentic decisioning are part of what you own, not just how you work.

You decide what these systems can act on autonomously, where a human needs to be in the loop, and how much confidence we need before we trust the output Technical partnership, written decisions: You work with engineers on feasibility, architecture, and trade-offs, and co-own the ADRs that make those calls durable. Part of engineering is remote, so undocumented decisions don't count You drive technical innovation with the business: Spot what's newly possible and turn it into use cases our business stakeholders actually want, shaped together, not handed down.