Skip to main content

Senior Java Technical Lead - Payment

Posted 2 days ago

resource logisticsEdison (NJ)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

We are seeking a Payments Backend Developer. The candidate should have 8 years and above strong experience in Java backend development, microservices, Kafka/MQ, cloud-native applications, and payment processing platforms. Payments Domain Experience (Mandatory): Wire Payments, RTP, Fedwire, SWIFT, ISO 20022, Treasury Payments, Cross-Border Payments, Payment Hubs, or High-Value Transaction Processing.
Key Responsibilities: Develop and maintain Java microservices and payment applications Build scalable APIs and event-driven solutions Support payment modernization and cloud migration initiatives Collaborate with cross-functional teams throughout the SDLC Support deployments, production issues, and continuous improvementIdeal candidate: A hands-on backend engineer with strong payments expertise and experience building scalable, high-performance banking applications.
Key Skills: Java 11/17/21, Spring Boot, REST APIs, Microservices Kafka, IBM MQ, Event-Driven Architecture Oracle/PostgreSQL/MongoDB OpenShift, Kubernetes, Docker CI/CD, Jenkins, Git, Azure DevOps

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this