Pega Lead Business Architect (LBA)

Role: Pega Lead Business Architect (LBA)

Location: Iselin, New Jersey, or Charlotte, NC

Contract role

Requirements for LBA (Must)

1. Experience working on Pega projects
2. Minimum 10 years of experience as a BA, including 5 6 years in Pega
3. Experience in the Banking domain
4. Ability to work independently with stakeholders (PO, Business, Onsite and Offshore teams, etc.)
5. Ability to translate business requirements into Pega requirements

Nice to have

1. Smart Dispute experience
2. Exposure to Fraud, Non-Fraud, Disputes, Claims in Banking
3. LBA Certification

Who are we looking for?

The Pega Lead Business Architect (LBA) with a good understanding of the Smart Dispute framework is responsible for driving legacy application discovery with business teams to translate the requirements with Pega's SDA framework. Promote OOB features and requirements with alignment of business process with minimum customizations where must.

Technical Skills:

12+ years of overall IT experience & 8+ years of hands-on Pega requirement management with center out approach

PCBA certification with good grip on Pega's Infinity platform and Low Code No Code development

Hands on expertise to use Pega BluePrint to drive requirements, visual feedbacks and refinements.

Working experience with Pega Infinity

Expertise in

JIRA, Pega Scenario Testing, Test Strategy and Data management

Case Management with Smart Dispute Agentic Automation framework and OOB journeys

Define best possible Pega User Experience with Constellation / UI Cosmos with OOB features

Ability to identify dependencies amongst EPICs, Features and User Stories

Crisp and clear way of defining and tracking user stories, Acceptance criteria

Run Show & Tell sessions with Client as needed.

Provide User Trainings before UAT starts

Support users in creating business scenarios, define quality test data as required

Very good domain understanding around Payment disputes (Fraud & Non-Fraud for Credit Cards)

Process Skills:

Agile, Center Out,

Identify and separate system user stories, integration user stories and establish clear dependencies

Ensure requirements are understood and functional defects are minimized on QA environment