PowerWire Logo
The trusted voice of the IBM Power community

The IBM i Skills You Need Are Already In‑House

The IBM i Skills You Need Are Already In‑House

The "Great Retirement" of the mid-2020s is no longer a theoretical threat discussed in boardrooms; it is a daily operational reality. As we move through April 2026, the IBM i community faces a unique inconsistency. The platform is more capable than ever, powering global supply chains, hybrid cloud environments and high-speed AI workloads, yet the hands on the keyboards are retiring at record rates.

For decades, the IBM i (it will always be AS/400 to some of us!) has been the silent workhorse of the enterprise, but as the architects of these systems reach the finish line of their careers, they take with them millions of lines of institutional logic and system-specifics. The traditional response has been to search for a senior RPG developer with thirty years of experience who is also an expert in modern APIs.

In today’s market, those candidates are nearly impossible to find. When you do find them, the bidding wars are astronomical. But there is a more strategic, sustainable and cost-effective move for 2026: Look inward. The solution to your skills gap isn't a headhunter; it’s the motivated internal apprentice already sitting in your warehouse, your finance department, or your support desk.


The Executive Case: ROI and Risk Mitigation

From a leadership perspective, recruiting external RPG talent in 2026 is a high-risk gamble. When you hire from the outside, you are paying for technical syntax, but you are still missing the context.

Institutional Knowledge is Non-Transferable

An external hire might know how to write an RPG program, but they don’t know your custom order-entry logic or why a specific process must trigger a certain way for your biggest client. An internal apprentice already lives and breathes your business rules. They understand the "why" before they ever learn the "how."

The Loyalty Dividend In an era of "job hopping," internal mobility is a massive retention tool. When you take a high-performing employee from an operational role and invest in their transition to a developer, you aren't just filling a seat; you are building a career path. The loyalty generated by that investment far outlasts the tenure of a mercenary hire.

Bridging the Knowledge Cliff The biggest risk to your business continuity is the "Knowledge Cliff", the moment your senior developer leaves without a successor. An internal apprenticeship model allows for a graceful handoff. It creates a bridge where the veteran becomes a mentor, passing down the logic while the apprentice brings the fresh energy to modernise it.


The Technical Case: The "Native" Advantage

For the IT Manager, the concern isn't just about "headcount", it’s about code quality and system integrity. Many modern "coding bootcamps" focus on high-level web languages that treat the IBM i like a generic Linux box. This is a big mistake. To truly master this platform, an apprentice needs to be "bilingual" in the native languages of the Power System.

To instil Native Mastery training philosophy should centre on taking apprentices through the full evolutionary stack of the IBM i:

1. Decoding the Legacy (RPG/400 and Fixed-Format) You cannot modernise what you do not understand. In 2026, trillions of lines of fixed-format RPG still run the world. Apprentices will struggle unless they know how to read and maintain this legacy code. They can then support existing core logic safely, rather than trying to "rip and replace" systems they don't comprehend.

2. System Orchestration (CL - Control Language) as we all know, the IBM i is an integrated machine, database, security and OS are one. Therefor training needs to move beyond simple application coding to teach Control Language (CL). This allows apprentices to manage jobs, handle system messages and orchestrate the Integrated Language Environment (ILE) with precision.

3. Modern Architecture (RPG IV & Free-Form) The goal isn't just "keeping the lights on. Apprentices should be equipped to write modular, thread-safe Free-Form RPG, so they can build modern Service Programs and APIs that allow your "legacy" box to communicate with the web, mobile apps and AI protocols seamlessly.


By teaching an apprentice how a 1990-era RPG/400 program can be refactored into a 2026-era ILE service program, you create a developer who can communicate across generations.

These graduates become the ultimate "Full-Stack" developers. They can look at a green screen legacy application and see the path toward a modern web interface without losing any of the underlying data integrity. They understand that the power of the IBM i isn't just in its legendary uptime, but in its incredible ability to evolve without breaking.

The Bottom Line

If you are waiting for a senior developer to drop into your lap, you are waiting for a miracle. If you are trying to "out-hire" the skills gap, you are fighting a losing battle.

The best developer for your company is already on your payroll. They have the passion, they have the business context, and they have the drive to see your company succeed. All they need is the technical "baptism" in native IBM i programming.

The "Knowledge Cliff" is only a drop-off if you aren't building a bridge. Why not start building yours today.