We supply COBOL developers on z/OS, PL/I and Assembler developers, z/OS Connect API engineers and card-system specialists from Poland's bank-trained mainframe pool. You direct the work, we keep the team's capacity steady, and the first CVs reach you within 48 hours.
Half of UK banks rely on software that only one or two people at or near retirement understand, a Baringa survey of 200 banks found. The regulatory changes of 2027 land in that same code.
Five problems come up in almost every first call.
Decades of business rules live in programs that two people can read. Engineers who join now learn the estate while those people are still at their desks.
EU banks outside the euro area must receive instant euro payments from 9 January 2027 and send them, with Verification of Payee, from 9 July 2027 (Regulation (EU) 2024/886). On a mainframe core that means posting around the clock.
Channels and partners need mainframe transactions as REST services. z/OS Connect engineers expose CICS and COBOL programs without rewriting them.
AI migration tools now translate COBOL at scale. A COBOL engineer confirms the new code behaves like the old before it reaches production.
Issuing and acquiring on VisionPLUS or CardPac needs people who know COBOL, CICS and the card lifecycle together.
Eight profiles, matched to your stack role by role.
AI tools translate and document mainframe code, and an engineer who knows the original signs off that the new system behaves the same.
In September 2026 Thought Machine and AWS announced a pipeline that turns mainframe COBOL into tested banking products. AWS describes the method as human-in-the-loop validation: at each review gate the bank's domain, risk and technology teams confirm how the business logic was read. A migration team needs four roles.
Reads the legacy program and confirms the translated logic, edge cases included.
Owns the target code: its structure, its performance and its place in your architecture.
Builds the harness that runs old and new side by side and compares every output.
Runs and tunes the translation tooling. We place AI engineers only from step four of our AI ladder: production experience, not demos. AI engineers →
The mainframe stays because it posts every transaction, every night, at a scale and reliability banks have built their books on.
Forty-five of the world's 50 largest banks still run mission-critical applications on the mainframe (AWS, May 2026).
End-of-day batch, interest and settlement for millions of accounts run in fixed windows, while online transactions post around the clock.
Product, fee and regulatory logic sits in COBOL that has been extended for decades. In the Baringa survey, 16% of UK banks still run code from the 1960s and almost 40% maintain code from the 1970s.
IBM ended standard support for z/OS 2.5 on 30 September 2026 (IBM lifecycle), so estates move to z/OS 3.1 and 3.2. Upgrades need systems programmers alongside the application teams.
The work is steady and the people are scarce. Running a packaged core next to the mainframe? See our core banking specialists.
Five steps, and the first takes 30 minutes.
Banks buy engineering capacity from us under tenders and framework agreements.
Placements last 2.6 years on average, and half of our people have been with us since NDS started in 2019.
In 30 minutes we map which roles you need, how many people and from when. You leave the call with a staffing plan and the date the first CVs arrive.
Book a 30-minute callCOBOL, PL/I, z/OS or Natural engineer: leave your CV and we will call when a bank needs your experience.
In Poland. The country has a mainframe pool trained in bank central-system teams and in global banks' Polish technology hubs. New Digital Street recruits from that pool and places COBOL, PL/I and z/OS engineers in your team, working remotely in Central European Time. First CVs arrive within 48 hours of agreeing the skill map.
Yes. Engineers connect through your own secure access, work in your tools and follow your change and security procedures. Poland is on Central European Time, one hour ahead of London, so the working day overlaps almost fully. Your team directs the work and runs the interviews; we look after contracts, start dates and continuity.
By adding engineers while the people who know the code still work there. In a Baringa survey of 200 UK banks, half relied on software that only one or two staff at or near retirement understand. Banks pair incoming COBOL engineers with those experts, document the programs as they go, and spread support across more than two names.
No. AI tools translate and document COBOL quickly, and the migration still needs someone who can read the original and confirm the new code behaves the same. AWS describes this as human-in-the-loop validation with review gates. The engineer who signs off is the one who can explain why the old program did what it did.
Four roles carry it. A COBOL reviewer reads the legacy logic. A Java engineer owns the target code. A test and data engineer runs old and new systems side by side and compares outputs. An AI engineer runs the translation tooling. We supply each role on its own or as a group that joins your programme under your architects' direction.
Yes. Mainframe API and integration engineers expose CICS transactions and COBOL programs as REST services through z/OS Connect, and connect them to channels over IBM MQ. They work to your API standards and security model, so digital teams call mainframe functions like any other service.
Yes. We source card-system specialists who combine COBOL, CICS and VSAM with the card lifecycle: authorisation, clearing, settlement and billing. They join issuer and acquirer teams for scheme mandates, product changes and production support. Tell us the platform and release in the first call and the skill map follows it.
First CVs arrive within 48 hours of agreeing the skill map. Interviews follow at your pace, and engineers start on the date set in the team plan. The first step is a 30-minute call where we fix the systems, the number of people and the start date.
You get a free replacement from our bench within days. The same people stay on the project to the deadline; we never swap them for someone cheaper or more junior. Placements with us last 2.6 years on average, which matters on systems where knowledge takes months to build.
Because the mainframe posts every transaction reliably at a scale few platforms match. Forty-five of the world's 50 largest banks still run mission-critical applications on it, and decades of product and regulatory rules live in COBOL. Banks modernise around that code: APIs, phased migrations and platform upgrades.
Sources: Baringa survey of 200 UK banks, Computer Weekly, Sep 2025 · Regulation (EU) 2024/886 · IBM z/OS 2.5 lifecycle · AWS for Industries, 22 May 2026 · Thought Machine and AWS, 29 Sep 2026
Updated 18 November 2026
Put a slot in a calendar, or send the brief and we will come back to you. Either way you are talking to a partner, not a queue.
Thirty minutes, no deck. Pick the one who handles your side — he takes the call himself.
Roles, platform, headcount, timeline. A link to a brief is even better.