Java Software Engineer – Event Driven Platforms (Kafka)

Java Software Engineer – Event Driven Platforms (Kafka)

For 37 years we have built software that sits at the heart of financial institutions. The kind of systems where reliability, traceability, and scale are not nice-to-haves, they are essential.

We are looking for a Java Software Engineer who has hands-on experience designing and building event-driven architectures , with Kafka as a core part of the platform , not an afterthought. This role is about building and evolving the event backbone that drives complex, business-critical workflows across multiple services.

The engineering challenge

You will work on systems where a single event can trigger multiple downstream processes, such as compliance checks, enrichment, audit logging, and real-time decisioning. The platform is built to handle high throughput, strict reliability requirements, and evolving business rules. You will be expected to think beyond synchronous APIs and design systems that are:

• Decoupled and scalable
• Resilient to failure and easy to recover
• Observable and traceable end-to-end

Kafka is used as the central nervous system of the platform, running in a modern cloud-native environment.

What you will be doing

• Designing and implementing event-driven services in Java
• Producing and consuming Kafka events that power core business workflows
• Working with topics, partitions, and consumer groups to support scale
• Handling real-world concerns such as retries, reprocessing, idempotency, and failure scenarios
• Collaborating closely with other engineers and product teams on architectural decisions
• Deploying and running services in a Kubernetes, Docker, Helm, and ArgoCD ecosystem

What we are looking for

• First-hand experience building Kafka-based event-driven systems in production
• Solid understanding of event delivery semantics and failure handling
• Confidence designing systems, not just implementing tickets
• A pragmatic, engineering-led mindset with a focus on quality and reliability

Nice to have

• Kafka Streams or stream processing experience
• Schema versioning or schema registry exposure
• Experience with observability and monitoring in distributed systems
• Familiarity with GitOps-style deployment workflows

Why Join

• Complex, meaningful technical challenges
• A product-led engineering culture where architecture matters
• Close collaboration across engineering, product, and the wider business
• The chance to work on systems that are genuinely critical to financial institutions
• 2 days a week on-site, 3 days work from home (Berlin)

If you are excited by event-driven thinking, enjoy solving hard backend problems, and want to build systems that scale cleanly over time, we would love to hear from you.