Senior Software Engineer – PowerBuilder
PowerBuilder to .NET migration · 5–8 years experience · Bachelor’s in Computer Science, Software Engineering, or equivalent practical experience
Core Key Responsibilities
-
Analyze the existing PowerBuilder application — modules, DataWindows, business logic, database interactions, integrations, and dependencies — to establish current behavior.
-
Support migration of PowerBuilder functionality to .NET / C#, translating existing functionality and business rules into maintainable technical solutions.
-
Contribute hands-on to the design, development, enhancement, and testing of the replacement .NET implementation.
-
Identify migration complexity, technical dependencies, gaps, and risks in the legacy codebase, and communicate findings clearly to the project team.
-
Analyze SQL Server queries, stored procedures, and data dependencies used by the PowerBuilder application and support their transition or reuse in the target solution.
-
Troubleshoot complex issues across the legacy PowerBuilder modules, the new .NET implementation, databases, integrations, and third-party components.
-
Document existing PowerBuilder functionality and technical behavior to support migration, testing, traceability, and knowledge transfer.
-
Develop and maintain unit tests and work with QA to compare legacy and migrated behavior and validate functional equivalence.
-
Participate in technical analysis, backlog refinement, estimation, sprint planning, and peer code reviews; work with minimal supervision and raise risks early.
Core Technology Skills Required
-
PowerBuilder — strong hands-on development; able to navigate, understand, troubleshoot, and modify an established codebase.
-
.NET / C# — hands-on experience sufficient to contribute directly to migration and replacement development.
-
Legacy modernization — experience migrating or re-platforming legacy applications to .NET or another modern stack, strongly preferred.
-
SQL Server — queries, stored procedures, and data dependency analysis.
-
Object-oriented programming, design principles, and application architecture — strong grounding in maintainable code practices.
-
Git, Visual Studio, and Azure DevOps — source control and development tooling, preferred.
-
CI/CD — working knowledge of automated build and deployment pipelines, desirable.
-
Engineering practices — coding standards, code reviews, source control, build processes, testing, deployment, and maintenance.
-
Reverse engineering — ability to determine legacy application behavior where documentation is limited.
-
Agile / Scrum — delivery within cross-functional development teams.
-
Communication — clear documentation of technical findings, dependencies, and migration risks.
