No COBOL or mainframe jobs available right now.
Leave your email and we'll notify you as soon as new opportunities are listed:
There are roughly 220 billion lines of COBOL running in production right now, processing about $3 trillion in transactions every day. It is not a historical curiosity — it is the layer your paycheck clears through. This page collects remote, hybrid, and contract COBOL and mainframe roles open to US-based applicants: application developers, systems programmers, AS/400/RPG specialists, and the modernization engineers hired to move it all somewhere newer.
The reason these jobs pay well is unglamorous arithmetic. The average working COBOL developer is now over 55, the median closer to 60, and about 10% of that workforce retires every year. Meanwhile 85% of universities dropped COBOL from the curriculum in the 1990s. Nobody is replacing them at the rate they're leaving, which is why 60% of organizations say finding qualified developers is their single biggest challenge — and why recruiters report these roles take two to three times longer to fill than comparable ones, with some staying open six months or more.
The practical upside for you: because the work happens through terminal emulators and cloud-hosted dev environments, it moved to remote more completely than most enterprise engineering. Geographic pay compression is weaker here than in the rest of tech, so a developer in a low-cost metro can hold a salary benchmarked to a financial center.
One honest note up front. This work is maintenance-heavy and the codebases are old, sprawling, and under-documented. If you want greenfield projects and a modern toolchain, this is not that. What it offers instead is scarcity, stability, and employers who cannot easily replace you.
Types of COBOL and mainframe jobs
"COBOL job" covers several distinct roles with very different day-to-day work:
COBOL application developer. The core role — maintaining and extending business logic for banking, claims, billing, or benefits systems. Expect to work with JCL, DB2, CICS, and VSAM alongside COBOL itself. Most postings list these together, and the surrounding stack matters as much as the language.
Mainframe systems programmer. Looks after the z/OS environment itself rather than the applications on top of it — installs, tuning, capacity, and recovery. Deeper and more specialized than app development, and paid accordingly (commonly $140,000–$175,000).
AS/400 (IBM i) and RPG developer. A parallel legacy world to z/OS mainframes. AS/400 runs general ledger, payroll, inventory, and multi-location accounting for a lot of mid-market companies, typically in RPG, CL, and COBOL/400. Frequently advertised as its own specialty, and worth watching separately.
Modernization / migration engineer. The growth area. Organizations moving off the mainframe need people who understand the legacy system well enough to translate it safely — which means reading COBOL, not just writing its replacement. These hybrid roles often pay more than pure development, because they need both sides.
Mainframe QA and production support. Batch scheduling, job failures, and testing. Lower barrier to entry than development, and a common way in the door for people who want to move to development later.
Contract and consulting engagements. A large share of this market is contract. Standard rates run $75–$125/hour, specialized mainframe work $125–$200/hour, and genuine emergency work above $200/hour. Many engagements are 12+ months with conversion to permanent on the table.
How much do COBOL and mainframe jobs pay?
Averages vary by source, which is worth understanding rather than glossing over. Glassdoor puts the average mainframe COBOL developer at $125,525; Salary.com's figure for "mainframe COBOL programmer" is $95,859; ZipRecruiter lands at $111,026. The spread is mostly job-title drift — "programmer" postings skew toward maintenance and support, "developer" and "engineer" toward design work. Read the responsibilities, not the title.
By experience, full-time US ranges look like this:
- Entry-level (0–2 years): $75,000–$95,000
- Mid-level (3–7 years): $95,000–$130,000
- Senior (8+ years): $130,000–$160,000+
- Architect / technical lead: $150,000–$185,000+
- Mainframe systems programmer: $140,000–$175,000
For context, mid-level COBOL developers typically earn $5,000–$20,000 more per year than Python developers at comparable experience in the same market. That premium is not about the language being better — it is scarcity pricing, and it is the whole reason this niche is worth your attention.
On contract rates. Hourly work is common and often pays better than salary on paper: $75–$125/hour standard, $125–$200/hour for specialized mainframe work. Before comparing that to a salary, price in the things it doesn't include — health coverage, paid time off, employer payroll taxes, and the gap between engagements.
The clearance premium. Some government COBOL roles require an active Secret clearance. If you already hold one, say so early; it materially narrows the candidate pool in your favor.
How to break into COBOL without prior mainframe experience
This is the question that stops most people, and the honest answer is that it's harder than a bootcamp pipeline but easier than the salaries suggest — precisely because employers cannot find people. About 76% of mainframe developers hold a bachelor's degree, which also means roughly a quarter do not. Realistic routes in:
- IBM Z Xplore. Free access to a real mainframe with digital badges you can put on a résumé. The closest thing to a standard credential for someone with no professional exposure.
- GnuCOBOL. The open-source COBOL compiler runs on Windows, Linux, or macOS at no cost. You can learn the language on your own hardware today; you don't need a mainframe to start.
- Employer training programs. The most reliable path. Banks and consulting firms run 8–16 week paid training because the market gave them no alternative. IBM, Accenture, Deloitte, Cognizant, and Infosys all hire into these.
- Community college mainframe certificates. Several run COBOL and z/OS programs, often with direct employer relationships attached.
- Production support as a side door. Batch monitoring and QA roles have a lower bar and put you next to the codebase. Moving to development from there is a well-worn path.
- A public portfolio. Rarer here than in web development, which is exactly why a GitHub repo with real COBOL in it stands out to a hiring manager who has seen nothing but empty pipelines.
One safeguard worth repeating. Because paid training is genuinely common in this field, it's also a convenient cover story for scams. A legitimate employer pays you during training and provides your equipment. Anyone who asks you to pay for certification, buy your own gear up front, or send money for a background check is running a scam — regardless of how real the company website looks.
Isn't AI about to make all of this obsolete?
It's the first thing anyone asks, and it deserves a straight answer rather than reassurance. So far, AI has increased demand for COBOL knowledge rather than removed it.
The reason is what these systems do. When code moves $3 trillion a day and clears 95% of ATM transactions, "the model translated it and the tests mostly passed" is not an acceptable standard. Someone has to understand the original well enough to know what the translation broke — and that person has to be able to read COBOL. Tools like IBM watsonx Code Assistant for Z are real and useful, but what they change is who can work on a large COBOL codebase, not whether anyone needs to. They lower the barrier to entry, which is good news if you're trying to get in.
The migration wave points the same direction. Every organization trying to leave the mainframe needs people who can read what's there before it can be replaced — and modernization work is a decade-long program at most institutions, not a weekend project. The realistic risk to this career isn't that AI writes COBOL; it's that a specific employer finishes its migration and the role ends. That's a normal job risk, and it's mitigated the normal way: keep the modernization skills alongside the legacy ones.
More remote jobs by category
COBOL & mainframe jobs — FAQ
Is COBOL a dead-end career in 2026?
The numbers say the opposite. Around 75% of the current COBOL workforce is expected to retire within 10–15 years, and 60% of organizations name finding qualified developers as their single biggest challenge. Recruiters report these roles take two to three times longer to fill than comparable ones, with some staying open six months or more.
Will AI replace COBOL developers?
So far it's doing the reverse. Tools like IBM watsonx Code Assistant for Z help developers read large COBOL codebases faster, but organizations still need people who understand the legacy system to oversee AI-assisted modernization and check translated code before it touches production.
Can I get a COBOL job without COBOL experience?
It happens, usually through employer training. Banks and consulting firms run 8–16 week paid training programs, IBM's Z Xplore gives free mainframe access with digital badges, and the open-source GnuCOBOL compiler runs on Windows, Linux, or macOS at no cost. A legitimate employer never charges you for training or equipment.
What do COBOL jobs pay?
Entry-level (0–2 years) generally runs $75,000–$95,000, mid-level (3–7 years) $95,000–$130,000, and senior (8+ years) $130,000–$160,000+, with architects and leads at $150,000–$185,000+. Contract rates run $75–$125/hour and higher for specialized mainframe work. Because much of it is remote, pay is often benchmarked to financial-center rates regardless of where you live.
Is a COBOL job worth pursuing?
If you want to work on something new, no. If you want leverage, this is one of the few corners of software where the supply of people is falling faster than the demand for the work — and where that gap shows up directly in what you're paid, how long employers wait for you, and how much of the job you can do from home. The code isn't going anywhere on any timeline that matters to your career: 220 billion lines don't get rewritten because a press release says "modernization."
Check the listings above, and if you're starting from zero, start with GnuCOBOL this week and IBM Z Xplore after that. The people hiring for these roles have been looking for six months. They are not a hard audience to reach.