Hiring AS400 / RPG Developers in 2026: A Practical Guide
May 12, 2026 · 7 min read · Virtuous Skill Solutions Team
The shortage is real, but not unsolvable
IBM i (AS400) systems still run a startling share of North American banking, insurance, manufacturing, and distribution workloads. The talent pool, however, has narrowed: most experienced RPG developers entered the field in the 1990s, and very few new graduates learn RPG, CL, or DB2 for i in school.
The result is a market where rates have climbed, lead times have stretched, and the difference between a great submission and an average one is enormous.
What "senior" actually means in 2026
A senior AS400 / RPG developer in 2026 is rarely just an RPG IV programmer. The role has merged with modernization work. Expect:
- Fluency in RPG IV, RPG/Free-Form, and SQLRPGLE — not just fixed-format
- Comfort with ILE service programs, modules, and binder source
- Strong DB2 for i skills, including embedded SQL, triggers, and journaling
- The ability to expose IBM i logic as REST or JSON APIs (often via integrated web services or third-party tooling)
- Experience with CL programming and operational concepts like subsystems, output queues, and message handling
The best candidates can also bridge to Azure, AWS, or Salesforce — because most modernization programs end somewhere off the IBM i.
Rates and engagement models
Most enterprises hire AS400 / RPG developers through one of three models:
- Direct hire / FTE — best when the role is long-term maintenance plus modernization, and your team has runway to onboard
- Contract (T4 / W2 / C2C) — best for surge capacity, modernization sprints, or specialist skills (e.g., MAPICS, BPCS, JDE World)
- Managed pod — best when the IBM i is a strategic but non-core platform, and you'd rather buy outcomes than manage individuals
Rates vary significantly by region, clearance requirements, and seniority. Plan for premium pricing on niche skills like BPCS configuration or financial-sector RPG.
What a good shortlist looks like
A useful shortlist of three candidates should include, at minimum:
- One specialist who matches the stack (e.g., RPG + DB2 + MAPICS)
- One generalist with modernization experience (Free-Form, web services)
- One candidate with domain depth in your industry (banking, insurance, manufacturing)
Each candidate should arrive with references checked, right-to-work verified, and a clear answer to "what would you change first?" — not just a resume.
Common pitfalls
- Filtering only on years of experience. A 25-year resume with no Free-Form or SQLRPGLE work is often less useful than a 10-year resume that's stayed current.
- Skipping the technical screen. RPG roles are one of the few areas where a 30-minute code walk-through still beats a take-home test.
- Ignoring knowledge transfer. The reason you can't hire RPG developers is that your predecessors didn't document. Build documentation deliverables into every engagement.
How we approach AS400 / RPG staffing
We maintain a bench of senior IBM i, RPG, and DB2 for i consultants across Canada and the U.S., and we pair every submission with reference checks and a short technical screen by another senior practitioner. If you're scoping an IBM i program — maintenance, modernization, or migration — start with a 30-minute conversation, not a resume request.
