Back-End Engineer - Java (Payments)

Capco is hiring a Back-End Engineer - Java (Payments) in Warsaw, Poland. Level rates it ; you can apply on Capco.

Level's read on this job

Little AI ●○○○ is how Level rates this role: aI is not part of the work.
Level classes it as a senior role.
Capco has 702 other open roles on Level.
Posted within the past two weeks.

AI in this role

CAPCO POLAND

*We are looking for Poland based candidate.

At Capco Poland, we’re not just another consultancy - we’re the spark behind digital transformation in the financial world. As a global leader in technology and management consulting, we thrive on helping clients tackle the toughest challenges across banking, payments, capital markets, wealth, and asset management.

Build scalable, secure back-end solutions and help shape the future of payment technology.

The Role

At Capco, we're looking for an experienced Back-End Developer to provide specialist development services for a project within the financial services and payments industry. You'll collaborate with the Team, contributing to the design, development, and enhancement of modern back-end applications and services supporting business-critical payment solutions.

This engagement offers the opportunity to apply your Java and Spring Boot expertise, work with PostgreSQL and AWS cloud technologies, and deliver reliable, scalable, and high-performance solutions within a collaborative engineering environment.

What You’ll Do

Design, develop, and deliver scalable, secure, and high-quality back-end services using Java 25 and Spring Boot 4.
Collaborate with the Agile Team, including developers, product owners, QA engineers, and other stakeholders, to coordinate technical activities and deliver agreed project outcomes.
Develop and maintain RESTful APIs, microservices, and integrations with PostgreSQL databases and AWS cloud services.
Deliver clean, maintainable, and testable code, contributing to technical reviews and applying established engineering standards.
Analyse and resolve technical challenges, optimise application and database performance, and contribute to improvements in system reliability, security, and scalability.

What We’re Looking For

Around 5–10 years of hands-on expertise in Java and Spring Boot, including knowledge of Java 25 and Spring Boot 4.
Strong understanding of object-oriented programming, microservices architecture, RESTful APIs, and modern back-end development principles.
Practical experience with PostgreSQL, including database design, SQL query optimisation, and efficient data management.
Hands-on experience with AWS cloud services and developing or integrating cloud-based applications.
Ability to deliver technical solutions independently while collaborating effectively with cross-functional teams in Agile or Scrum project environments.

Bonus Points For

Experience delivering technology solutions within financial services, payments, or transaction-processing environments.
Familiarity with AWS services such as ECS, EKS, Lambda, RDS, S3, or CloudWatch.
Experience with containerisation technologies such as Docker and Kubernetes, alongside CI/CD pipelines and automated deployment processes.
Knowledge of automated testing frameworks such as JUnit, Mockito, and integration testing tools.
Understanding of event-driven architecture, messaging technologies such as Kafka, and application monitoring and observability practices.

B2B cooperation in a hybrid model, with the option to provide services from the Warsaw office to the extent agreed based on project needs.

Recruitment Process:

HR Interview with the recruiter
Technical Interview
Client Interview
Feedback and offer

#LI-HYBRID

How we rate this

Back-End Engineer - Java (Payments) at Capco rates 35 out of 100 for how much of the daily work is AI. That makes it Little AI (AI Level 1 of 4). The level is about AI in the job, not seniority.

Classification

Little AI. AI is not part of the work.

●●●● Builds AI80 to 100
●●●○ Works on AI60 to 79
●●○○ Uses AI40 to 59
●○○○ Little AI0 to 39

Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.