IBM Integration Bus (IIB) Developer- Role - Hybrid - Banking

London
10 months ago
Applications closed

Related Jobs

View all jobs

Data Engineer

Data Engineer - SC Cleared

Data Engineer - Active SC required

Data Engineer - Active SC required

Data Engineer - Active SC required

IBM Integration Bus (IIB) Developer - Tier 1 Bank - 6 month contract - Hybrid

IIB / IBM / ACE / MQ / MIDDLEWARE / BANKING

Role - IBM Integration Bus (IIB) Developer

Duration - 6 months

Location - Remote / Canary Wharf, London - 3 days per week in the office in Canary Wharf, London.

Rate - £415 per day (Inside IR35)

Key Experience -

The IBM Integration Bus (IIB) developer will be responsible for development of new (as well as maintenance of existing) message flows, DFDL message models and other interface processes, which form part of the Bank's application internal and external interfaces.
Production support of existing interface processes, including troubleshooting and investigation of any issues relating to these processes.
Obtaining a high-level of understanding of relevant Middleware applications.
Obtaining a high-level of understanding of all projects being undertaken.
Responsible for designing and developing message flows and message models as part of the Bank's Interface Team.
Responsible for troubleshooting issues and assisting with code reviews to ensure optimal solutions are being delivered.
Responsible for new development, ongoing maintenance, and Production support of all the Bank's application, both internal and external interfaces.
Responsible for developing and maintaining interfaces between the Bank's applications, which are pivotal to the Bank's operations in both Europe and North America. The ideal candidate will have some experience in IBM ACE/IIB.
Work with various application team members and developers from other teams to perform their development work and they will be responsible for maintenance and support of the existing interface processes including investigation of issues and production support for the Bank's operations.Skills -

Solid experience with IBM Integration Bus v9 or higher(Preferably ACE 12), IBM MQ v8.0 or higher, MQFTE v7.0 or higher
Experience working with API Connect/Azure API Management & Apache Kafka
Experience in developing Message Sets and Message Definitions using XML, MRM and TDS formats.
Experience in developing message flows using Compute Nodes, SOAP Nodes, HTTP Nodes, Routing Nodes, Mapping Nodes, Java Compute Nodes, File Nodes (Input, Output, Read & Write) and Database Nodes.
Experience in Programming Languages: Korn Shell scripts, PERL, Java, Ant, SQL, ESQL.
Experience in working with Operating systems such as UNIX (AIX), Linux, Windows.
Experience in working with Databases such as Oracle 10G, 11i, PL/SQL, Stored Procedures.

GCS is acting as an Employment Business in relation to this vacancy

Subscribe to Future Tech Insights for the latest jobs & insights, direct to your inbox.

By subscribing, you agree to our privacy policy and terms of service.

Industry Insights

Discover insightful articles, industry insights, expert tips, and curated resources.

Careers

How Many Data Engineering Tools Do You Need to Know to Get a Data Engineering Job?

If you’re aiming for a career in data engineering, it can feel like you’re staring at a never-ending list of tools and technologies — SQL, Python, Spark, Kafka, Airflow, dbt, Snowflake, Redshift, Terraform, Kubernetes, and the list goes on. Scroll job boards and LinkedIn, and it’s easy to conclude that unless you have experience with every modern tool in the data stack, you won’t even get a callback. Here’s the honest truth most data engineering hiring managers will quietly agree with: 👉 They don’t hire you because you know every tool — they hire you because you can solve real data problems with the tools you know. Tools matter. But only in service of outcomes. Jobs are won by candidates who know why a technology is used, when to use it, and how to explain their decisions. So how many data engineering tools do you actually need to know to get a job? For most job seekers, the answer is far fewer than you think — but you do need them in the right combination and order. This article breaks down what employers really expect, which tools are core, which are role-specific, and how to focus your learning so you look capable and employable rather than overwhelmed.

Jobs

What Hiring Managers Look for First in Data Engineering Job Applications (UK Guide)

If you’re applying for data engineering jobs in the UK, the first thing to understand is this: Hiring managers don’t read every word of your CV. They scan it. They look for signals of relevance, credibility, delivery and collaboration — and if they don’t see the right signals quickly, your application may never get a second look. In data engineering, hiring managers are especially focused on whether you can build and operate reliable, scalable data systems, handle real-world data challenges and work effectively with analytics, BI, data science and engineering teams. This guide breaks down exactly what they look at first in your application — and how to shape your CV, portfolio and cover letter so you stand out.

Education

The Skills Gap in Data Engineering Jobs: What Universities Aren’t Teaching

Data engineering has quietly become one of the most critical roles in the modern technology stack. While data science and AI often receive the spotlight, data engineers are the professionals who design, build and maintain the systems that make data usable at scale. Across the UK, demand for data engineers continues to rise. Organisations in finance, retail, healthcare, government, media and technology all report difficulty hiring candidates with the right skills. Salaries remain strong, and experienced professionals are in short supply. Yet despite this demand, many graduates with degrees in computer science, data science or related disciplines struggle to secure data engineering roles. The reason is not academic ability. It is a persistent skills gap between university education and real-world data engineering work. This article explores that gap in depth: what universities teach well, what they consistently miss, why the gap exists, what employers actually want, and how jobseekers can bridge the divide to build successful careers in data engineering.

🍪 We use cookies to enhance your browsing experience on our website. By continuing to use this site, you consent to the use of cookies as described in our Cookie Policy. You can review our Cookie Policy for more information.