Can you describe your role as a software developer for open banking?
I work as a software developer at SBS, where I design, develop, and optimize backend services for our open banking products. My role goes beyond coding—I contribute to architectural discussions, ensure high-quality, reliable feature delivery, and continuously look for ways to improve performance and user experience. It’s a mix of problem-solving, creativity, and collaboration that keeps the work exciting and meaningful.
In concrete terms, what kind of open banking projects do you manage on a daily basis?
On a daily basis, I work on backend development, compliance-driven features like strong customer authentication and data protection, and contribute to architectural design and performance optimization. Currently, my main focus is on Wero, an instant payment solution initiated by EPI to harmonize digital payments across the EU. We’re designing a system that integrates core banking, EPI bank connectors, and consent management to enable seamless wallet-based transactions.
Our team of six developers is also maintaining two other products: FDX, our open banking solution for the U.S. market, and our legacy PSD2 platform, which we’re gradually transitioning to a next-gen architecture.
Is there one that you found particularly interesting?
Definitely the FDX project. It was a big shift for us — moving away from SBCP, a low-code platform where things like security and deployment were mostly handled for us, to building a full architecture from scratch. That meant taking ownership of everything: defining the FDX-compliant API framework, integrating Keycloak for security, designing data flows, and making key decisions on deployment, scalability, and performance.
It really pushed me to expand my skill set — not just in development, but also in DevOps and architecture. And beyond the technical side, what made it even more rewarding was the close collaboration within our small team. We had a great dynamic, regularly discussing ideas on the whiteboard, learning from each other, and making joint decisions. It was challenging, but incredibly fulfilling.
*FDX, or the Financial Data Exchange, is essentially the U.S. equivalent of open banking standards like those we see in Europe — for example, the Berlin Group.
Is there a technology, library, or tool that you find essential for working effectively on these topics?
Before diving into tools, I believe having the right mindset—being adaptable, solution-oriented, and understanding both technical and functional aspects—is key, especially in a fast-evolving space like open banking. That said, we currently use platforms like Amplify Fusion, a low-code/no-code tool that lets us rapidly build and iterate flows, significantly reducing time to market. We also leverage a centralized API marketplace that enables banks to securely expose their APIs and allows TPPs to onboard efficiently, creating a seamless experience for all stakeholders.
What does a typical day look like for you as a software developer?
In India, we follow a hybrid model — working three days from the office and two days remotely. Being on-site helps me stay closely connected with my team, collaborate more effectively, and actively participate in discussions and brainstorming sessions that directly contribute to the product’s success.
I genuinely enjoy the vibrant office culture. Over time, I’ve built strong friendships with colleagues, which makes the workday even more enjoyable. A typical day often starts with a coffee catch-up with a friend, and during breaks, we play a quick game of ping-pong or pool. These informal moments really help maintain a healthy work-life balance and foster a sense of community within the team.
Where do you think open banking will take us tomorrow, technically speaking?
Technically speaking, I see open banking evolving from basic data sharing to a more intelligent, real-time financial ecosystem. Today, we’re just scratching the surface—sharing data via APIs. But tomorrow’s open banking will focus on secure, real-time decision-making powered by AI and personalized services. This shift will demand high system performance, seamless orchestration, and strong security, especially for consent handling and SCA. Beyond banks, sectors like insurance, lending, and payments will increasingly benefit, expanding the scope and impact of open banking.
What’s the most important lesson you’ve learned so far?
The biggest lesson for me has been the value of adaptability. With the rapid rise of AI and constant shifts in technology, it’s clear that it’s no longer enough to specialise in just one tech stack or domain. I’ve come to realise that being a true contributor means staying open to learning — and sometimes even unlearning — in order to grow beyond defined roles.
I don’t want to be seen as “just” a Java backend developer. I want to be known as a problem solver — someone who can tackle any challenge, think critically, and deliver impactful solutions, regardless of the tools or technologies involved. That’s the kind of legacy I aim to build every day.
Do you have a memorable anecdote to share about your work or a particular project?
My first international trip to our Paris office was truly memorable. During a two-week workshop, we worked on designing a migration strategy from a legacy system to a new PSD2-compliant solution. Scope was quite extensive—it involved migrating third-party providers (TPPs), planning their onboarding journey to the new platform, and handling the migration of sensitive data like consents, tokens, and user credentials. It was a challenging and rewarding experience — full of deep collaboration, problem-solving, and the excitement of working face-to-face with the team (Nicolas de Genot , Ashwin Sharma…).
Would you like to join the SBS (ex-Sopra Banking Software) adventure? Discover all our job offers on our Careers page by clicking on this link.