Pega BPM Developer
ARCHIVED
We can't find an active application page for this role right now. It may reopen or be listed elsewhere. Use Next Steps to search for an active apply link and similar live jobs.
Role: Pega BPM Developer
Location: Remote, C2CExperience:10+ And L2/L3 Hands-on Developer
Visa:
Independent OnlyShare your resumes to divya@brillfy.com / gopi@brillfy.comRequired Skills:
Pega 8.x / Pega 24 – hands-on experience; Pega 25 exposure/readiness preferred.
Case Management: Case Types, Stages, Steps, Flows, Flow Actions, Flow Rules, Circumstancing.
Rule Development: Data Transforms, Activities, When Rules, Routing Rules, Validation Rules.
UI/UX:
Sections, Dynamic Layouts, Skins, Field/Value Controls, Localization/Translation, Accessibility.
Correspondence: Correspondence Rules, Templates, Fragments, Paragraph Rules, document/letter generation, processing queues, high-volume content updates, bulk logo/phone/verbiage/disclaimer changes, reuse/circumstancing by Product/LOB.Data & Integrations: Data Pages, Data Transforms, Connectors, Java/SOA integration contracts, Mocking/Stubbing, data-page refresh/caching troubleshooting.
Reporting & Workflow: Report Definitions, Summarized Views, Work Queues, Assignments, SLAs.
Upgrades: Pega 24→25 upgrade awareness, deprecated components, warnings, remediation, Guardrails, Skins/Components behavior.
Testing: Unit/Scenario Testing, PegaUnit, Regression Testing, Defect Triage.
Deployment: RuleSets, Branching, Merge, CI/CD, Deployment and Release Management.
Performance: Guardrails, performance optimization and troubleshooting.
Domain: Healthcare/Insurance; Claims, Appeals, Encounters, Return Mail, Member/Provider Communications, Medicare preferred.
Agile: Sprint delivery, Scrum ceremonies, story ownership and time-boxed execution.
Collaboration: Work with Leads/BSAs, Java/SOA teams, Scrum and Release Management teams.
Nice to Have:
Large-scale Pega rebranding, CCP/POPM, Encounters, Return Mail, basic scripting/content audits. Key Requirement: Strong hands-on Pega 24 development + Correspondence + UI + Case/Flow/Rule development. L2/L3 developers preferred, not Architects/Leads.