Software Engineer; Mid-Level; TRLO

Job Description

Currencycloud was acquired by Visa in December 2021. This role sits within Visa’s Treasury function, which is responsible for managing global liquidity, cash flow, and risk to keep payments moving smoothly across markets. Treasury ensures funds are available where needed and supports critical processes like settlements and foreign exchange. As part of this team, you’ll help build reliable, scalable systems that underpin these operations and enable real‑time visibility and control.

• Develop and maintain backend services and tooling using Java (11+) and Spring Boot, integrating with Kafka, Flink, and related technologies.
• Build frameworks and reusable components that simplify consumption of real‑time data capabilities for other teams.
• Implement reliability, scalability, and observability features (metrics, logs, tracing) for platform components.
• Work with cross‑functional partners to understand requirements and deliver incrementally in Agile squads.
• Contribute to code reviews, testing, documentation, and CI/CD pipelines.
• Support event‑driven architectures by applying patterns and communicating practical benefits to partner teams.

• Clear ownership of your domain
• A clean modern codebase
• An independent path to production
• Strong platform and product support
• The ability to make real changes with real business value.

• Object‑oriented programming forms the bulk of our codebase, currently in Java, versions 11+, and ideally Spring Boot framework.
• 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, Elastic Search, log 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, RSpec and Cucumber.
• Agile development, with teams broadly aligned with the Spotify - Squads 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 of your product development.

Preferred Qualifications:

• Some experience in Java backend (Spring Boot 2.x/3.x preferable)
• Skills with functional Java (versions 8+) and Spring (ideally Spring Boot)
• Agile ways of working such as Scrum or Kanban in cross‑functional teams
• Expert knowledge of Docker, EKS, AWS (public cloud) and Kafka
• Ability to communicate equally effectively with both technical and non‑technical stakeholders
• Modern Cloud‑Native architectures and practices. To name…