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}
CL (Control Language) is the native command and scripting language for IBM's iSeries (formerly AS/400, now IBM i) systems. Created in the 1980s as part of the System/38 architecture, CL allows developers to automate system operations, call compiled programs (written in RPG, COBOL, or other languages), manage resources, and integrate applications running on IBM i. CL syntax is verbose and keyword-based, designed for readability and systematic structure rather than brevity.
IBM i systems run critical business applications in finance, manufacturing, retail, and government. These are proven, stable platforms with decades of uptime records. CL developers don't write applications from scratch; they orchestrate system operations, call programs, manage jobs, handle file operations, and automate business processes. A CL program might trigger nightly batch jobs, move files between systems, enforce security policies, or coordinate multi-program workflows.
The IBM i ecosystem is mature but aging. Modern applications are built on Linux, Windows, or cloud platforms, but tens of thousands of IBM i systems still run mission-critical workloads globally. Unlike dying languages (like COBOL, which faces replacement pressure), IBM i is actually gaining new life through modernization efforts and cloud hosting. However, finding developers aged 25-40 who know CL is increasingly difficult, creating a supply crisis.
CL is not a general-purpose programming language like Python or Go. It's a system administration and integration language specific to IBM i. Hire CL developers only if you're maintaining IBM i systems. Learning curve is steep for developers unfamiliar with mainframe or IBM i concepts like libraries, job streams, and file systems.
Hire a CL developer if you're maintaining critical IBM i systems that drive core business operations. These systems often handle high-transaction volumes (retail point-of-sale, financial clearing, manufacturing planning) and operate 24/7/365. CL developers maintain batch jobs, system interfaces, and operational scripts that keep these systems running.
Don't hire CL for new development unless you're already committed to IBM i. The language is tied to a specific platform, and building new capabilities on IBM i is rare. If you're evaluating whether to stay on IBM i or modernize, consult an IBM i architect first, then hire specialists accordingly.
Hire part-time if you have a small IBM i footprint requiring occasional maintenance, job scheduling, or integration scripting. Many organizations run one or two IBM i systems for specific functions (financials, inventory, point-of-sale) while everything else runs on modern infrastructure.
Team composition depends on your strategy. If staying on IBM i, hire senior CL developers who understand system architecture. If modernizing, pair IBM i specialists with modern developers building replacement systems on Java, Python, or cloud platforms.
Look for developers with 10+ years of IBM i experience. They should understand the IBM i architecture, job management, file systems, security models, and integration with compiled programs (RPG, COBOL). Knowledge of IPA (Integrated Platform Architecture) or modern IBM i capabilities is valuable. They should be comfortable debugging system-level issues and working with minimal documentation.
Must-haves: Deep CL expertise, proven IBM i production experience, understanding of system operations and batch jobs, comfort with IBM i command-line tools and system architecture.
Nice-to-haves: RPG or COBOL knowledge (common pairings), experience with modern IBM i versions (7.4+), cloud hosting (IBM i on AWS or Azure), REST API integration, modernization experience.
Red flags: Developers claiming CL expertise without IBM i experience, those unfamiliar with concepts like job descriptions or file organization, lack of long-term system maintenance experience.
Junior (1-2 years): Rare. CL talent is senior by necessity, having worked with IBM i for decades.
Mid-level (3-5 years): Uncommon. Most CL developers have 10+ years experience from career-long commitment to IBM i.
Senior (10+ years): Typical hire. Deep IBM i knowledge, system architecture understanding, ability to optimize complex batch operations and integrations.
1. Tell me about your longest-running CL program or batch job. What was its business function? How did you maintain it? Look for evidence of understanding business impact and long-term ownership.
2. Describe a time you had to integrate an IBM i system with a modern application (web service, cloud platform, etc.). What was your approach? Tests adaptability. IBM i is modernizing, and integration skills are increasingly valuable.
3. Walk me through a challenging CL debugging session. How did you identify and fix the issue? Tests problem-solving rigor and knowledge of IBM i debugging tools.
4. How have you seen IBM i evolve in your career? What trends do you think will shape the platform's future? Gauge awareness of platform trajectory and comfort with modernization discussions.
5. Tell me about a time you had to mentor someone or document a complex CL process. How did you approach it? Knowledge transfer is critical in IBM i communities. Look for communication skills.
1. Explain the structure of a CL program: DCL (declare), CRTCLPGM (create), and JCL (job control). How do they relate? Fundamental IBM i concepts. Strong answers show understanding of program lifecycle and job management.
2. How do you handle error conditions in CL? Walk me through your error handling strategy in a batch job. Tests practical systems thinking. Look for answers mentioning MONMSG (monitor message), return codes, and job failure handling.
3. You need to call an RPG program from CL and handle different return codes. Walk me through the implementation. Tests interoperability between CL and compiled languages, common in IBM i environments.
4. Explain the differences between a library, a file, and a data area in IBM i. When would you use each in a CL program? Tests fundamental IBM i concepts. Strong answers show understanding of namespacing, data storage, and system organization.
5. How would you schedule a CL program to run daily at 2 AM, and how would you handle failures? Tests practical job scheduling and operational understanding. Look for answers mentioning job scheduling and notification mechanisms.
Ask the candidate to write a CL program that reads a file, validates records, calls a processing program, handles errors, and logs results. Expected time: 45-60 minutes. Grade on correct CL syntax, error handling, and understanding of IBM i file operations and program calling conventions.
US market comparison: CL developers command $75,000-120,000 for mid-level and $120,000-180,000+ for senior, reflecting extreme scarcity. LatAm rates reflect 35-45% discount.
What's included: South staffing covers employment taxes, equipment, time zone coordination, and ongoing support. Rates vary by platform version (OS/400 vs. modern IBM i) and domain expertise.
IBM i talent exists globally but is geographically concentrated. LatAm has pockets of IBM i expertise, particularly in Brazil and Argentina, from enterprise outsourcing history. These developers bring deep platform knowledge and stability-focused mindsets.
Time zone alignment is excellent: UTC-3 to UTC-5 provides 6-8 hours real-time collaboration with US teams. For 24/7 systems requiring synchronous support, this is invaluable.
LatAm CL developers typically understand the full IBM i stack (CL, RPG, COBOL, database) and often have experience with large-scale business systems. English proficiency and cultural alignment with stability and process are strong in this specialization.
Cost efficiency is 35-45% below US rates, significant when maintaining critical systems long-term. Retention is high, as IBM i specialists are deeply committed to the platform.
CL is specialized, so we identify candidates from our curated IBM i network. We prioritize developers with experience in your specific domain (finance, retail, manufacturing, etc.) and IBM i version.
You describe your systems, pain points, and modernization strategy (if any). We match from our network and conduct technical interviews on platform knowledge and specific challenges. You interview and assess. South handles compliance, equipment, and ongoing support.
If a hire doesn't fit, we replace at no charge within 30 days. For mission-critical IBM i systems, this guarantee provides confidence and continuity.
For modernization initiatives, we pair IBM i specialists with modern developers, enabling gradual migration without service disruption. Start your IBM i hire now.
Yes. Thousands of mission-critical systems run on IBM i, particularly in finance, retail, and manufacturing. The platform is stable, secure, and increasingly cloud-hosted. Growth is limited, but the installed base is massive.
Depends on your strategy. If IBM i systems are performing well and your team can maintain them, focus on gradual modernization (exposing services via APIs, adding cloud-based extensions). Full migration is expensive and high-risk unless driving specific business benefits.
CL is for system automation and job orchestration. RPG is for application logic and data processing. They complement each other. Most IBM i projects need both.
Expect $45,000-95,000/year depending on seniority, with most candidates in the 10+ year range. Scarcity commands premium rates.
2-4 weeks. CL is highly specialized, and candidate availability varies globally.
Yes. Many organizations need part-time IBM i support for maintenance and integration work. South can staff part-time specialists for 15-30 hours/week.
Primarily UTC-3 to UTC-5 (Brazil, Argentina), providing 6-8 hours real-time overlap with US East Coast. Excellent for critical system support.
We review IBM i production experience, conduct technical interviews on CL and platform architecture, and validate problem-solving ability through practical assessments.
We replace at no charge within 30 days. Critical systems require continuity and confidence.
Yes. South handles employment, taxes, equipment, and HR. You manage work directly; we handle administration.
