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}
RPG (Report Program Generator) is an enterprise language purpose-built for IBM's System i and mainframe platforms, handling business logic, report generation, and data processing at massive scale. If your organization depends on RPG systems for accounting, inventory, sales processing, or other mission-critical operations, experienced RPG developers are irreplaceable for maintaining, modernizing, and extending these systems. South connects you with expert RPG specialists from Latin America who understand IBM i architecture and can guide your platform through modernization.
RPG (Report Program Generator) originated in the 1960s as a language for IBM System i (formerly i5/OS and AS/400) platforms, designed specifically for business application development and report generation. Unlike general-purpose languages, RPG is tightly integrated with the IBM i operating system, database (DB2 for i), and file systems. It's a fixed-format language with built-in record I/O, making it exceptionally efficient for the business applications it was designed for: payroll, accounting, inventory management, and data processing workflows.
RPG remains deeply embedded in enterprise operations, particularly in small and mid-market manufacturing, distribution, and financial services. Companies that deployed RPG systems 20-30 years ago still run them as core operational systems, processing millions of transactions daily. The language has evolved: RPG IV and free-form RPG modernized the syntax, added object-oriented capabilities, and improved integration with web services and modern APIs. But the core mission remains the same: reliable, high-performance business application development.
The RPG ecosystem is concentrated in specific industries and geographies. The System i platform dominates in manufacturing (ERP), wholesale distribution, and small business accounting software. This concentration means RPG expertise is highly specialized and increasingly valuable as the aging developer population creates a skills gap. Organizations that depend on RPG are actively seeking experienced developers who can maintain systems, implement modern integration patterns, and mentor the next generation.
You need RPG expertise if you operate System i platforms as part of your core business infrastructure. This includes maintaining existing RPG applications, enhancing system functionality, debugging production issues, and modernizing legacy code. RPG is the native language for System i, so if you're on that platform, you'll need RPG expertise to optimize performance or implement new features efficiently.
The second critical scenario is modernization and API integration. If you're building web interfaces to RPG systems, creating REST APIs that wrap System i business logic, or integrating RPG applications with cloud platforms, an experienced RPG developer can architect modern integration layers while preserving the reliability of the underlying systems. This is increasingly common as organizations want cloud-native frontends connected to System i backends.
You should also hire RPG talent when facing a knowledge gap in your System i operations team. The RPG developer base is aging, and many organizations have only one or two experts remaining. Bringing in remote RPG developers from Latin America provides stability, knowledge transfer, and operational continuity while you build internal expertise.
RPG is NOT appropriate for building new applications from scratch unless those applications specifically target the System i platform. Modern web applications, mobile apps, cloud-native systems, and microservices should use contemporary languages. RPG shines for business application development on System i, not as a general-purpose platform.
Team composition matters. Pair RPG developers with System i database architects, security specialists (System i has unique security models), and ideally integration architects if you're building API layers. For modernization efforts, pair RPG expertise with cloud architects who can guide the transition strategy.
Evaluate RPG candidates on core language fluency: fixed-format and free-form RPG syntax, file I/O operations, data structures, and control flow. Beyond syntax, look for deep System i knowledge. Strong RPG developers understand how their code interacts with the underlying platform: the integrated file system (IFS), the DB2 for i database, security models (user profiles, authority), and job management. They've debugged production systems and understand performance implications of their code choices.
Modern RPG developers are differentiated by their ability to work beyond traditional RPG silos. Can they write web services and REST APIs? Do they understand JSON and XML? Have they integrated RPG with modern platforms using tools like Node.js or Python adapters? Senior developers signal awareness that RPG systems exist within larger IT ecosystems and can architect appropriate integration patterns.
Red flags include candidates with only academic RPG experience, those who treat the language as purely legacy with no understanding of modern capabilities, developers without System i platform knowledge, and anyone who can't articulate how their code handles errors or performance optimization. Also watch for developers who lack communication skills; System i knowledge is rare and valuable, so you need someone who can mentor others.
Junior (1-2 years): Understands RPG syntax (fixed and free-form), has written simple programs under guidance, familiar with basic file I/O and data structures. Can write functional code but needs mentoring on production practices, optimization, and System i platform specifics. Often working on maintenance tasks or well-structured features.
Mid-level (3-5 years): Writes production applications independently, understands System i architecture and database concepts, can debug complex programs and optimize performance. Familiar with modern RPG capabilities (APIs, web services, SQL integration). Can mentor junior developers and contribute to architecture decisions. Knows when to use different RPG approaches for different problems.
Senior (5+ years): Designs RPG systems and modernization strategies, mentors teams, understands integration architectures and can build bridges between RPG and cloud platforms. Often specialists in particular domains (ERP systems, financial applications, supply chain). Serve as architects and knowledge transfer partners for organizations modernizing their System i footprint.
Walk me through the largest RPG system you've worked on. What were the key components and how did they interact? A strong answer shows understanding of system architecture, data flow, integration points, and business requirements. Listen for specific examples: file structures, transaction volumes, performance considerations. The answer should demonstrate they've thought about systems holistically, not just individual programs.
Tell me about a time you modernized legacy RPG code. What approach did you take and what were the trade-offs? This tests real modernization experience. Strong answers discuss specific strategies: refactoring to free-form syntax, moving to SQL queries, adding API layers, or redesigning data structures. They discuss why they made certain choices and what constraints they worked within (legacy systems can't always be fully rewritten).
How do you approach troubleshooting a production RPG application that's running slowly or crashing intermittently? Strong answers show systematic debugging: using System i tools (debug mode, job logs, performance tools), understanding where the bottleneck might be (I/O, database queries, application logic), isolating the issue, and implementing fixes without disrupting production. They discuss communication with operations teams.
Describe your experience building modern integrations between RPG systems and cloud platforms or APIs. This separates purely legacy developers from modernization-capable experts. Good answers include concrete examples: REST API wrappers around RPG business logic, webhook integrations, data sync patterns, or cloud service calls from RPG. Indicates understanding that RPG systems need modern interfaces.
What's your experience with SQL in RPG and how do you decide between traditional file I/O vs SQL approaches? Strong candidates understand the trade-offs: SQL is more powerful for complex queries and joins, but traditional RPG I/O is optimized for sequential processing. They've made these decisions in real systems and can articulate the reasoning (business logic clarity, performance, maintenance).
Write an RPG program that reads a customer master file, identifies customers with unpaid invoices over 60 days, and generates a report. Include appropriate error handling. Evaluate for: correct RPG syntax (free-form or fixed depending on their expertise), proper file I/O, date calculations, error handling, and report formatting. A junior developer might miss edge cases; a senior developer writes defensive code that handles missing data, invalid dates, and empty result sets.
How would you optimize this RPG program that processes 1 million records and takes 30 minutes to run? Strong developers discuss specific optimization techniques: using SQL subqueries instead of sequential reads, reducing I/O operations, better indexing strategy, data structure optimization, or parallelization. They explain why each optimization matters and how they'd validate the improvements don't break existing logic.
Explain the difference between RPG /COPY directives and subroutines. When would you use each? This tests modular code design understanding. Correct answer shows understanding of when to share code via /COPY (truly common code) vs subroutines (reusable logic within or across programs). A good answer includes design rationale: maintainability, code reuse, and testability.
How would you expose RPG business logic as a REST API without rewriting the entire application? Strong answers discuss specific approaches: building a thin Node.js or Python wrapper layer, using IBM's native API tools (like IBM i Web Services), or creating new SQL-based stored procedures that the API calls. They think about compatibility, performance, and gradual migration.
An RPG program is failing in production but runs fine in test. Walk me through your diagnostic approach. Evaluate for systematic thinking: understanding production vs test differences (data volumes, system load, timing issues), using production debugging tools, working with production support, implementing safe fixes, and preventing similar issues. Shows they've dealt with real production pressure.
Build an RPG program that reads sales transactions (customer, product, amount, date), groups by customer, calculates total sales and average transaction, and writes a summary file. Include validation of input data, error handling, and comments. Expected time: 90 minutes. Evaluation criteria: correct RPG syntax, proper file I/O, accurate calculations, robust error handling, readable code. Senior candidates should discuss performance optimization and suggest API design if this were exposed as a service.
Latin America RPG Developer Rates (2026):
US Market Rates (for comparison):
RPG specialists from Latin America offer 40-55% cost savings compared to US talent while often bringing deeper system knowledge. The talent pool is mature and experienced, particularly in Brazil, Argentina, and Mexico where System i platforms remain common in manufacturing and distribution.
When budgeting for RPG developers, remember you're often hiring someone with irreplaceable expertise. A mid-level LatAm RPG developer is typically more reliable and knowledgeable than a junior US developer and costs 35-45% less. Many organizations hire senior RPG developers specifically for knowledge transfer and modernization guidance, making the investment in experienced talent crucial.
Latin America has a deep System i ecosystem, particularly in Brazil, Argentina, and Mexico, rooted in decades of IBM business systems presence. Manufacturing, distribution, and financial companies across the region built their core operations on System i, creating a stable talent pool of RPG specialists. These developers understand not just the language but the entire business context in which it operates.
Time zone compatibility is valuable. Most LatAm RPG developers work UTC-3 to UTC-5, giving you 6-8 hours of real-time collaboration with US teams. This overlap matters for production support and debugging because many System i issues require synchronous investigation and quick fixes.
RPG developers from Latin America bring systems thinking and business understanding that modern-language developers often lack. They've built complete business applications from data modeling through reporting, understanding how systems fit together and how to maintain stability while implementing changes. This perspective is increasingly rare and highly valuable as organizations modernize.
English proficiency in the LatAm technical community is strong. RPG developers have typically worked with distributed teams and understand technical documentation and communication. Remote collaboration with RPG developers from Brazil, Argentina, or Mexico is seamless from a communication perspective.
Hiring RPG talent through South starts by understanding your specific needs. Are you maintaining existing applications, implementing modernization, building new integrations, or addressing a knowledge gap? We ask detailed questions about your System i environment, your application portfolio, and your modernization strategy if one exists.
We then match you from our network of pre-vetted RPG specialists across Latin America. Our vetting process includes RPG language assessment, System i platform knowledge, and real-world problem-solving scenarios. For RPG specifically, we validate understanding of your specific System i version and any custom extensions or legacy frameworks you use.
You interview matched candidates, typically focusing on your specific environment and challenges. We provide guidance based on hundreds of successful RPG placements and help you understand how candidates approach modernization and system architecture. Once you select a candidate, we handle onboarding and ensure smooth integration into your team.
Throughout the engagement, South provides ongoing support. If a matched developer isn't meeting expectations after 30 days, we replace them at no cost. For RPG specifically, where expertise is scarce and valuable, this guarantee protects your investment and ensures we're committed to finding the right fit.
Ready to strengthen your System i team with expert RPG developers? Start a conversation with South today and let's discuss your RPG modernization and staffing needs.
RPG powers core business applications on System i platforms: ERP systems, accounting software, inventory management, supply chain applications, and financial services platforms. It remains the dominant language for System i development and is used for new feature development, integration, and modernization initiatives.
Yes, but with context. New applications targeting System i are often built in RPG with modern patterns (APIs, web interfaces, cloud integration). New greenfield applications for other platforms should use contemporary languages. RPG is the right choice for System i, not for building new cloud-native or mobile applications.
RPG if you're building core System i business applications where performance and tight platform integration matter. Java or Node.js if you're building cloud-native services or web frontends that integrate with System i. Many organizations use both: RPG for business logic, modern languages for API layers and front-end clients.
Mid-level RPG developers in Latin America cost $48,000-$68,000/year, while senior developers range $72,000-$105,000/year. This represents 40-55% savings compared to US talent. Pricing varies by country; Brazil and Argentina are typically higher due to deeper talent pools and cost of living.
From initial conversation to a matched candidate ready for interviews: typically 5-10 business days. Interview and selection: 1-2 weeks. Onboarding and productivity: 1-2 weeks after selection. Total timeline: 3-4 weeks from request to productive developer on your team.
For bug fixes and maintenance of existing systems, mid-level developers are sufficient. For new feature development, optimization, or modernization initiatives, senior developers provide better results. Staff-level RPG developers are valuable if you lack internal expertise and need someone to guide your System i strategy.
Yes. South places RPG developers on part-time and project-based engagements. For short-term work, communicate your timeline clearly so we can match someone available for that duration. Part-time RPG support is common for organizations with occasional development needs.
Most South RPG developers operate in UTC-3 to UTC-5 (Brazil, Argentina, Mexico), providing 6-8 hours of real-time overlap with US East Coast teams. This overlap is valuable for production troubleshooting and synchronous development coordination. We can accommodate specific time zone requests if needed.
Our vetting includes RPG language assessment (fixed and free-form), System i platform knowledge, database concepts, and real-world application development problem-solving. For senior candidates, we assess their ability to design systems, mentor teams, and architect modernization strategies. Client references are always verified.
We replace them at no cost within the first 30 days of engagement. If expectations aren't being met, communication issues arise, or the skill fit is off, we match you with a different candidate immediately. This guarantee ensures we're motivated to make the right match.
Yes. South handles all payroll, tax compliance, and benefits administration for your RPG developers in their respective countries. You pay South one all-in rate; we manage all local compliance. If you prefer direct hire, we can facilitate that conversation.
Absolutely. Whether you need a small team for maintenance, a mixed junior-and-senior team for knowledge transfer, or a larger group for modernization initiatives, South can assemble the right RPG team. We've successfully placed teams of 5+ RPG developers for major System i projects.
