We source, vet, and manage hiring so you can meet qualified candidates in days, not months. Strong English, U.S. time zone overlap, and compliant hiring built in.
.svg){kind=logo}
PL/I (Programming Language One) is a high-level compiled language designed by IBM in the 1960s to unify the features of FORTRAN, ALGOL, and COBOL into a single language for both business and scientific computing. It compiles to machine code and runs on mainframes and other platforms.
PL/I was ahead of its time: it supported structured programming, exception handling, modular code, and powerful I/O operations decades before these features became standard in mainstream languages. For its era, it was remarkably sophisticated.
Today, PL/I is primarily a legacy language. Millions of lines of PL/I code run in production on mainframes worldwide, particularly in banking, insurance, government, and telecommunications. You don't learn PL/I to build new systems. You learn it to maintain, extend, and migrate existing systems that have been delivering value for 30, 40, or 50 years.
You hire PL/I developers for legacy system maintenance and modernization. There are very few new PL/I systems being built.
Mainframe System Maintenance: If your organization runs critical systems on IBM mainframes written in PL/I, you need developers who understand the language, the platform, and the unique characteristics of mainframe development. Code that's been running for decades is often deeply embedded in your business processes.
Legacy Code Modernization: Many organizations are modernizing mainframe systems without abandoning them entirely. This requires developers who understand the existing PL/I code deeply and can refactor, improve, or bridge it to modern platforms. Strangler fig patterns, data migration, and gradual system replacement all require PL/I expertise.
System Integration and Middleware: PL/I systems often need to integrate with modern APIs, databases, or cloud services. Developers who understand both PL/I and modern integration patterns can build bridges between old and new systems.
Performance-Critical Financial Systems: Some financial institutions deliberately maintain PL/I systems because they've spent decades optimizing them for transaction throughput, reliability, and correctness. Modifying these systems requires deep expertise.
Risk Mitigation During Transitions: When replacing PL/I systems, hiring experienced PL/I developers to support the transition often costs less than mistakes made by developers who don't understand the original system's design decisions.
Don't hire PL/I for new projects. If your organization has no existing PL/I code, learn a modern language instead. The sole reason to hire PL/I is to work with existing systems.
Deep Mainframe Knowledge: The best PL/I developers don't just know the language; they understand mainframe architecture, CICS, IMS, DB2, TSO/ISPF, and the broader ecosystem. PL/I development is inseparable from mainframe operations.
Legacy Code Fluency: Look for developers who've worked in large PL/I codebases and understand patterns like macro usage, global data structures, and the coding conventions that have accumulated over decades. This experience is gold.
System Design and Refactoring: The best candidates can read old code, understand its intent, and refactor it safely. They understand trade-offs: when to rewrite, when to extend, and when to leave well enough alone.
Business Domain Knowledge: Developers who've worked in banking, insurance, or telecommunications understand the business logic embedded in these systems. They can distinguish critical features from technical debt more effectively than language specialists.
Problem-Solving Under Constraints: Mainframe development operates under real constraints: limited memory (historically), specific I/O patterns, strict error handling requirements. Candidates who've worked within these constraints make better decisions.
Modernization Experience: If you're moving off mainframes, hire developers who've done this before. They understand the pitfalls, the regulatory requirements, and the data migration challenges that most developers miss.
PL/I developers are aging out of the workforce. The language isn't taught in universities, and younger developers rarely learn it. This creates a supply crunch.
Latin America Market (2026): PL/I developers with production mainframe experience typically earn 85,000-140,000 USD per year. Senior developers with deep system knowledge reach 140,000-180,000 USD. Geographic location matters less than experience; organizations will pay for proven expertise.
Contract and consulting arrangements are common. Experienced PL/I contractors charge 80-150 USD per hour, often with minimum engagement terms.
The scarcity premium is real and growing. As experienced PL/I developers retire, their replacement cost increases. If you have PL/I systems, budget generously for maintenance.
Cost Advantage for Scarce Expertise: PL/I expertise costs 25-35% less in Latin America than in North America or Europe. For organizations maintaining business-critical PL/I systems, this represents significant savings on maintenance budgets.
Mature Engineering Talent: Latin American developers interested in mainframe systems often have decades of experience and deep domain knowledge. Many have worked on banking and government systems where PL/I still dominates.
Timezone and Support: Latin American developers provide excellent timezone coverage for North American and European organizations. Support for 24/7 critical systems becomes more feasible with distributed teams.
Reliability and Commitment: Developers who specialize in legacy system maintenance tend to be reliable, committed, and detail-oriented. These traits matter more than raw speed when dealing with mission-critical code.
Knowledge Transfer Opportunities: As experienced PL/I developers retire globally, hiring Latin American talent now provides opportunities for knowledge transfer before expertise disappears entirely.
Finding PL/I developers is harder than finding most other skills. South maintains relationships with mainframe specialists, legacy systems experts, and experienced developers who've worked across banking and government sectors.
Mainframe Community Access: We tap into mainframe conferences, user groups, and industry associations to identify experienced PL/I developers throughout Latin America and beyond.
Experience Assessment: We evaluate candidates' depth of mainframe knowledge: which systems have they maintained, what was the scale, and what was their impact? We look for substance, not just resume keywords.
Business Domain Understanding: For banking, insurance, or government systems, we assess whether candidates understand your industry context. Domain-specific experience often matters more than pure language expertise.
30-Day Replacement Guarantee: Every PL/I placement includes a 30-day replacement guarantee. If the developer can't effectively maintain your systems or struggles with the business domain, we find a replacement at no additional cost.
Ready to secure expertise for your legacy systems? Start your search with South today.
That's a strategic business decision, not a language question. If the systems are generating revenue and meeting your needs, maintaining them can be cost-effective. If they're becoming a liability or blocking innovation, migration makes sense. Hiring experienced PL/I developers helps you execute either strategy well. We can help you assess your options.
It's possible, but risky for mission-critical systems. PL/I is complex, mainframe systems are finicky, and mistakes are expensive. For learning projects, sure. For production systems, hire experienced developers. The cost difference is worth it.
This is where South's specialization pays off. We maintain networks in mainframe communities, academic institutions that still teach PL/I, and organizations with large legacy PL/I systems. We can find developers you won't find on regular job boards.
COBOL is business-focused and verbose. PL/I is more general-purpose and compact. Both are legacy languages. If you're on mainframes and can't find PL/I developers, COBOL developers might be more available, though their skills don't transfer completely.
Yes, though it's awkward. Most integration is via data files or middleware. Experienced developers can build bridges, but PL/I wasn't designed for REST APIs or JSON. The integration layer is usually the most expensive part of modernization.
Only if you're maintaining existing PL/I systems. Don't learn it for new projects. If you work in mainframe systems, learning PL/I can make you valuable in a shrinking talent market, but it's not a growth skill.
Typically 3-8 weeks. PL/I talent is sparse and often not actively job hunting. We need time to identify and engage experienced developers. Urgency may extend the timeline if we need to search globally.
Look for developers experienced with CICS (transaction processing), IMS (hierarchical database), DB2 (relational database), and ISPF/TSO (development environment). These are the ecosystems where PL/I lives.
Look for clean structure, proper exception handling, clear variable names, and modular procedures. Legacy code is often cryptic; good PL/I developers make it understandable. Ask them to explain their approach to code organization and maintainability.
PL/I code will run on mainframes for decades. The language itself is stable, not growing. If you maintain PL/I systems, you'll need expertise for the foreseeable future. Plan for succession as experienced developers retire.
COBOL | Mainframe Systems | CICS | DB2 | Legacy Systems Modernization
