Pega LSA

Assessment and planning Lead technical assessment of rule overrides (several hundred on the disputes framework), custom Java, integrations, data, batch processing, and UI customizations for 25.1 compatibility. Run the Upgrade Estimator and Upgrade Impact Summary, and turn the findings into a prioritized remediation plan. Inventory, classify, and prioritize overrides for client review and formal approval. Support the downtime approach and the sequencing of multiple upgrades across three applications. Cloud 2 to Cloud 3 migration Support Cloud 3 readiness: private links, DNS, certificates, firewall rules, IP allow-listing, and schema and routing readiness. Assess and remediate unsupported file handling and filename constraints, and refactor to supported file storage and repository APIs. Review queue processor and background processing behavior, including backlog volumes, thread scaling, and consumer offsets, given Pega 25’s move to Kafka-based processing. Coordinate with Pegasystems support on environment readiness and timelines. Remediation and build Define remediation design and development standards for the delivery team. Remediate rule overrides, deprecated rules and APIs, custom Java (refactoring to supported JDK levels and favoring out-of-the-box capabilities), and integration components, as approved by the client. Support retrofitting, code freeze, and branching strategy while development continues on the current version. Support remediation to reach a 90+ guardrail score before the upgrade. Testing and validation Support clone/baseline environment setup so upgrade defects can be separated from existing defects. Support regression, end-to-end, performance, and in-flight case testing, including card network integrations and negative paths. Work with QA and business users on defect triage and retesting. Cutover, rollback, and stabilization Support downtime mitigation options (for example, a read-only legacy instance for duplicate checks, queuing middleware, or de-duplication within Pega) and their trade-offs. Support rollback planning, including replaying queued intake into the prior version with de-duplication and reconciliation. Support mock cutovers, dress rehearsals, runbook preparation, command center, and post-go-live hypercare, with production deployments led by the client.

• 12+ years of enterprise Pega experience, with recent leadership of platform upgrades or version migrations.
• Hands-on experience with a major Pega Platform upgrade (for example, v8.x or later to v23/24/25) on a customized production application.
• Direct experience with Pega Cloud: provisioning, private connectivity, endpoint architecture, DNS, and working with Pegasystems on migration or cutover. Cloud 2 to Cloud 3 experience strongly preferred.
• Experience assessing and remediating rule overrides, deprecated components, and framework changes (for example, Pega Smart Disputes or Customer Service frameworks).
• Custom Java assessment and refactoring experience, including JDK compatibility.
• Experience with Pega integrations (REST/SOAP, SFTP, TLS, authentication) and with queue processors, agents, and Kafka-based background processing.
• Experience planning and executing production cutovers, including rollback strategy, rehearsals, and runbooks.
• Pega Certified Lead System Architect (CLSA, or Part I with a plan to complete) and CSSA.
• US-based and able to work full time, on site or hybrid as the client requires.
• Able to meet client onboarding, security, and background screening requirements.

Domain experience (required)

• Banking or credit card experience, ideally on dispute management, chargebacks, or collections workflows on Pega.
• Familiarity with the credit card transaction lifecycle, including clearing and settlement.
• Experience with card network integrations for chargeback and dispute processing, and with the compliance changes that affect them.
• Experience in regulated financial institutions, including change management, audit, and production access controls., * Experience migrating or upgrading within a large, controlled banking environment with strict downtime windows.
• In-flight case migration and validation experience in dispute or case management applications.
• CI/CD and release governance experience (for example, Pega Deployment Manager or equivalent pipelines).
• Performance baselining and tuning after an upgrade, including Static Assembler handling.
• Prior experience as the on-site Pega lead supporting a client with limited upgrade experience.