Mainframe / COBOL Developer Recruiters

No upfront fee
Pay only if you hire
Technology only
We reach engineers who aren't on job boards
Replacement guarantee on standard searches

Mainframe Programmerz/OS DeveloperMainframe Programmerz/OS Developer

What this hire really comes down to

Hiring a mainframe developer is hiring for systems that quietly run payments, policies, claims and benefits. Buyers come to us because the people who wrote and understood these programs are retiring, because modernization projects need someone who can read the old logic, or because a batch window cannot afford a misunderstanding. The scarcity is real, but the answer is rarely panic. It is careful selection of people who combine patience, domain knowledge and respect for change control.

Environment matters. In banking, insurance and government IT, programmers maintain large COBOL estates with JCL driven batch cycles and CICS online transactions, backed by DB2 or IMS data. Work is often enhancement and defect resolution, with tight testing procedures and formal release windows. In mainframe modernization consultancies, the work is analysis, extraction of business rules, re-platforming and testing against the legacy results. These are different jobs, and the second demands more explaining to non specialists.

Core technical evidence includes fluency in COBOL data divisions and copybooks, JCL for job streams including conditions and restarts, and CICS for transaction flow. DB2 skill means embedded SQL and understanding of locks and plans; IMS means hierarchical data thinking. A candidate should be able to describe reading an abend, finding the failing step and correcting data safely, because that is daily reality.

What we check before you see anyone

COBOL
Ask them to describe a program they modified: the files and copybooks involved, the logic change and how they tested it. Strong candidates explain business effect, not only code changes.
JCL
Probe job steps, condition codes, restart logic and handling of a failed overnight job. Ask how they decide whether to rerun, restart or fix data first.
CICS and DB2 or IMS
Ask about transaction design, screen maps or services, and how they resolved a locking or performance issue. For IMS, probe segment handling and database calls.
Modernization project exposure
Ask what they contributed: rule extraction, testing against production output, interface building. Partial exposure still counts if they can explain the lessons.

Send Us Your Open Role Book a 15-minute call with Ivan Call 305-306-4829

Where we find them

Banking, insurance and government IT groups are the principal pool. These developers have deep domain knowledge and respect for controlled release. Many are long tenured and need a strong reason to move, including clarity about modernization plans and stability.

Mainframe modernization consultancies offer people used to reading unfamiliar code quickly and working with business stakeholders on rule discovery. They bring broader tooling awareness, but check depth of hands-on COBOL maintenance.

Another pool is retired or semi retired specialists open to contract support, and graduates from mainframe training programs who can be developed. Both need clear expectations about knowledge transfer.

Mistakes we see

Treating a credential as the answer
Do not let cobol become a keyword filter. Strong candidates explain business effect, not only code changes.
Leaving the actual scope out
Put the responsibility for jcl in the brief, including who helps the hire and who decides. Probe job steps, condition codes, restart logic and handling of a failed overnight job.
Waiting until the offer to discuss the work
Discuss what the person will own in cics and db2 or ims before the interview loop. For IMS, probe segment handling and database calls.

The search in three steps

Agree the brief
We start by asking what the mainframe does for you and what is changing. A maintenance hire, a knowledge transfer role and a modernization analyst each need distinct profiles.
Find and speak with people
Screening centers on a conversation about real programs and failures. We listen for caution, documentation habits and the ability to teach.
Introduce the people who fit
We send a written brief on each person you meet, including why the work fits and the questions still worth asking about modernization project exposure. You decide who to interview. We help with the conversations through the offer.

Red flags include an unwillingness to document, vague descriptions of testing, and resistance to any change in tooling such as source control or modern editors. Good evidence includes a modernization exposure story, even in a minor capacity, and an ability to explain business rules in plain language. Younger candidates who trained through academic programs are real options, provided mentoring is available.

Knowledge transfer deserves explicit planning. A new hire will rarely understand decades of accumulated logic from documentation alone, so pair them with a retiring expert if possible, and set aside time for reading code, tracing batch flows and learning why strange conditions exist. Employers who treat this as an investment retain people; those who expect immediate independence lose them. Be open about your tooling as well, including whether editors, source control and testing environments are modern, because candidates weigh that heavily when choosing between offers.

The difficult part can be understanding why an old batch job exists. Give the hire access to the people who know the business rule, not just the source code. We ask candidates how they traced an unfamiliar COBOL program and checked its dependencies before changing it. A quick edit that disrupts the overnight run is not progress, even if the code review looks clean.

Questions about this search

When will we see a shortlist?

We agree the search plan after checking your requirements for cobol and jcl, rather than promising a date before the brief is clear. Ask them to describe a program they modified: the files and copybooks involved, the logic change and how they tested it.

What if a candidate gets a counteroffer?

We ask what would make someone leave work involving cobol, and what could make them stay. Before you invest in interviews, we discuss whether your offer changes the problem they want to leave, including the responsibility for modernization project exposure.

Should this role be remote or on site?

Experience with cobol and jcl does not settle the location question. Tell us what access and supervision the work needs, including who owns decisions about modernization project exposure, so we approach people who can accept the arrangement.

How will you check fit before we interview?

Ask them to describe a program they modified: the files and copybooks involved, the logic change and how they tested it. Strong candidates explain business effect, not only code changes. Probe job steps, condition codes, restart logic and handling of a failed overnight job.

How does the fee work?

No upfront fee. You pay only if you hire. Agree the fee and the responsibilities covering cobol and jcl in the recruiting agreement before the search proceeds.

What if the hire does not work out?

We offer a candidate replacement guarantee on standard search agreements. The applicable period and exact terms are set out in the signed client recruiting agreement. Make sure the agreed scope includes what you expect of modernization project exposure, rather than leaving that discussion until after the start.

Pay snapshot