🚀 Be part of a movement to change the way Europe pays

In today’s digital world, payments often still feel outdated: random delays and confusing rules make it harder than it should be to pay and get paid. The European Payments Initiative (EPI) is here to change all that, forever.

With Wero, our digital wallet, we make sending and receiving money simple, seamless and secure across France, Belgium and Germany, with more countries and omnichannel solutions coming soon. Supported by 16 major banks and the two largest European acquirers, EPI is building a new, proudly European payment system: easy, instant and transparent, all for the greater good.

🔎 What's in it for you

In this role, you’ll drive the development of cutting‑edge payment and identity solutions for Europe. You’ll lead rapid prototyping of EUDI flows, influence key architectural decisions, and help shape the future of our platform. Working with a modern tech stack and a collaborative, remote‑first team, you’ll deliver secure, scalable services that millions can trust.

Our roadmap is clear: prototyping and specification run through 2026, pilot and testing follow in 2027, and then we move into integration within Wero, our digital wallet, and rollout. You’ll provide technical continuity across phases and have the opportunity to grow into a trusted Digital Identity engineering reference in the organisation, working alongside teams across EPI as the topic expands.

🐝 About the team

You will work closely with our Digital Identity Product Leader and Product Design as part of a small, focused task force. From day one, you act as the Engineering Lead, turning ambiguous requirements into working prototypes and clear technical decisions. You will collaborate with our broader Pan-European engineering organisation (backend, iOS, Android) across Europe in a matrix setup, and you should enjoy owning the technical direction throughout the phases, from prototype to pilot, and into Wero integration and rollout.

💥 Your impact

• Lead discovery and prototype end-to-end payment and EUDI/EUDIW flows, including combined payment consent and identity attributes (e.g. age verification)

• Turn evolving pilot requirements into clear APIs, interface contracts, and working reference implementations that others can build on

• Document architecture decisions (ADRs) and define technical guardrails to ensure continuity from prototype to pilot, and into Wero integration and rollout

• Enable Product Teams to industrialize prototypes into production solutions by providing technical direction, reviews, and hands-on support

• Coach engineers on architecture, implementation, observability, and automated testing

• Drive architectural choices that balance short-term delivery with long-term scalability

• Proactively manage technical debt and design for resilience and growth

• Apply modern system design patterns and REST/OpenAPI best practices

• Implement defense-in-depth security measures

• Maintain high quality through comprehensive testing and clear documentation

💻 Technology stack

• Primary: Java, Kotlin, JavaScript, Python or any other major programming language, OpenAPI, Docker

• Secondary: Kubernetes, Terraform

This is our current stack, but we stay technology-agnostic. What matters most is your ability to ship end-to-end flows and make pragmatic choices during the prototyping phase.

🕵🏻‍♀️ To succeed, you should meet at least 70% of these requirements

• +5 years of professional experience developing highly scalable web applications

• Strong knowledge of Java, Kotlin, JavaScript, Python (or any major programming language)

• Experience with OpenAPI and Docker, combined with hands-on expertise in AWS, Kubernetes, and Terraform

• Understanding of eIDAS 2 Regulation and PSD2 / PSD3 / PSR Directive

• Fluent in English (CEFR C1 or C2); French, German or Dutch or any additional European languages is a plus

• Participation in an EUDIW Large Scale Pilot; familiarity with W3C Verifiable Credentials, OpenID4VP, OpenID4VCI

• Experience with EUDI, payments, and the financial services industry

🪜 If this looks like you, the recruitment steps are:

1. A first call with one of our recruiters

2. A technical interview with our Senior Software Architect & Head of Engineering

3. An interview with our Digital Identity Product Lead

4. A final interview with our CPTO

5. Hopefully, an offer you can’t refuse

⛔ Turn back if …

• You’re looking for an already highly structured environment with no ambiguity

• You are not open to working on discovery and prototyping

• You’re not comfortable leading the technical direction from day one, including making decisions with incomplete information

• You prefer to focus purely on delivery within a team, rather than acting as an internal technical partner who aligns with stakeholders and shapes interfaces

• You’re not comfortable translating business, regulatory, or consortium inputs into clear technical scope, architecture decisions, and documentation

• You don’t enjoy frequent stakeholder communication and explaining technical trade-offs to mixed audiences