Summary
✨ AI‑Generated
Take ownership of technically demanding revenue-management products where product decisions require deep engineering judgment. You will work closely with engineers and business stakeholders to decide priorities, define what success looks like, and turn commercial needs into buildable solutions. The role sits within engineering and offers substantial exposure to AI, automation, and agentic tooling.
Highlights
Own technically complex products where engineering and product judgment intersect. Work directly with engineers and business stakeholders, influence priorities and quality standards, and operate at the intersection of commercial data, automation, and AI.
Description
Job DescriptionRevenue 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 stableYou 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 shipYou 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 outputTechnical 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 countYou 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.
That same closeness lets you say no well when you have toYOUR SKILLS MATTER
Engineering depth you actually use You read code fluently and dig into a codebase to verify a claim or judge a change.
You'll rarely write production code, never on the critical path, but you've been close enough to it that engineers trust your judgmentAI in how you work, not a talking point You use coding assistants, agents, and LLMs as part of your workflow already.
You've built or evaluated LLM-based and agentic systems enough to judge what they're doing and whether to trust the output.
Baseline here, not a specialismA track record of decisions, not alignment You've owned a call that made a stakeholder unhappy, and it held.
Tell us the instance, the pushback, what happened afterSystems and platform judgment You have a solid grasp of distributed systems, APIs, service boundaries, and data-intensive architectures — enough to spot coupling, failure modes, and long-term costData-driven trade-offs You use evidence to prioritize, define success, and argue for cutting things, and build the measurement when it doesn't exist yetWriting that carries decisions You can write a scope rationale or ADR someone outside the room can act on.
Bring a real example WHAT WE OFFER
Extra benefits Enjoy discounts on SIXT rent, share, ride and SIXT+, attractive vehicle leasing offers, and exclusive deals with partners for travel, tech, fashion and moreMobility boost We support you with a monthly mobility allowance of €20 per month for even more freedomFuture security We contribute to your retirement plan and support you with capital-forming benefits to ensure you are well coveredFeel-good atmosphere Stay active with our modern SIXT gym, various leisure activities like the gaming area or the SIXT choir, and enjoy our high-quality employee restaurantFlexibility Enjoy 30 days of vacation and a hybrid working model with flexible hoursGiving back Take one day each year to volunteer at a charitable organization dedicated to supporting children