Pega Lead System Architect (LSA)
- Discuss this with your agent
- Open in Claude
- Open in ChatGPT
Role details
Tech stack
Requirements
The Pega Lead System Architect (LSA) with good understanding of Smart Dispute framework, is responsible for driving the end-to-end Pega Application implementation through Pega s Center Out approach. leading the design, architecture, and delivery of Pega-based enterprise solutions. The LSA ensures alignment with Pega best practices, business objectives, and enterprise architecture standards while mentoring teams and driving successful implementations.
Technical Skills:
10+ years of overall IT experience & 8+ years of hands-on Pega Design & Architecture & Build
PCLSA - PART 2 complete.
Pega Smart Dispute Framework experience & financial domain experience.
Working experience with Pega 7.x, 8.x & Pega Infinity
Expertise in
o Case Management & Business rules & decisioning
o Data modeling and data pages
o UI Kit / Cosmos / Constellation UI
o Integrations (REST, SOAP, JMS, File, Database)
o Security & Access Control
Strong understanding of Pega Build /performance / rollouts - optimization & best practices
Crisp & Clear client facing communication with Technical Leadership & People management skills
Process Skills:
Understand most of the Pega offerings including BluePrint, Smart Dispute, Gen AI & Agentic
Excellent in setup, configurations, troubleshooting, integrations, security
Ability to work on aggressive schedules, drive team to achieve high velocity with low to no rework
Apply for this position
This job is hosted externally. Click below to view the full posting and apply.
Apply on www.dice.comGood distractions
Talks and stories from around this role — technically off-topic, practically not.
Moments
Explore playlistsVideos
See allRelated articles
See all
What Are The Top Skills Required For Azure Developers?
Graph and AI Trends 2026: Why Is AI Running but Not Yet Delivering?
From Prototype to Production: Build AI Agents with This Free 4-Course Learning Path
7 Important Tips That Every Software Developer Should Know