Pega Lead Business Architect

About the role

Lead Business Architect (LBA) for a long‑term Pega project based in Iselin, New Jersey. The role focuses on driving Pega‑based solutions from requirement gathering through implementation, working closely with product owners, business stakeholders, and onsite/offshore teams.

Responsibilities

• Translate business requirements into detailed Pega requirements.
• Work independently with stakeholders (PO, Business, Onsite and Offshore teams).
• Run Show & Tell sessions with clients as needed.
• Provide user training before UAT starts.
• Support users in creating business scenarios and define quality test data.
• Identify dependencies among EPICs, Features and User Stories.
• Define and track user stories and acceptance criteria.
• Contribute to case management using the Smart Dispute Agentic Automation framework and out‑of‑the‑box journeys.
• Define the optimal Pega user experience with Constellation/UI Cosmos and out‑of‑the‑box features.

Requirements

• Experience working on Pega projects.
• Minimum 10 years of experience as a Business Analyst, including 5–6 years specifically in Pega.
• Experience in the Banking domain.

Qualifications

• PCBA certification with solid knowledge of Pega’s Infinity platform and Low‑Code/No‑Code development.
• 12+ years of overall IT experience.
• 8+ years of hands‑on Pega requirement management using a center‑out approach.

Skills

• Hands‑on expertise with Pega Blueprint to drive requirements, visual feedback 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 out‑of‑the‑box journeys.
• Ability to define best‑possible Pega User Experience using Constellation/UI Cosmos and out‑of‑the‑box features.
• Skill in identifying dependencies amongst EPICs, Features and User Stories.
• Crisp and clear definition and tracking of user stories and acceptance criteria.
• Ability to run Show & Tell sessions and provide user trainings before UAT.
• Support users in creating business scenarios and defining quality test data.
• Very good domain understanding of payment disputes (fraud and non‑fraud for credit cards).