You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
Capco

Full Stack Engineer (Java & React)

  • Hybrid

Salary

Not stated

Similar roles pay €60K - 95K a year · our estimate

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

CAPCO POLAND - WARSAW

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.

Role Overview

We are seeking React / Java Full Stack Engineer to join our Global Asset Servicing Platform team. This is a hands-on engineering role where you will design, build, and test features end-to-end – with full ownership of code and quality.

You will work across development and test automation: coding new functionality, writing unit and integration tests, and adding Cucumber-based end-to-end tests – not only for your own work but also for features built by your teammates, to ensure unbiased validation.

The ideal candidate will be skilled in Java backend development and modern UI development using React. This role will work across the full stack to build a scalable, reliable, and user-friendly application.

Responsibilities

  • Design, develop, and maintain features using Java and React .
  • Build responsive and modern frontend applications using ReactJS,
  • Develop and integrate APIs and web services.
  • Experience working with relational databases (Oracle, Postgres)
  • Write clean, well-structured unit tests (JUnit or equivalent) alongside your code.
  • Contribute to and maintain our automated test framework using Ruby and Cucumber :
  • Write new Ruby step definitions as needed.
  • Create and maintain Cucumber feature files for end-to-end testing.
  • Write automated tests for features developed by other engineers , ensuring high-quality outcomes and reducing development bias.
  • Champion a test-first approach , delivering code that is reliable, maintainable, and scalable.
  • Apply performance and scalability considerations; use tools such as JMeter for load/performance testing where required.
  • Ensure instrumentation, configuration, and logging are embedded in code to support ongoing monitoring and support.
  • Analyse and debug issues using logs; propose and implement fixes.
  • Collaborate in Agile ceremonies, helping the squad plan effectively and commit to clear sprint goals.
  • Partner with product managers and analysts to understand what is being built, why it matters, and how best to implement it for both functional and non-functional needs.
  • Build with a product mindset – appreciating client impact, configurability, and long-term supportability.

Requirements

  • Technical Skills
  • Proficiency in:
  • Java (with strong JUnit testing experience)
  • React (with associated unit testing frameworks)
  • Familiarity with automation frameworks & languages:
  • Ruby scripting (nice to have) for step definitions
  • Cucumber for end-to-end testing
  • Strong understanding of:
  • Multi-threading, parallel processing, and real-time messaging
  • Test-first design, CI/CD practices
  • Ability to use JMeter or similar tools for performance testing (a plus)
  • Basic understanding of cloud services : databases, servers, storage, gateways (not at architect level, but practical awareness of hosting environments).
  • Experience using AI-assisted engineering tools (such as GitHub Copilot, ChatGPT, or similar) to accelerate coding, testing, debugging, and documentation, while maintaining code quality and critical thinking.
  • Functional / Domain Knowledge
  • Familiarity with financial markets concepts.
  • Knowledge of corporate actions lifecycle preferred.
  • Soft Skills
  • Strong analytical and debugging abilities.
  • Clear communicator, able to articulate trade-offs and solutions to both technical and business audiences.
  • Collaborative team player, comfortable working in agile, cross-functional squads .
  • Curious and thoughtful: able to look beyond the ticket to understand requirements, impact, and broader context.
  • Product mindset — balancing immediate delivery with long-term maintainability and client impact.
  • 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

Where you’d work

Part of the week in the office

About the company

Capco

Office in Warsaw, Poland

Also hiring in Brussels, Belgium, Prague, Czechia, Houston, United States and 14 more places

3 of their 63 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 19 checks run
  • 1 red flag

Still hiring?

13 checks

No red flags

How crowded?

6 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details9 facts · Role, Location, Compensation, Employment
Tech stack
  • React
  • Java
  • PostgreSQL
  • Ruby
  • CI/CD
Type
Contract
Specialty
Fullstack
Region
Europe
Pay period
Annual
Show 4 more factsShow less

Role

Category
Development
Specialty
Fullstack
Tech stack
  • React
  • Java
  • PostgreSQL
  • Ruby
  • CI/CD

Location

Work model
Hybrid
Region
Europe
Office
  • Warsaw, Poland

Compensation

Salary
Salary by agreement
Pay period
Annual

Employment

Type
Contract

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason