YOUR ROLE AT SIXT

• You share architectural ownership of SIXT's payment platform, not carry it alone. It's grown fast this past year alone: a payment method with a settlement lifecycle stretching over weeks and a mobile-wallet integration deep inside our PCI-secured zone
• You report directly to our Division Engineering Manager for Finance, a direct seat at the table on architecture decisions, not a role several layers removed from where they get made, working alongside about 40 engineers in six teams spread across multiple countries
• Every new use case is a cross-channel, cross-system flow: a payment might start at a counter, in the app, or on the web, and your design follows it through refunds, disputes, and reconciliation. You carry that same ownership into our multi-year migrations: the franchise business coming onto the platform, a decade-old legacy core being retired, and invoices that now split more ways than before
• You use AI as a genuine lever, not a checkbox, leaning on the in-house agentic toolkit we've built for payment investigations and design reviews to stress-test integration decisions before they get expensive to unwind
• You stay hands-on where it matters: writing RFCs and reference implementations, prototyping to de-risk a design, and reviewing the load-bearing code, on a stack of Java, Spring Boot, Kafka, PostgreSQL, Temporal, AWS, and Kubernetes
• You raise the design bar across the platform, pairing with staff engineers and engineering managers on their toughest calls, and leaving each of them more confident to own the next big one themselves
• 
  
• 
  

YOUR SKILLS MATTER

• Experience You have several years designing and owning architecture for payment or financial-transaction systems end-to-end, ideally having mentored other engineers into that kind of ownership along the way
• Payments Fluency You understand payment flows (authorization, capture, refund, chargebacks, reconciliation), know your way around the regulatory frameworks behind them (PCI-DSS, PSD2, and the like), and design comfortably across both modern and legacy systems
• Engineering Depth You still build: strong on the JVM, comfortable with event-driven designs where money has to move exactly once, and fluent in the habits that go with them: idempotency, retries, observability
• Systems Judgment You default to designing for the whole flow rather than the piece directly in front of you, and you're comfortable being the one who makes the call when two systems' constraints pull in different directions
• AI Fluency You reach for AI tools as a genuine thinking partner in your day-to-day design work, and you know exactly where you still need to verify things yourself
• Stakeholder Leadership You drive architectural alignment across engineering teams through influence and technical credibility, not formal authority, and communicate trade-offs so both engineers and leadership can act on them
• 
  

YOUR ROLE AT SIXT

• You share architectural ownership of SIXT's payment platform, not carry it alone. It's grown fast this past year alone: a payment method with a settlement lifecycle stretching over weeks and a mobile-wallet integration deep inside our PCI-secured zone
• You report directly to our Division Engineering Manager for Finance, a direct seat at the table on architecture decisions, not a role several layers removed from where they get made, working alongside about 40 engineers in six teams spread across multiple countries
• Every new use case is a cross-channel, cross-system flow: a payment might start at a counter, in the app, or on the web, and your design follows it through refunds, disputes, and reconciliation. You carry that same ownership into our multi-year migrations: the franchise business coming onto the platform, a decade-old legacy core being retired, and invoices that now split more ways than before
• You use AI as a genuine lever, not a checkbox, leaning on the in-house agentic toolkit we've built for payment investigations and design reviews to stress-test integration decisions before they get expensive to unwind
• You stay hands-on where it matters: writing RFCs and reference implementations, prototyping to de-risk a design, and reviewing the load-bearing code, on a stack of Java, Spring Boot, Kafka, PostgreSQL, Temporal, AWS, and Kubernetes
• You raise the design bar across the platform, pairing with staff engineers and engineering managers on their toughest calls, and leaving each of them more confident to own the next big one themselves
• 
  
• 
  

YOUR SKILLS MATTER

• Experience You have several years designing and owning architecture for payment or financial-transaction systems end-to-end, ideally having mentored other engineers into that kind of ownership along the way
• Payments Fluency You understand payment flows (authorization, capture, refund, chargebacks, reconciliation), know your way around the regulatory frameworks behind them (PCI-DSS, PSD2, and the like), and design comfortably across both modern and legacy systems
• Engineering Depth You still build: strong on the JVM, comfortable with event-driven designs where money has to move exactly once, and fluent in the habits that go with them: idempotency, retries, observability
• Systems Judgment You default to designing for the whole flow rather than the piece directly in front of you, and you're comfortable being the one who makes the call when two systems' constraints pull in different directions
• AI Fluency You reach for AI tools as a genuine thinking partner in your day-to-day design work, and you know exactly where you still need to verify things yourself
• Stakeholder Leadership You drive architectural alignment across engineering teams through influence and technical credibility, not formal authority, and communicate trade-offs so both engineers and leadership can act on them
•