Software Engineer; m​/f​/d; Revenue Management

• Legal Entity:
  Sixt SE

Revenue Management at SIXT runs on systems that gather, interpret, and act on huge amounts of commercial data from our Pullach near Munich headquarters. Pricing decisions are made automatically, at scale, with automation and agentic tooling doing more of the work every quarter. This role owns how those systems are built: the architecture, the hardest technical calls, and the engineering bar that keeps them correct when every decision is real money.

You’ll work across our Revenue Management engineering teams as the senior hands‑on technical voice: setting direction where it spans teams, going deep where the problem is hardest, and raising the bar for everyone around you. You partner closely with multiple Engineering Managers, their teams, and product owners: they own what we build and why, you own how, and whether it will hold.

We use AI heavily across engineering, and part of this platform is agentic. We’re hiring someone who can design, build, and harden systems where some of the behavior is generated rather than written.

• You own the technical direction for our Revenue Management systems: architecture, service boundaries, data flows, and the long‑term cost of today’s choices. You write it down, invite the challenge, and make the call
• You build the engineering pipeline: how agents code, test, and ship our work across teams, the eval loops that tell us it’s working, and the standards other engineers build on
• You stay close to the code where it counts: the problems nobody else can unblock: performance, correctness, migrations, incidents. You lead through the pipeline and its standards, not by sitting on the critical path
• You design how we know these systems are right: testing, evaluation, and observability for pricing logic and agentic components whose behavior is easier to observe than to inspect. You set the guardrails: what runs autonomously, where a human stays in the loop, and how things fail safely
• You own quality standards and make them enforceable: the Non Functional Requirements (latency, reliability, cost, auditability), architectural constraints that fail the build instead of waiting for a reviewer, and tech debt strategy as measurable constraints you can enforce in code, pipelines, and reviews
• You grow the engineers around you through design reviews, pairing, and honest feedback. Part of engineering is remote, so decisions live in writing: design docs and ADRs that someone outside the room can act on. You spot what’s newly possible, especially with LLMs and agents, prove it with a prototype, and turn it into something the teams can build on

• Technical Depth Many years building and operating production backend systems, and you still write code you’d put your name on. Strong in multiple languages and comfortable with cloud solutions
• Distributed Systems You’ve designed systems that process high‑volume data and make decisions in near real time: APIs, event streams, storage, consistency, failure modes. Tell us about the incident you learned the most from
• Applied AI Assistants and agents are already part of your daily workflow. You’ve built or shipped LLM‑based or agentic systems and know how to evaluate them, constrain them, and tell when they’re wrong
• Technical Leadership You’ve set technical direction across multiple teams and it held, know when to build it properly and when good enough is right, can explain the cost of both, and you’re willing to kill your own ideas when the evidence says so. Tell us the instance, the disagreement, what happened after
• Written Communication You can write a design doc that changes minds and still makes sense a year later. Bring a real example
• Domain…