Java Integration Developer

Build the GCP-based Integration Layer

• Design and implement API-based, event-based, and batch/file-based integrations.
• Develop services and workflows either GCP native components:
  • Cloud Pub/Sub (async messaging & decoupling)
  • Cloud Storage (GCS) (file landing zones)
  • Cloud Composer / Workflows (orchestration)
  • Cloud Functions / Cloud Run (microservices & serverless)
  • Apigee / API Gateway (API exposure layer)
• Or IBM MQ, IBM Sterling, Kafka,  Or experience on workflow orchestrator tools like Camunda.
• Govern the use of middleware, messaging queues (e.g., Kafka, MQ), and transformation engines (e.g., UDF) to ensure consistency and reusability.

Integration Development

• Build adapters for:
  • File transfers (SFTP, FTPS, managed transfer via GCP Transfer Service)
  • SWIFT messages (MT/MX), ISO20022 translations
  • Queue-based integrations (JMS, MQ → Pub/Sub bridges)
  • Event-driven flows between systems like FNZ, Calypso, BNP.
  • Kafka integrations
  • Migrate existing point-to-point logic into centralized, Standardized services.

Implement Transformations

• Write transformation Rules  (Avro, Jolt, XML/JSON/CSV/ISO → target schema).
• Implement validation, enrichment, and business rules.

DevOps And Automation

• Use CI/CD (Cloud Build, GitHub Actions, Jenkins).
• Ensure logging, monitoring, alerts using Cloud Logging & Cloud Monitoring.

Work with Cross-Functional Teams

• Collaborate with FO/MO/BO SMEs, FNZ/Calypso/BNP vendor teams.
• Understand upstream/downstream data models and event triggers.
• Debug issues in a distributed multi-system environment.

Required Skills And Technologies

Core Languages

• Java
• Python

Integration And Messaging

• MQ / JMS
• SFTP / MFT
• Kafka
• SWIFT MT/MX
• ISO20022 messages
• REST/JSON/SOAP/XML

Preferred Background

• Banking or wealth domain experience: trades, corporate actions, settlements, custody, accounts, securities, static data.
• Experience integrating with platforms like:
  • FNZ
  • Calypso
  • BNP
  • Custody systems
  • IBM MQ on OpenSystem
  • File transfer between Cloud and Mainframe

• Experience moving legacy point-to-point flows into modern integration layers (both Cobol-to-cobol, MQ, file based)