Hiring RPG developers across generations, challenges of attracting talent for IBM i (AS/400, iSeries) platforms, generational workforce differences, importance of remote work and flexible perks, cross‑generational hiring strategies, modernizing RPG versions (II, III, IV, open‑source alternatives) and implementing modernization plans, and practical tips for finding and recruiting skilled RPG programmers.
Photo by Annie Spratt on Unsplash
Hiring for the IBM i (AS/400, iSeries) platform
When it comes to hiring RPG developers, the fact that there are multiple generations in the workforce creates some unique challenges.
The generations that are currently in the workforce are:
- The Traditionalists / Silent: 1920 to 1945
- Baby Boomers: 1946 to 1964
- Generation X: 1965 to 1980
- Generation Y (Millennials): born after 1980
The differences between generations can make it difficult to attract and hire talent. While a baby boomer might not care about working remote, it might be one of the perks that is necessary to attract a Gen-Xer or Millennial.
To address these and other challenges, companies need to look at implementing a cross-generational hiring strategy. Doing so will break down some of the barriers, making it easier to attract and hire talent.
We also see that in many organizations, the hiring process is broken. Candidates are asked to jump through all kinds of hoops just to apply. As a result, many of them, who are passive, don’t finish the application process and go elsewhere.
How much friction are you creating for candidates to go through your application process?
In the future, organizations that recognize they need to make it easier for candidates to engage with them, as well as offer a variety of perks and incentives that are important to them, will win the war for talent.
Hiring RPG Developers and Modernization
We also need to rethink RPG as it relates to modernization because it plays a critical role in attracting and retaining talent.
There are a number of different versions of RPG — as well as several open-source options — in production today. They are, but are not limited to:
- RPG II
- RPG III
- RPG IV
- Open Source (PHP, Node.js, Java, Python, Javascript, Ruby)
As we look at RPG, each one of the older versions has its place. But as technology advancements continue to accelerate, and the needs of business change, IBM i shops must look at putting in place a modernization strategy to remain competitive.
How does this relate to talent?
Most of the IBM i professionals that I work with are looking to work with new and emerging technology on the platform.
This is either driven by their frustration of working on older versions of RPG and/or combined with the desire to be challenged and help modernize the platform.
So, what it comes down to is, it will be hard to attract or retain talent if you are not looking to modernize.
Solving the hiring challenges for the IBM i might not be easy, but it does not have to be difficult. We just need to look at modernization as a benefit for the business and to those who are working on the platform.
Hire remote IBM i (AS/400) RPG Developers
This is one of the easiest and most cost-effective ways to modernize your AS/400 environment.
Allowing your developers to work from home opens up the talent pool tenfold. Instead of having to depend on the availability of talent in your local market, you now have access to talent on a national level.
Of all the clients I work with, the ones that allow for remote work always get the best talent. Period. They are also the ones that are using the IBM i to its fullest potential.
Don't believe me? Give us a call and you will see the difference.
Another trick to hiring the best RPG developers is knowing where to look for talent.
Share
Found this article interesting? Others in your network may too. Please use the social media buttons to spread the word. Thank you!
Ongoing Insight
Get Talsco Weekly: Where IBM i security, talent, and continuity intersect
Each week, Talsco Weekly covers:
- Real-world IBM i talent and succession planning ideas
- Questions hiring managers should be asking—but often aren’t
- Signals that talent gaps may be becoming security gaps
- Practical insight from inside the IBM i ecosystem