Progress Software Engineering
Role Overview
Our team maintains and extends established business applications built using Progress
OpenEdge / ABL. Much of this work involves understanding and safely modifying long-lived
applications, troubleshooting existing behavior, implementing enhancements, and
extending existing systems to participate in newer application architectures.
The majority of the work is legacy application maintenance and enhancement. New
development is also required, particularly around the creation of APIs that make existing
Progress application capabilities available to other systems.
Effective augmentation requires strong Progress development skills as well as good
software engineering judgment. A resource needs to be able to understand unfamiliar
existing code, determine the implications of a proposed change, communicate effectively
with the internal team, and make changes without unnecessarily destabilizing established
systems.
Progress Development
The teamâs Progress work includes:
ï· Development using Progress ABL / Progress 4GL
ï· Supporting applications running on Progress OpenEdge 11.7 and later
ï· Maintaining and enhancing established Progress applications
ï· Understanding and safely modifying unfamiliar or legacy code
ï· Debugging and tracing application behavior through existing codebases
ï· Implementing new functionality within established applications
ï· Working with Progress database access from an application developerâs
perspective
Deep Progress database administration knowledge is not required for this development
profile.
API and Integration Development
An increasing portion of the work involves enabling established Progress systems to
integrate with newer applications and services.
Relevant capabilities include:
ï· Creating APIs around existing Progress application capabilities
ï· Understanding HTTP and REST-style APIs
ï· Separating business logic from API or transport concerns where practical
ï· Designing clear interfaces between legacy applications and newer systems
ï· Working with formats such as JSON for application integration
Software Engineering Practices
Progress development is expected to reflect sound software engineering practices despite
the age or constraints of the systems involved.
Relevant capabilities include:
ï· Designing maintainable software
ï· Understanding separation of concerns, coupling, cohesion, and dependency management
ï· Incrementally refactoring legacy code where doing so improves the change being made
ï· Balancing improvement opportunities against scope, risk, and business value
ï· Applying automated testing where practical
ï· Reasoning carefully about regression risk
ï· Understanding existing behavior before modifying it
ï· Avoiding unnecessary rewrites when incremental change is more appropriate
Requirements, Judgment, and Communication
The nature of the work requires developers who can:
ï· Listen carefully and communicate clearly
ï· Clarify requirements and assumptions
ï· Understand the purpose and expected outcome of a change
ï· Work independently while maintaining regular communication with the internal team
ï· Seek alignment when requirements or technical direction are unclear
ï· Identify unexpected dependencies and regression risks
ï· Raise concerns or alternative approaches early
ï· Accept technical direction and incorporate feedback constructively
ï· Recognize when additional technical guidance is needed
Additional Relevant Capabilities
Depending on the work, useful experience can include:
ï· Integrating Progress applications with .NET or other modern application environments
ï· REST API design and consumption
ï· JSON serialization and API payload design
ï· Relational database concepts
ï· Query performance and indexing from an application-development perspective
ï· Git source control
ï· Modernization of legacy application interfaces
ï· Automated testing of legacy or difficult-to-test applications
ï· Working in environments where established Progress systems coexist with newer technologies
Responsibilities Outside This Profile
This development profile does not depend on a resource serving as:
ï· A Progress DBA
ï· An AIX or operating-system administrator
ï· A business analyst
ï· A help desk or second-tier application support resource
ï· A CI/CD or deployment infrastructure administrator
Those capabilities may be useful in particular circumstances, but they should not be
treated as primary screening criteria when identifying resources to augment Progress
development work.
Most Important Characteristics
When considering a resource for this work, the strongest indicators of fit are:
1. Strong Progress ABL development capability.
2. The ability to understand and safely modify established applications.
3. Good technical judgment about scope, risk, and design.
4. Strong listening and communication skills.
5. A tendency to seek and maintain alignment on requirements and intended outcomes.
6. An incremental approach to improving legacy software rather than unnecessary rewriting.
7. The ability to recognize when questions or technical concerns need to be raised with the internal team.
Your email job alert is now active!