Senior Software Engineer TLMT

Job Description

Currencycloudwas acquired by Visa in December 2021. The Treasury Liquidity Management Team is responsible for building the engine that determines where funds should be positioned at any given time to optimise liquidity across our global network. This engine will be designed using modern architectural principles, including event-driven approaches, to ensure scalability, resilience, and real-time decision-making.

As a Senior Software Engineer, you’ll play a key role in designing and implementing this engine. Your focus will be on delivering robust, performant solutions while collaborating with other engineers and stakeholders. While the architecture will leverage event-driven principles, your role will involve lightly advocating for these practices within the team rather than broad organisational evangelism.

Our stack runs on AWS as a set of distributed applications using Kubernetes and a microservice-led architecture. We are also utilising Kafka for our streaming and PACT for Contract testing.

• Design, develop, and maintain core services for the liquidity management engine using Java and related technologies.
• Implement event-driven patterns where appropriate to support real-time decision-making.
• Ensure high availability, scalability, and observability of critical components.
• Collaborate with cross-functional teams to understand requirements and deliver solutions that meet organisational needs.
• Contribute to continuous improvement in code quality, testing, and deployment practices.
• Support and advocate for event-driven architecture within the team as part of delivering the solution.

• Ownership of critical components within a high-impact financial system.
• Opportunity to work on complex, business-critical problems with real-world impact.
• A modern tech stack and autonomy to innovate.
• Strong organisational support and visibility for your work.

• Object-oriented programming forms the bulk of our codebase, currently in Java, versions 11+, and ideallySpringbootframework
• Highly-scalable, highly-available, cloud-native applications on AWS are key to our next phase of growth, are written to 12-factor principles and fit into our microservices architecture
• Cloud-related tools, services, and distributed system observability to support these applications, such as Docker, Kubernetes management systems, and Datadog APM, to name but a few
• API specifications, conforming to the OpenAPI (Swagger) standard, provide a clean boundary both externally between our customers and our product, and internally between our microservices
• SQL, and large SQL databases, provide the persistence layer for our applications. You’ll be working with (and know the limitations of using) such large data stores
• Infrastructure automation is primarily owned by the infrastructure team, but you will be a consumer of their work, familiarity with AWS, Terraform and Docker is beneficial
• Testing approaches, including TDD, BDD and Contract Testing, all form an important part of our approach to quality assurance, ensuring that the code that we write forms products that are fit for use. We currently use a variety of frameworks including JUnit,RSpecand Cucumber
• Agile development, with teams broadly aligned withads and Tribes - model, helps us deliver incremental improvements to our products in an iterative manner. Advocating this model, and joining us on a journey of continuous improvement, is a key attribute of members of our teams
• Continuous Integration and Continuous Delivery pipelines allow us to automate-all-the-things, providing repeatable builds and consistent deployments
• Git Hub, and the Git Hub PR review process, forms a core part of our developer workflow, and peer reviews help share knowledge and improve quality
• Teamwork, and cross-team collaboration, is fundamental to the delivery of our applications. Whilst each application has an independent path to production, there will always be some activities and initiatives that span multiple teams and require cross-team collaboration. Within your team you’ll need to collaborate with a number of stakeholders, including Product Owners and QA, as part…